Skip to content

Commit 737d850

Browse files
authored
Clarify persistence on master-eligible nodes (#70556)
We document that master nodes should have a persistent data path but it's a bit hard to understand that this is what the docs are saying and we don't really say why it's important. This commit clarifies this paragraph. Relates 49d0f34
1 parent b1c4cb4 commit 737d850

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

docs/reference/modules/node.asciidoc

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -121,9 +121,11 @@ Any master-eligible node that is not a <<voting-only-node,voting-only node>> may
121121
be elected to become the master node by the <<modules-discovery,master election
122122
process>>.
123123

124-
IMPORTANT: Master nodes must have access to the `data/` directory (just like
125-
`data` nodes) as this is where the cluster state is persisted between node
126-
restarts.
124+
IMPORTANT: Master nodes must have a `path.data` directory whose contents
125+
persist across restarts, just like data nodes, because this is where the
126+
cluster metadata is stored. The cluster metadata describes how to read the data
127+
stored on the data nodes, so if it is lost then the data stored on the data
128+
nodes cannot be read.
127129

128130
[[dedicated-master-node]]
129131
===== Dedicated master-eligible node

0 commit comments

Comments
 (0)