Interface CPMember
CPSubsystem, hence maintain CP data structures. If
CPSubsystemConfig.getCPMemberCount() is configured to be N,
first N members of the cluster are assigned as CP members during startup.
After CP Subsystem is initialized, other Hazelcast members can be promoted
to be a CP member via
CPSubsystemManagementService.promoteToCPMember().-
Method Summary
Modifier and TypeMethodDescriptionReturns the address of this CP member.getUuid()Returns the UUID of this CP member.booleanReturns whether this CP member is configured to automatically step down from leadership in non-metadata CP groups.
-
Method Details
-
getUuid
UUID getUuid()Returns the UUID of this CP member. The CP member UUID does not have to be same with the UUID of the local member that is accessed viaCluster.getLocalMember().- Returns:
- the UUID of this CP Member
-
getAddress
Address getAddress()Returns the address of this CP member. It is same with the address ofCluster.getLocalMember()- Returns:
- the address of this CP member
-
isAutoStepDownWhenLeader
boolean isAutoStepDownWhenLeader()Returns whether this CP member is configured to automatically step down from leadership in non-metadata CP groups.If
true, whenever this member is elected leader, it will suspend replication, immediately trigger a leadership transfer, and resume normal operation once a leader-capable member takes over. Client operations are retried transparently and eventually succeed under the new leader.When this flag is enabled, the member's effective priority is treated as
Integer.MIN_VALUEto prevent leader rebalancing from assigning leadership to a node that would immediately step down.This feature is useful when a node has high latency to the rest of the CP group, where holding leadership could destabilize replication. A brief unavailability window may occur during the leadership transfer, proportional to the RTT and log catch-up required for the target leader.
- Returns:
trueif this member automatically steps down from leadership- Since:
- 5.7
-