-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.4.0-rc3
-
Component/s: Replication
-
None
-
Fully Compatible
-
v3.4
-
Repl 2016-11-21, Repl 2016-12-12
-
0
DataReplicator currently requires a dedicated thread to run doInitialSync, which has ramifications for testing and makes it inconvenient to integrate with other components such as the ReplicationCoordinator.
- causes
-
SERVER-30913 remove unused getLatestOplogEntry method from initial_syncer
- Closed
- depends on
-
SERVER-27079 DataReplicator should wait for last oplog fetcher to finish before starting next initial sync attempt
- Closed
- is related to
-
SERVER-25662 Data replicator should stop initial sync and shut down immediately when server is shut down
- Closed
- related to
-
SERVER-25966 Add initial sync unittests for metadata retries
- Closed
-
SERVER-26704 Refactor DataReplicator::getLatestOplogEntry() to use _scheduleLastOplogEntryFetcher_inlock()
- Closed
-
SERVER-27047 DataReplicator should return ShutdownInProgress when it is shutdown
- Closed
-
SERVER-27134 Do not reset numGetMoreOplogEntries in GetInitialSyncProgress test in DataReplicatorTest
- Closed
-
SERVER-27135 Check if DataReplicator finishEvent has been signalled before signalling it again
- Closed
-
SERVER-31995 Logged initial sync statistics may exceed 16mb causing fassert
- Closed