Returns the distributed AtomicLong instance with given name. The instance is created on CP Subsystem.
If no group name is given within the name argument, then the
AtomicLong instance will be created on the DEFAULT CP group.
If a group name is given, like .getAtomicLong('myLong@group1'),
the given group will be initialized first, if not initialized
already, and then the instance will be created on this group.
Returns the distributed AtomicReference instance with given name. The instance is created on CP Subsystem.
If no group name is given within the name argument, then the
AtomicLong instance will be created on the DEFAULT CP group.
If a group name is given, like .getAtomicReference('myRef@group1'),
the given group will be initialized first, if not initialized
already, and then the instance will be created on this group.
Returns the distributed CountDownLatch instance with given name. The instance is created on CP Subsystem.
If no group name is given within the name argument, then the
ICountDownLatch instance will be created on the DEFAULT CP group.
If a group name is given, like .getCountDownLatch('myLatch@group1'),
the given group will be initialized first, if not initialized
already, and then the instance will be created on this group.
Returns the distributed FencedLock instance with given name. The instance is created on CP Subsystem.
If no group name is given within the name argument, then the
FencedLock instance will be created on the DEFAULT CP group.
If a group name is given, like .getLock('myLock@group1'),
the given group will be initialized first, if not initialized
already, and then the instance will be created on this group.
Returns the distributed Semaphore instance with given name. The instance is created on CP Subsystem.
If no group name is given within the name argument, then the
Semaphore instance will be created on the DEFAULT CP group.
If a group name is given, like .getSemaphore('mySemaphore@group1'),
the given group will be initialized first, if not initialized
already, and then the instance will be created on this group.
Generated using TypeDoc
CP Subsystem is a component of Hazelcast that builds a strongly consistent layer for a set of distributed data structures. Its APIs can be used for implementing distributed coordination use cases, such as leader election, distributed locking, synchronization, and metadata management.
Its data structures are CP with respect to the CAP principle, i.e., they always maintain linearizability and prefer consistency over availability during network partitions. Besides network partitions, CP Subsystem withstands server and client failures.
Data structures in CP Subsystem run in CP groups. Each CP group elects its own Raft leader and runs the Raft consensus algorithm independently.
The CP data structures differ from the other Hazelcast data structures in two aspects. First, an internal commit is performed on the METADATA CP group every time you fetch a proxy from this interface. Hence, callers should cache returned proxy objects. Second, if you call
DistributedObject.destroy()on a CP data structure proxy, that data structure is terminated on the underlying CP group and cannot be reinitialized until the CP group is force-destroyed. For this reason, please make sure that you are completely done with a CP data structure before destroying its proxy.