-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Labels
>docs
General docs changes
Comments
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
Pinging @elastic/es-core-features (:Core/Features/Features) |
@TomonoriSoejima Thank you for bringing this up to our attention. |
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
matriv
added a commit
that referenced
this issue
Nov 28, 2019
matriv
added a commit
that referenced
this issue
Nov 28, 2019
matriv
added a commit
that referenced
this issue
Nov 28, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: