Update rolling-upgrade.md #7943
Merged
Conversation
This file contains 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
The current procedure doesn't follow the correct order. The shard allocation must be re-enabled after each node restart and the cluster status must be checked before upgrading the next node. Signed-off-by: Pawel Wlodarczyk <[email protected]>
pawelw1
requested review from
hdhalter,
kolchfa-aws,
Naarcha-AWS,
vagimeli,
AMoo-Miki,
natebower,
dlvenable and
epugh
as code owners
|
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
kolchfa-aws
approved these changes
Aug 8, 2024
opensearch-trigger-bot bot
pushed a commit
that referenced
this pull request
Aug 8, 2024
The current procedure doesn't follow the correct order. The shard allocation must be re-enabled after each node restart and the cluster status must be checked before upgrading the next node. Signed-off-by: Pawel Wlodarczyk <[email protected]> (cherry picked from commit f959fcb) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current procedure doesn't follow the correct order. The shard allocation must be re-enabled after each node restart and the cluster status must be checked before upgrading the next node.
Description
Describe what this change achieves.
The documentation issue has been reported in https://forum.opensearch.org/t/shard-fail-while-rolling-upgrade-cluster/20726
The current procedure doesn't follow the correct order. The shard allocation must be re-enabled after each node restart and the cluster status must be checked before upgrading the next node.
Version
List the OpenSearch version to which this PR applies, e.g. 2.14, 2.12--2.14, or all.
all 2.x versions
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.