Package org.opensearch.cluster.coordination
package org.opensearch.cluster.coordination
Cluster Coordination foundation classes.
-
ClassDescriptionA cluster-manager node sends this request to its peers to inform them that it could commit the cluster state with the given term and version.Service for bootstrapping the OpenSearch clusterHelper for cluster failure eventsPublishes the cluster stateAn acknowledgement listener.A helper class to utilize the compressed stream.Metadata for cluster coordinationBuilder for coordination metadata.Excluded nodes from voting config.A collection of persistent node ids, denoting the voting configuration for cluster state changes.The core class of the cluster state coordination algorithm, directly implementing the formal modelPluggable persistence layer for
CoordinationState.A collection of votes, used to calculate quorums.This exception is thrown when rejecting state transitions on theCoordinationStateobject, for example when receiving a publish request with the wrong term or version.The main lifecycle resource coordinatorThe mode of the coordinator.Command to detach a node from the clusterIt's provably impossible to guarantee that any leader election algorithm ever elects a leader, but they generally work (with probability that approaches 1 over time) as long as elections occur sufficiently infrequently, compared to the time it takes to send a message to another node and receive a response back.Allows plugging in a custom election strategy, restricting the notion of an election quorum.Thrown when failing to publish a cluster state.The FollowersChecker is responsible for allowing a leader to check that its followers are still connected and healthy.Request to check follower.Persist state in memoryTriggered by aStartJoinRequest, instances of this class represent join votes, and have a source and target node.Helper utility class for joining the clusterThe callback interface.Request for a node to join the clusterMain executor for Nodes joining the OpenSearch clusterTask for the join task executor.A publication can succeed and complete before all nodes have applied the published state and acknowledged it; however we need every node eventually either to apply the published state (or a later state) or be removed from the cluster.The LeaderChecker is responsible for allowing followers to check that the currently elected leader is still connected and healthy.Service to block the master nodeThis exception is thrown if the File system is reported unhealthy by @FsHealthServiceand this nodes needs to be removed from the clusterUpdate cluster state when node is removed from the clusterTask for the executor.Command Line Interface tool for NodesDeprecated.Main set of node commandsAn unknown condition.Custom unknown metadata.Response from peer nodesClass encapsulating stats about the PendingClusterStatsQueueA class which encapsulates the PersistedStatesDistinct Types PersistedState which can be present on a nodeCollects information prior to a promotion voteRequests pre vote information collectionResponse for a PreVoteRequestPublication taskTransport handler for publicationClass encapsulating stats about the PublishClusterStateActionRequest which is used by the cluster-manager node to publish cluster state changes.Response to aPublishRequest, carrying the term and version of the request.Response to aPublishRequest.Computes the optimal configuration of voting nodes in the cluster.Removes custom metadataRemoves custom settingsRepresents the action of requesting a join vote (seeJoin) from a node.Tool to run an unsafe bootstrapDeprecated.As of 2.2, because supporting inclusive language, replaced byUnsafeBootstrapClusterManagerCommandTransport request to validate node join
NoClusterManagerBlockService