mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
777598d602
* [DOCS] Remove manual redirects * [DOCS] Removed refs to modules-discovery-hosts-providers * [DOCS] Fixed broken internal refs * Fixing bad cross links in ES book, and adding redirects.asciidoc[] back into docs/reference/index.asciidoc. * Update docs/reference/search/point-in-time-api.asciidoc Co-authored-by: James Rodewig <james.rodewig@elastic.co> * Update docs/reference/setup/restart-cluster.asciidoc Co-authored-by: James Rodewig <james.rodewig@elastic.co> * Update docs/reference/sql/endpoints/translate.asciidoc Co-authored-by: James Rodewig <james.rodewig@elastic.co> * Update docs/reference/snapshot-restore/restore-snapshot.asciidoc Co-authored-by: James Rodewig <james.rodewig@elastic.co> * Update repository-azure.asciidoc * Update node-tool.asciidoc * Update repository-azure.asciidoc --------- Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Amy Jonsson <amy.jonsson@elastic.co> Co-authored-by: James Rodewig <james.rodewig@elastic.co>
71 lines
2.6 KiB
Text
71 lines
2.6 KiB
Text
[[modules-discovery]]
|
|
== Discovery and cluster formation
|
|
|
|
The discovery and cluster formation processes are responsible for discovering
|
|
nodes, electing a master, forming a cluster, and publishing the cluster state
|
|
each time it changes.
|
|
|
|
The following processes and settings are part of discovery and cluster
|
|
formation:
|
|
|
|
<<discovery-hosts-providers>>::
|
|
|
|
Discovery is the process where nodes find each other when the master is
|
|
unknown, such as when a node has just started up or when the previous
|
|
master has failed.
|
|
|
|
<<modules-discovery-quorums>>::
|
|
|
|
How {es} uses a quorum-based voting mechanism to
|
|
make decisions even if some nodes are unavailable.
|
|
|
|
<<modules-discovery-voting>>::
|
|
|
|
How {es} automatically updates voting configurations as nodes leave and join
|
|
a cluster.
|
|
|
|
<<modules-discovery-bootstrap-cluster>>::
|
|
|
|
Bootstrapping a cluster is required when an {es} cluster starts up
|
|
for the very first time. In <<dev-vs-prod-mode,development mode>>, with no
|
|
discovery settings configured, this is automatically performed by the nodes
|
|
themselves. As this auto-bootstrapping is
|
|
<<modules-discovery-quorums,inherently unsafe>>, running a node in
|
|
<<dev-vs-prod-mode,production mode>> requires bootstrapping to be
|
|
<<modules-discovery-bootstrap-cluster,explicitly configured>>.
|
|
|
|
<<add-elasticsearch-nodes,Adding and removing master-eligible nodes>>::
|
|
|
|
It is recommended to have a small and fixed number of master-eligible nodes
|
|
in a cluster, and to scale the cluster up and down by adding and removing
|
|
master-ineligible nodes only. However there are situations in which it may
|
|
be desirable to add or remove some master-eligible nodes to or from a
|
|
cluster. This section describes the process for adding or removing
|
|
master-eligible nodes, including the extra steps that need to be performed
|
|
when removing more than half of the master-eligible nodes at the same time.
|
|
|
|
<<cluster-state-publishing>>::
|
|
|
|
Cluster state publishing is the process by which the elected master node
|
|
updates the cluster state on all the other nodes in the cluster.
|
|
|
|
<<cluster-fault-detection>>::
|
|
|
|
{es} performs health checks to detect and remove faulty nodes.
|
|
|
|
<<modules-discovery-settings,Settings>>::
|
|
|
|
There are settings that enable users to influence the discovery, cluster
|
|
formation, master election and fault detection processes.
|
|
|
|
include::discovery/discovery.asciidoc[]
|
|
|
|
include::discovery/quorums.asciidoc[]
|
|
|
|
include::discovery/voting.asciidoc[]
|
|
|
|
include::discovery/bootstrapping.asciidoc[]
|
|
|
|
include::discovery/publishing.asciidoc[]
|
|
|
|
include::discovery/fault-detection.asciidoc[]
|