-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication
-
ALL
-
This behavior means that we cannot use {w:2} writes to tell whether a slave has completed initial sync.
- related to
-
SERVER-25618 Slave in master/slave deployment can acknowledge operations prior to applying them
- Closed
-
SERVER-27033 Optype "db" not handled correctly by applyOperation_inlock
- Closed
-
SERVER-27055 initial_sync_id_index.js should not use w:2 write to check initial sync is complete
- Closed