Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 0 additions & 26 deletions docs/reference/setup/important-settings.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -188,29 +188,3 @@ be thrown which will prevent the node from starting.

[float]
[[node.max_local_storage_nodes]]
=== `node.max_local_storage_nodes`

It is possible to start more than one node on the same server from the same
`$ES_HOME`, just by doing the following:

[source,sh]
--------------------------------------------------
./bin/elasticsearch -d
./bin/elasticsearch -d
--------------------------------------------------

This works just fine: the data directory structure is designed to let multiple
nodes coexist. However, a single instance of Elasticsearch is able to use all
of the resources of a single server and it seldom makes sense to run multiple
nodes on the same server in production.

It is, however, possible to start more than one node on the same server by
mistake and to be completely unaware that this problem exists. To prevent more
than one node from sharing the same data directory, it is advisable to add the
following setting:

[source,yaml]
--------------------------------------------------
node.max_local_storage_nodes: 1
--------------------------------------------------