-
Type:
Improvement
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Minor Change
-
Repl 2016-11-21
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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.
- is related to
-
-
- Closed
-
- related to
-
SERVER-27056 Don't enforce data freshness for step-up command
-
- Closed
-