-
Notifications
You must be signed in to change notification settings - Fork 453
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
Modified Upgrader11to12.upgradeZookeeper to be idempotent #5349
Open
dlmarion
wants to merge
1
commit into
apache:3.1
Choose a base branch
from
dlmarion:upgrade-zk-idempotence
base: 3.1
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is nearly identical to the code suggested by @keith-turner in #4996. I replied with #4996 (comment)
In short, it is not safe to assume that a non-zero length of data here is a complete and valid mapping.
If this fails, it could have failed for any number of unpredictable reasons. The current code behavior will catch it and force the user to deal with the unique and special circumstances that apply to them. This change, however, makes a lot of assumptions about the current contents being the result of a very specific situation that you encountered due to another bug in the upgrade process. That situation has already been fixed. If this is encountered again, it is likely a completely different scenario, and you can't make assumptions about that new scenario and why it failed.
It's nice to try to make the upgrade code more idempotent, but it's very hard to do that correctly and safely. We really need to make sure the upgrade works without failing. But, if it does fail, it's more important to detect it, and troubleshoot why. We really shouldn't be making guesses here.