Update max local storage nodes docs

This commit updates the max local storage nodes docs to reflect that the
default is now one after 1f0673c9bd7e26ddf5ce55c6a184db2dbf4c778a.

Relates #20029
This commit is contained in:
Jason Tedor 2016-08-17 12:13:09 -04:00 committed by GitHub
parent 312a7d45ba
commit d4dec26aa0

View File

@ -281,21 +281,16 @@ your data! The RPM and Debian distributions do this for you already.
[[max-local-storage-nodes]]
=== `node.max_local_storage_nodes`
The <<data-path,data path>> can be shared by multiple nodes, even by nodes
from different clusters. This is very useful for testing failover and
different configurations on your development machine. In production, however,
it is recommended to run only one node of Elasticsearch per server.
The <<data-path,data path>> can be shared by multiple nodes, even by nodes from different
clusters. This is very useful for testing failover and different configurations on your development
machine. In production, however, it is recommended to run only one node of Elasticsearch per server.
To prevent more than one node from sharing the same data path, add this
setting to the `elasticsearch.yml` config file:
By default, Elasticsearch is configured to prevent more than one node from sharing the same data
path. To allow for more than one node (e.g., on your development machine), use the setting
`node.max_local_storage_nodes` and set this to a positve integer larger than one.
[source,yaml]
------------------------------
node.max_local_storage_nodes: 1
------------------------------
WARNING: Never run different node types (i.e. master, data) from the
same data directory. This can lead to unexpected data loss.
WARNING: Never run different node types (i.e. master, data) from the same data directory. This can
lead to unexpected data loss.
[float]
== Other node settings