HBASE-26071: Document HBASE-26021 and upgrade considerations for 1.7.… #3469
Conversation
This file contains hidden or 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
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
gjacoby126
reviewed
Jul 9, 2021
| version. 1.7.0 was withdrawn and removed from the Apache sites. | ||
| * If you already installed a 1.7.0 cluster from scratch and are looking to migrate to 1.7.1+, you | ||
| cannot follow the regular rolling upgrade procedures due to broken compatibility contracts. | ||
| Instead shutdown the cluster and reboot with 1.7.1+ binaries. Newer versions detect any existing |
Contributor
There was a problem hiding this comment.
tiny nit: double space between "the" and "cluster"
Contributor
There was a problem hiding this comment.
For 1.7.0 to 1.7.1, do clients have to shutdown the cluster? I thought it was about restarting master only.
Contributor
Author
There was a problem hiding this comment.
In 1.7.0, client expects TableState (faulty serialization pb message) in GetTableStateResponse. Given that serialization has been undone (as we do not want to expose TableState anymore), client is not compatible (certain RPCs) with restarted Master. So it is safe to shutdown, update binaries everywhere and reboot the cluster.
I think this is ok given it is impossible that any serious user has upgraded an existing cluster to 1.7.0. Its only about new installations.
|
|
||
| * If you are considering an upgrade to 1.7.x version, skip 1.7.0 completely and upgrade to 1.7.1+ | ||
| version. 1.7.0 was withdrawn and removed from the Apache sites. | ||
| * If you already installed a 1.7.0 cluster from scratch and are looking to migrate to 1.7.1+, you |
Contributor
There was a problem hiding this comment.
What if I upgraded from 1.6 to 1.7.0 and am now running 1.7.0?
Contributor
Author
There was a problem hiding this comment.
You cannot, the bug doesn't let you upgrade. During the upgrade, 1.7.0 binaries try to parse the table descriptors and it blows up (META to begin with).
Reidddddd
reviewed
Jul 10, 2021
| version. 1.7.0 was withdrawn and removed from the Apache sites. | ||
| * If you already installed a 1.7.0 cluster from scratch and are looking to migrate to 1.7.1+, you | ||
| cannot follow the regular rolling upgrade procedures due to broken compatibility contracts. | ||
| Instead shutdown the cluster and reboot with 1.7.1+ binaries. Newer versions detect any existing |
Contributor
There was a problem hiding this comment.
For 1.7.0 to 1.7.1, do clients have to shutdown the cluster? I thought it was about restarting master only.
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
virajjasani
approved these changes
Jul 16, 2021
Contributor
virajjasani
left a comment
virajjasani
left a comment
There was a problem hiding this comment.
+1, one question: we can merge this only after withdrawing and removing mirrors of 1.7.0 release?
Contributor
Author
Correct, waiting for them to cleaned up everywhere. Will merge once done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
…0/1.7.1