-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.0.3, 2.1.0
-
Component/s: Replication, Sharding
-
None
-
ALL
... currently we're using a count that is never actually flushed out, except on reconfig (in 2.1, potentially in 2.0).
Also we may want to rethink our logic of waiting until the majority of slaves (# slaves / 2 + 1) is caught up. Why not majority of the set, for example?
- is duplicated by
-
SERVER-8072 Migrations calculate majority incorrectly when waiting for writes to replicate
- Closed