[SERVER-21068] Ability to resume initial sync attemps Created: 22/Oct/15  Updated: 22/Oct/15  Resolved: 22/Oct/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.0.7
Fix Version/s: None

Type: Improvement Priority: Critical - P2
Reporter: Ricardo Lorenzo Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-18565 Allow resuming initial sync: during a... Closed
Related
is related to SERVER-13117 Secondary repeatedly fails to sync Closed
Participants:

 Description   

For large data sets (>2TB) the initial sync is problematic. If you are migrating from MMAP to WiredTiger storage engine, there is no other way to do it.

It would be nice to have the ability to resume the attempts if some issue occurs, especially in relation to the network. Otherwise, you need to start from the beginning a process that could take more than 2-6 days depending on the size. I understand other features like parallel sync for different collections could help here. However, it isn't the case for large collections.

This is especially relevant for the phase where the initial sync is applying the oplog. It should be easy to resume the operation here if the oplog has a valid point instead of triggering a new initial sync.


Generated at Thu Feb 08 03:56:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.