Skip to content

Commit ee0f116

Browse files
authored
Recommend no requests to dedicated masters (#70491)
Today the docs on node roles say that you shouldn't use dedicated masters for heavy requests such as indexing and searching, but as per the "designing for resilience" docs this guidance applies to all client requests. This commit generalises the node roles docs slightly to clarify this. Relates #70435
1 parent a99f3b5 commit ee0f116

File tree

1 file changed

+13
-10
lines changed

1 file changed

+13
-10
lines changed

docs/reference/modules/node.asciidoc

Lines changed: 13 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -130,16 +130,19 @@ restarts.
130130

131131
It is important for the health of the cluster that the elected master node has
132132
the resources it needs to fulfill its responsibilities. If the elected master
133-
node is overloaded with other tasks then the cluster may not operate well. In
134-
particular, indexing and searching your data can be very resource-intensive, so
135-
in large or high-throughput clusters it is a good idea to avoid using the
136-
master-eligible nodes for tasks such as indexing and searching. You can do this
137-
by configuring three of your nodes to be dedicated master-eligible nodes.
138-
Dedicated master-eligible nodes only have the `master` role, allowing them to
139-
focus on managing the cluster. While master nodes can also behave as
140-
<<coordinating-node,coordinating nodes>> and route search and indexing requests
141-
from clients to data nodes, it is better _not_ to use dedicated master nodes for
142-
this purpose.
133+
node is overloaded with other tasks then the cluster will not operate well. The
134+
most reliable way to avoid overloading the master with other tasks is to
135+
configure all the master-eligible nodes to be _dedicated master-eligible nodes_
136+
which only have the `master` role, allowing them to focus on managing the
137+
cluster. Master-eligible nodes will still also behave as
138+
<<coordinating-node,coordinating nodes>> that route requests from clients to
139+
the other nodes in the cluster, but you should _not_ use dedicated master nodes
140+
for this purpose.
141+
142+
A small or lightly-loaded cluster may operate well if its master-eligible nodes
143+
have other roles and responsibilities, but once your cluster comprises more
144+
than a handful of nodes it usually makes sense to use dedicated master-eligible
145+
nodes.
143146

144147
To create a dedicated master-eligible node, set:
145148

0 commit comments

Comments
 (0)