Skip to content

Rolling upgrade, use transient settings to disable shard allocation #343

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
bharath-elastic opened this issue Apr 25, 2018 · 1 comment
Closed
Labels
bug Something that does not look or behave correctly docs DO NOT USE for *contents* of our docs. Only use for documentation *about* this repo. question

Comments

@bharath-elastic
Copy link

Here https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html
Step 1: Disable shard allocation using persistent settings
.
.
Step 7: Enable shard allocation using transient settings (overrides persistent)
.
.
Step 9: Repeat steps for every node
If I repeat step 1 for the next node and disable shard allocation using "persistent settings", that wouldn't override the enabled shard allocation (which was set using transient settings in Step 7 of previous iteration) and won't get disabled correct? Unless I am missing something this is a bug? Please confirm.

@bharath-elastic bharath-elastic added bug Something that does not look or behave correctly question docs DO NOT USE for *contents* of our docs. Only use for documentation *about* this repo. labels Apr 25, 2018
@debadair
Copy link
Contributor

The docs need further changes. There's an issue for this in the ES repo: elastic/elasticsearch#27677

FYI, content issues should be opened in the appropriate product repo. We use this repo to track doc infra issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that does not look or behave correctly docs DO NOT USE for *contents* of our docs. Only use for documentation *about* this repo. question
Projects
None yet
Development

No branches or pull requests

2 participants