-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[vtctld/wrangler] Extract EmergencyReparentShard
logic to dedicated struct and add unit tests
#7464
Conversation
|
||
event.DispatchUpdate(ev, "reparenting all tablets") | ||
|
||
// (@ajm188) - A question while migrating: Is this by design? By my read, |
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.
@deepthi question for you in particular here. @setassociative this is the issue I was talking to you about the other day.
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.
It seems like an oversight. Either we care about errors from handleReplica
and we should process them or not send them at all. The original design is documented in #6206 but I don't see that it goes into the details of error handling.
05e2207
to
ffd870e
Compare
Enforcing single-MASTER shards is something only certain tests will want, and in fact adding this behavior to `testutil.AddTablet` without this option broke several existing tests. Signed-off-by: Andrew Mason <[email protected]>
Signed-off-by: Andrew Mason <[email protected]>
…it tests This for increasing test coverage on the ERS code as well as to set us up for code reuse between the new vtctld and legacy vtctl RPCs in a future PR. Signed-off-by: Andrew Mason <[email protected]>
ffd870e
to
500b2e6
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. I assume we'll need to fix the errCh
issue separately.
Yep, I just filed #7480 to track that. I'll work on a fix after I finish up tests on |
[vtctld/wrangler] Extract `EmergencyReparentShard` logic to dedicated struct and add unit tests Signed-off-by: Richard Bailey <[email protected]>
Description
Mostly what it says in the title. I'll follow up with a
PlannedReparenter
PR soonish to do the same thing to that set of functionality.This for increasing test coverage on the ERS code as well as to set us
up for code reuse between the new vtctld and legacy vtctl RPCs in a
future PR.
Signed-off-by: Andrew Mason [email protected]
Related Issue(s)
Checklist
Deployment Notes
Impacted Areas in Vitess
Components that this PR will affect: