- All Implemented Interfaces:
- com.hazelcast.internal.cluster.impl.operations.JoinOperation, com.hazelcast.nio.serialization.DataSerializable, com.hazelcast.nio.serialization.IdentifiedDataSerializable, com.hazelcast.spi.impl.AllowedDuringPassiveState, com.hazelcast.spi.UrgentSystemOperation
public class AskForClusterStartResultOperation
extends com.hazelcast.spi.Operation
implements com.hazelcast.internal.cluster.impl.operations.JoinOperation
It may happen that master can fail just after validating partition table of the nodes. If next master doesn't receive
the status change and some of other nodes receive, next master can not validate partition tables since some of other nodes
will not send their partition table as they started loading hot restart data. Master sends this operation to other nodes to
check if there is a status change it missed.