-
Notifications
You must be signed in to change notification settings - Fork 9.9k
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
[3.6] Backport DowngradeInfo proto change #19471
Conversation
Signed-off-by: Wei Fu <[email protected]> (cherry picked from commit 9d57554) Signed-off-by: Wei Fu <[email protected]>
Signed-off-by: Wei Fu <[email protected]> (cherry picked from commit 8575de3) Signed-off-by: Wei Fu <[email protected]>
Signed-off-by: Wei Fu <[email protected]> (cherry picked from commit 091b6ed) Signed-off-by: Wei Fu <[email protected]>
1. Update DowngradeUpgradeMembersByID If it's downgrading process, the desire version of cluster should be target one. If it's upgrading process, the desire version of cluster should be determined by mininum binary version of members. 2. Remove AssertProcessLogs from DowngradeEnable The log message "The server is ready to downgrade" appears only when the storage version monitor detects a mismatch between the cluster and storage versions. If traffic is insufficient to trigger a commit or if an auto-commit occurs right after reading the storage version, the monitor may fail to update it, leading to errors like: ```bash "msg":"failed to update storage version","cluster-version":"3.6.0", "error":"cannot detect storage schema version: missing confstate information" ``` Given this, we should remove the AssertProcessLogs statement. Similar to etcd-io#19313 Signed-off-by: Wei Fu <[email protected]> (cherry picked from commit 65159a2) Signed-off-by: Wei Fu <[email protected]>
Fixes: 65159a2 (*: Update cases related to Downgrade) Signed-off-by: Wei Fu <[email protected]> (cherry picked from commit 2de17bd) Signed-off-by: Wei Fu <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
... and 22 files with indirect coverage changes @@ Coverage Diff @@
## release-3.6 #19471 +/- ##
===============================================
- Coverage 68.99% 68.97% -0.03%
===============================================
Files 420 420
Lines 35753 35762 +9
===============================================
- Hits 24669 24666 -3
- Misses 9662 9674 +12
Partials 1422 1422 Continue to review full report in Codecov by Sentry.
|
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.
LGTM
Thanks
We need to update the 3.6 changelog as well.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahrtr, fuweid The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Link to #19456 |
Cherry-pick:
#19451
#19461
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.