Remove usage of transient settings to enable allocations in full restart upgrade docs #29670
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
…art upgrad docs Since we disable allocation using persistent settings, we should be consistent and remove the setting from the persistent storage. Otherwise an accidental restart will leed for shards not being allocated.
colings86
added
>docs
Collaborator
|
Pinging @elastic/es-distributed |
Contributor
|
why is this PR opened against 6.2 instead of master? |
Contributor
Author
|
@ywelsch that's because this is how our "edit this" links on the websites are wired. It has to be that way to avoid confusion when people try to edit what they see. I will future port it once lgtmed. |
ywelsch
approved these changes
Apr 24, 2018
| -- | ||
| When all nodes have joined the cluster and recovered their primary shards, | ||
| reenable allocation. | ||
| reenable allocation by restoring `cluster.routing.allocation.enable` to it's |
Contributor
Author
|
Thanks @ywelsch |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Since we disable allocation using persistent settings, we should be consistent and remove
the setting from the persistent storage. Otherwise an accidental restart will leed for shards
not being allocated.
Relates to #28757