-
Notifications
You must be signed in to change notification settings - Fork 837
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
[BTS-1644] ResignLeadership + Wait #21401
base: devel
Are you sure you want to change the base?
[BTS-1644] ResignLeadership + Wait #21401
Conversation
@@ -337,7 +344,28 @@ bool ResignLeadership::start(bool& aborts) { | |||
|
|||
// Schedule shard relocations | |||
if (!scheduleMoveShards(pending)) { | |||
finish("", "", false, "Could not schedule MoveShard."); | |||
LOG_TOPIC("d4473", DEBUG, Logger::SUPERVISION) |
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.
I would make this a "WARN" log level, according to our policy.
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.
Maybe "INFO", but it should show up in the logs whenever it happens in production, IMHO.
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.
I figured that it is enough to display this message when the job actually fails (see further down). Furthermore scheduleMoveShards
already creates log messages which explain why it won't start yet.
Scope & Purpose
Added waitForInSync and waitForInSyncTimeout parameters to the resign leadership job. This allows the user to wait for a certain amount of time to make sure that there exist common in sync followers. Previously they were just ignored and could cause downtime.
Design Doc: https://github.com/arangodb/documents/pull/136