Remove node.max_local_storage_nodes from setup doc #21305
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously node.max_local_storage_nodes defaulted to fifty, and this permitted users to start multiple instances of Elasticsearch sharing the same data folder. This can be dangerous, and usually it does not make sense to run more than one instance of Elasticsearch on a single server. Because of this, we had a note in the important settings docs advising users to set this setting to one. However, we have since changed the default value of this setting to one so this advise is no longer needed.
nik9000
approved these changes
Nov 3, 2016
jasontedor
added a commit
that referenced
this pull request
Nov 3, 2016
Previously node.max_local_storage_nodes defaulted to fifty, and this permitted users to start multiple instances of Elasticsearch sharing the same data folder. This can be dangerous, and usually it does not make sense to run more than one instance of Elasticsearch on a single server. Because of this, we had a note in the important settings docs advising users to set this setting to one. However, we have since changed the default value of this setting to one so this advise is no longer needed. Relates #21305
jasontedor
added a commit
that referenced
this pull request
Nov 3, 2016
Previously node.max_local_storage_nodes defaulted to fifty, and this permitted users to start multiple instances of Elasticsearch sharing the same data folder. This can be dangerous, and usually it does not make sense to run more than one instance of Elasticsearch on a single server. Because of this, we had a note in the important settings docs advising users to set this setting to one. However, we have since changed the default value of this setting to one so this advise is no longer needed. Relates #21305
jasontedor
deleted the
remove-node-max-local-storage-nodes-from-important-settings
branch
Member
Author
|
Thanks @nik9000. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously node.max_local_storage_nodes defaulted to fifty, and this
permitted users to start multiple instances of Elasticsearch sharing the
same data folder. This can be dangerous, and usually it does not make
sense to run more than one instance of Elasticsearch on a single
server. Because of this, we had a note in the important settings docs
advising users to set this setting to one. However, we have since
changed the default value of this setting to one so this advise is no
longer needed.
Relates #19964, relates #20029