Skip to content

Commit 236f55a

Browse files
authored
Fix admonition about initial_master_nodes (#98242) (#98282)
Admonition paragraphs cannot be combined with a `+` continuation mark. This commit fixes the formatting by using an admonition block instead.
1 parent 4f75438 commit 236f55a

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

docs/reference/modules/discovery/bootstrapping.asciidoc

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -27,15 +27,18 @@ node:
2727
if it is not possible to use the `node.name` of the node and there are
2828
multiple nodes sharing a single IP address.
2929

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

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

0 commit comments

Comments
 (0)