-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Improving ConfigCheckSeconds for a faster failover detection #1735
Improving ConfigCheckSeconds for a faster failover detection #1735
Conversation
After a master node disconnect performs ConfigCheckSeconds on replica nodes with an exponential backoff
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 think this one's good - would like a name tweak for clarity though please!
|
||
|
||
// Forces frequent replication check starting from 1 second upto max ConfigCheckSeconds with an exponential increment | ||
internal void ForceExponentiallyReplicationCheck() |
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.
Can we rename this for clarity please?
internal void ForceExponentiallyReplicationCheck() | |
internal void ForceExponentialBackoffReplicationCheck() |
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.
👍 Looking good, thanks for the tweaks!
Fixes info command storm on a disconnect
After a master node disconnect performs ConfigCheckSeconds on replica nodes with an exponential backoff