Skip to content
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

add some pointer to determine when upgrading is complete #49670

Closed
TomonoriSoejima opened this issue Nov 28, 2019 · 4 comments · Fixed by #49686
Closed

add some pointer to determine when upgrading is complete #49670

TomonoriSoejima opened this issue Nov 28, 2019 · 4 comments · Fixed by #49686
Assignees
Labels
>docs General docs changes

Comments

@TomonoriSoejima
Copy link
Contributor

https://www.elastic.co/guide/en/elasticsearch/reference/7.4/rolling-upgrades.html#rolling-upgrades shows the step of rolling upgrade process, but it would be nice to add final step as to how to validate the upgrade finished successfully.

I can imagine that everyone must be issuing some flavor of cat API and it would be helpful if we can list them up in this page as well.

@matriv matriv added the >docs General docs changes label Nov 28, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs (>docs)

matriv added a commit to matriv/elasticsearch that referenced this issue Nov 28, 2019
Add a couple of pointers for the user to check the
overall cluster health and the version of ES running
on every node.

Fixes: elastic#49670
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Features)

@matriv
Copy link
Contributor

matriv commented Nov 28, 2019

@TomonoriSoejima Thank you for bringing this up to our attention.
A PR is out to provide more info on how to check the status of a rolling upgrade.

@matriv matriv self-assigned this Nov 28, 2019
matriv added a commit that referenced this issue Nov 28, 2019
Add a couple of pointers for the user to check the
overall cluster health and the version of ES running
on every node.

Fixes: #49670
matriv added a commit that referenced this issue Nov 28, 2019
Add a couple of pointers for the user to check the
overall cluster health and the version of ES running
on every node.

Fixes: #49670

(cherry picked from commit 8ca11f5)
matriv added a commit that referenced this issue Nov 28, 2019
Add a couple of pointers for the user to check the
overall cluster health and the version of ES running
on every node.

Fixes: #49670

(cherry picked from commit 8ca11f5)
matriv added a commit that referenced this issue Nov 28, 2019
Add a couple of pointers for the user to check the
overall cluster health and the version of ES running
on every node.

Fixes: #49670

(cherry picked from commit 8ca11f5)
@matriv
Copy link
Contributor

matriv commented Nov 28, 2019

master : 8ca11f5
7.x : d5842ae
7.5 : eefc6ec
7.4 : 073449b
6.8 : 6e643fe

matriv added a commit that referenced this issue Nov 28, 2019
Add a couple of pointers for the user to check the
overall cluster health and the version of ES running
on every node.

Fixes: #49670

(cherry picked from commit 8ca11f5)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>docs General docs changes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants