NutclusterSharedDataManager (Atlassian Confluence 10.1.0 API)

java.lang.Object

com.atlassian.confluence.cluster.nutcluster.shareddata.NutclusterSharedDataManager

All Implemented Interfaces:: SharedDataManager

@Internal @Deprecated(since="8.2", forRemoval=true) public class NutclusterSharedDataManager extends Object implements SharedDataManager

Deprecated, for removal: This API element is subject to removal in a future version.

since 8.2

A Nutcluster implementation of SharedDataManager

Since:: 5.7

Constructor Summary

Constructors

Constructor

Description

NutclusterSharedDataManager(com.atlassian.nutcluster.core.NutclusterInstance nutclusterInstance)

Deprecated, for removal: This API element is subject to removal in a future version.
Method Summary

Modifier and Type

Method

Description

@NonNull SharedData

getSharedData(String name)

Deprecated, for removal: This API element is subject to removal in a future version.

Obtain a SharedDataManager for the given key.

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details
- NutclusterSharedDataManager
  
  public NutclusterSharedDataManager(com.atlassian.nutcluster.core.NutclusterInstance nutclusterInstance)
  
  Deprecated, for removal: This API element is subject to removal in a future version.
  
  Since:
  
  7.6
Method Details
- getSharedData
  
  public @NonNull SharedData getSharedData(String name)
  
  Deprecated, for removal: This API element is subject to removal in a future version.
  
  Description copied from interface: SharedDataManager
  
  Obtain a SharedDataManager for 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:
  
  getSharedData in interface SharedDataManager