-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2019-07-15, Repl 2019-08-26
We currently think this was only necessary for mmapv1 when updates could cause a collection scan to miss a document. If we could remove this step, it could significantly speed up initial sync in certain workloads and simplify initial sync.
This would require the storage engine API to prohibit updates from causing collection scans to miss a document.
- is depended on by
-
SERVER-26780 SyncTail::getMissingDoc() should retry on SocketExceptions
- Closed
- is related to
-
SERVER-21057 Collection scan during concurrent move-update can return invalid results, trip fatal assertion (mmapv1 only)
- Closed
- related to
-
SERVER-15410 Batch fetch missing documents during initial sync, with retries
- Closed