Details
-
Improvement
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
Minor Change
-
Repl 2016-11-21
Description
Currently in pv1 we call for priority takeover without concern for whether the higher priority node is caught up in replication, which can lead to unnecessary rollbacks of w:1 writes. If we avoid calling for an election due to priority takeover if we are more than X seconds repl lagged, then that in combination with the catchup period should prevent any writes from being lost during priority takeover.
Attachments
Issue Links
- is documented by
-
DOCS-9475 Docs for SERVER-26748: Don't call for priority takeover when repl lagged
-
- Closed
-
- is related to
-
SERVER-26725 Automatically reconfig pv1 replica sets using priorities or arbiters to pv0
-
- Closed
-
- related to
-
SERVER-27056 Don't enforce data freshness for step-up command
-
- Closed
-