Skip to content
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

memberID equals zero in corruption alarm #14272

Merged
merged 1 commit into from
Jul 26, 2022
Merged

Conversation

serathius
Copy link
Member

cc @ahrtr

@serathius serathius force-pushed the memberID branch 2 times, most recently from 0f0358a to 7645ac7 Compare July 25, 2022 11:59
@serathius serathius force-pushed the memberID branch 2 times, most recently from 6e3b284 to a798812 Compare July 25, 2022 12:19
@serathius serathius changed the title Fix member id in CORRUPT alarm memberID equals zero in corruption alarm Jul 25, 2022
@codecov-commenter
Copy link

Codecov Report

Merging #14272 (a798812) into main (4977877) will decrease coverage by 0.15%.
The diff coverage is 73.91%.

@@            Coverage Diff             @@
##             main   #14272      +/-   ##
==========================================
- Coverage   75.40%   75.24%   -0.16%     
==========================================
  Files         456      456              
  Lines       36919    36946      +27     
==========================================
- Hits        27838    27800      -38     
- Misses       7345     7394      +49     
- Partials     1736     1752      +16     
Flag Coverage Δ
all 75.24% <73.91%> (-0.16%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
server/embed/etcd.go 75.14% <0.00%> (ø)
server/storage/mvcc/testutil/hash.go 83.56% <61.53%> (-12.19%) ⬇️
server/etcdserver/server.go 84.88% <75.00%> (-0.29%) ⬇️
server/etcdserver/corrupt.go 86.83% <100.00%> (+0.76%) ⬆️
server/auth/simple_token.go 80.00% <0.00%> (-8.47%) ⬇️
client/v3/namespace/watch.go 87.87% <0.00%> (-6.07%) ⬇️
client/v3/leasing/cache.go 87.77% <0.00%> (-3.89%) ⬇️
server/etcdserver/api/v3rpc/member.go 93.54% <0.00%> (-3.23%) ⬇️
client/v3/leasing/txn.go 88.09% <0.00%> (-3.18%) ⬇️
server/etcdserver/cluster_util.go 70.35% <0.00%> (-3.17%) ⬇️
... and 24 more

Help us with your feedback. Take ten seconds to tell us how you rate us.

@@ -16,6 +16,7 @@ Previous change logs can be found at [CHANGELOG-3.4](https://github.com/etcd-io/
- Fix [lessor may continue to schedule checkpoint after stepping down leader role](https://github.com/etcd-io/etcd/pull/14087).
- Fix [Restrict the max size of each WAL entry to the remaining size of the WAL file](https://github.com/etcd-io/etcd/pull/14127).
- Fix [Protect rangePermCache with a RW lock correctly](https://github.com/etcd-io/etcd/pull/14227)
- Fix [memberID equals zero in corruption alarm](https://github.com/etcd-io/etcd/pull/14272)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume you will update this once the PR is backported to 3.5?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes.

@serathius
Copy link
Member Author

ping @ahrtr

@ahrtr
Copy link
Member

ahrtr commented Jul 26, 2022

ping @ahrtr

I will take a deep review on this PR tomorrow. I guess you might need to rebase this PR after merging #14120

Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
Copy link
Member

@ahrtr ahrtr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ahrtr ahrtr merged commit 37e4193 into etcd-io:main Jul 26, 2022
@serathius
Copy link
Member Author

@ahrtr It might be worth considering backporting this to v3.4 release as currently corruption checks will not report which member is corrupted making the restore process require manually finding corrupted member.

@ahrtr
Copy link
Member

ahrtr commented Sep 27, 2022

Sure, let me take care of it for 3.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

3 participants