Skip to content

Commit

Permalink
Fix admonition about initial_master_nodes (#98242) (#98282)
Browse files Browse the repository at this point in the history
Admonition paragraphs cannot be combined with a `+` continuation mark.
This commit fixes the formatting by using an admonition block instead.
  • Loading branch information
DaveCTurner authored Aug 8, 2023
1 parent 4f75438 commit 236f55a
Showing 1 changed file with 8 additions and 5 deletions.
13 changes: 8 additions & 5 deletions docs/reference/modules/discovery/bootstrapping.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -27,15 +27,18 @@ node:
if it is not possible to use the `node.name` of the node and there are
multiple nodes sharing a single IP address.

IMPORTANT: After the cluster has formed, remove the `cluster.initial_master_nodes`
setting from each node's configuration. It should not be set for
master-ineligible nodes, master-eligible nodes joining an existing cluster, or
nodes which are restarting.
+
[IMPORTANT]
====
After the cluster has formed, remove the `cluster.initial_master_nodes` setting
from each node's configuration. It should not be set for master-ineligible
nodes, master-eligible nodes joining an existing cluster, or nodes which are
restarting.
If you leave `cluster.initial_master_nodes` in place once the cluster has
formed then there is a risk that a future misconfiguration may result in
bootstrapping a new cluster alongside your existing cluster. It may not be
possible to recover from this situation without losing data.
====

The simplest way to create a new cluster is for you to select one of your
master-eligible nodes that will bootstrap itself into a single-node cluster,
Expand Down

0 comments on commit 236f55a

Please sign in to comment.