-
Notifications
You must be signed in to change notification settings - Fork 855
Delay MoveShard job until old and new leader ready - BTS-1110 #17554
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
Conversation
Also delay, if supposed follower is not in sync.
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.
The code logic is fine. But MoveShard::start()
now finally broke the 300 lines mark. Is it possible to put the new code into a separate function?
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.
Minor language
This addresses https://arangodb.atlassian.net/browse/BTS-1110 .
The problem is that if a MoveShard which switches leadership begins to
work, although the supposed leader has not yet assumed its leadership,
then we get stuck. The old leader does no longer assume leadership and
as a consequence cannot resign and the MoveShard job is stuck.
Scope & Purpose
(Please describe the changes in this PR for reviewers, motivation, rationale - mandatory)
Checklist
Related Information
(Please reference tickets / specification / other PRs etc)