-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Replication
Investigate making initial sync more tolerant regarding network connectivity issues on the sync, i.e. investigate the possibility of a fresh TCP connection to resume the sync as opposed to going back to the start.
There are three distinct areas that would have to handle this better: the one they ran into (querying the primary for its latest optime), cloning, and connecting to fetch missing documents (as in their linked ticket).
One could also argue that it should be more flexible about changing initial sync targets mid-stream, however, that may be more difficult.
- is duplicated by
-
SERVER-17139 More retries needed when there are sync errors after initial sync
- Closed
-
SERVER-14133 Make the initial sync process more resilient to connectivity issues
- Closed
- is related to
-
SERVER-15410 Batch fetch missing documents during initial sync, with retries
- Closed
- related to
-
SERVER-18039 Add Initial Sync Skeleton to DataReplicator
- Closed