[SERVER-14133] Make the initial sync process more resilient to connectivity issues Created: 02/Jun/14  Updated: 10/Dec/14  Resolved: 02/Jun/14

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

Type: Improvement Priority: Major - P3
Reporter: Alexander Komyagin 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-8076 Increased tolerance around network co... Closed
Related
Participants:

 Description   

Right now the initial sync process will drop all databases and restart upon losing the connectivity to the sync source. It can be a very big issue for big databases syncing from another DC.

There are a few places where we can improve the behavior:

  • if we are in the index build phase, we don't really care about the connection as data has already been fetched
  • if a collection has been already successfully fetched, there is no point in dropping it and fetching it all over again if there was a temporary connectivity problem.

Possibly there are other places, too. But these should be fairly simple and a good start.


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