Class NonClusterSharedDataManager
- java.lang.Object
-
- com.atlassian.confluence.cluster.nonclustered.NonClusterSharedDataManager
-
- All Implemented Interfaces:
PluginSharedDataStore,SharedDataManager
@Internal public final class NonClusterSharedDataManager extends Object implements SharedDataManager, PluginSharedDataStore
An implementation ofSharedDataManagerfor use when no clustering is configured. It provides trivial in-memory data structures.- Since:
- 5.7
-
-
Constructor Summary
Constructors Constructor Description NonClusterSharedDataManager()
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description SharedDatagetPluginSharedData(PluginSharedDataKey sharedDataKey, com.atlassian.plugin.Plugin plugin)Obtain the stored SharedData instance for the given key and plugin informationSharedDatagetSharedData(String name)Obtain aSharedDataManagerfor the given key.voidunregisterPluginSharedData(com.atlassian.plugin.Plugin plugin)Unregisters all shared data for the specific version of the given plugin.
-
-
-
Method Detail
-
getPluginSharedData
public SharedData getPluginSharedData(PluginSharedDataKey sharedDataKey, com.atlassian.plugin.Plugin plugin)
Description copied from interface:PluginSharedDataStoreObtain the stored SharedData instance for the given key and plugin information- Specified by:
getPluginSharedDatain interfacePluginSharedDataStore
-
unregisterPluginSharedData
public void unregisterPluginSharedData(com.atlassian.plugin.Plugin plugin)
Description copied from interface:PluginSharedDataStoreUnregisters all shared data for the specific version of the given plugin.- Specified by:
unregisterPluginSharedDatain interfacePluginSharedDataStore
-
getSharedData
public SharedData getSharedData(String name)
Description copied from interface:SharedDataManagerObtain aSharedDataManagerfor the given key. Data managed via that provider will be shared across all nodes of the cluster.The returned shared data provider makes no consistency guarantees. On a single node cluster, or in a non-clustered installation, strong consistency can be assumed, and in a multi-node cluster a best-effort consistency will be provided. Some implementations may provide strong consistency, others may only provide weak and/or eventual consistency.
The shared data should be persistent as long as at least one node of the cluster remains running. If multiple cluster nodes fail simultaneously, then the data may be lost. Implementations may persist this data even if the whole cluster is restarted, but clients should not assume one way or the other.
- Specified by:
getSharedDatain interfaceSharedDataManager
-
-