Skip to content

[Docs] Rolling upgrade use "transient" instead "persistent" for disabling shard allocation #27860

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.

Sign up for GitHub

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

Jump to bottom
Closed
johtani opened this issue Dec 18, 2017 · 1 comment
Closed

[Docs] Rolling upgrade use "transient" instead "persistent" for disabling shard allocation #27860

johtani opened this issue Dec 18, 2017 · 1 comment
Labels
>bug >docs General docs changes v6.0.0 v6.1.0

Comments

@johtani
Copy link
Contributor

johtani commented Dec 18, 2017

https://www.elastic.co/guide/en/elasticsearch/reference/6.1/rolling-upgrades.html

In Rolling upgrades document, the sample request of step 1. uses persistent for enabling shard allocation, but the sample request for 7. reenabling shard allocation uses transient.

If a user restart cluster after upgrading, elasticsearch can not allocate shards any more...
The sample request for 1. has to use transient.

This change happened after 6.0, we shared the documentation between rolling upgrade and full cluster restart.
@johtani johtani added >bug >docs General docs changes v6.0.0 v6.1.0 labels Dec 18, 2017
jsuchenia added a commit to jsuchenia/elasticsearch-prometheus-metrics that referenced this issue Jan 19, 2018
@jsuchenia
Update cluster-name, add additional rules
565a183 
Prevent from an Elastic bug: elastic/elasticsearch#27860
@jasontedor
Copy link
Member

Duplicates #27677

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>bug >docs General docs changes v6.0.0 v6.1.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@johtani @jasontedor