-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Add cluster id check for hash kv handler #15924
Add cluster id check for hash kv handler #15924
Conversation
Change overall looks good, but would like to have more tests as this is pretty critical functionality. If possible I would also like to have an e2e tests for inplace cluster restore. Do you think you can add an e2e tests? |
Sure. Working on it. |
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.
Thanks for your work on this @CaojiamingAlan.
Can you please squash the two identically named commits for etcdserver: add e2e test for periodic check after in-place recovery
.
216a75b
to
903a440
Compare
@serathius I've added the tests. Could you please review them? thx. |
Hi @CaojiamingAlan I can help review the PR in case Marrek bandwidth is limited, give me a hour to refresh my mind on this area of code. |
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 with some nit-picks.
@chaochn47 Comments fixed. Thank you for your review. |
Thanks @CaojiamingAlan, please consider squash all the commits into one before asking for merging the PR~ |
3c8a40b
to
b16b4d4
Compare
@chaochn47 Squashed. |
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 with some comments.
1113d40
to
21afa04
Compare
4525a37
to
3c48272
Compare
@CaojiamingAlan Have you raised a followup ticket for #15924 (comment)? Please also rebase this PR although github doesn't show any conflict. |
3c48272
to
f787be4
Compare
@ahrtr Have just rebased the PR and raised #16178. I was waiting for this to be merged first so didn't raise it previously. Sorry for misunderstanding what you meant. BTW, are all errors supposed to be in api/v3rpc/rpctypes/error.go? I've just realized that Raft and corrupt uses HTTP rather than gRPC. I think using errors with the 'grpc' prefix is a bit confusing. |
f787be4
to
79b212e
Compare
Right. We should avoid defining errors in |
79b212e
to
0afc201
Compare
Signed-off-by: caojiamingalan <[email protected]>
0afc201
to
eff9517
Compare
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 @CaojiamingAlan
Was this backported to v3.4 and v3.5? @CaojiamingAlan can you backport? |
backport etcd-io#15924 to 3.4 Signed-off-by: Benjamin Wang <[email protected]>
backport etcd-io#15924 to 3.4 Signed-off-by: Benjamin Wang <[email protected]>
backport etcd-io#15924 to 3.4 Signed-off-by: Benjamin Wang <[email protected]>
backport etcd-io#15924 to 3.4 Signed-off-by: Benjamin Wang <[email protected]>
Fix #15548
This PR only adds cluster id check for hashKVHandler. Cluster id checks for other handlers(member, promote, version, etc.) will be in separate PRs.