[SERVER-32357] When secondary node's host crashes during MongoDB's initial sync, secondary needs to restart syncing data from scratch Created: 15/Dec/17  Updated: 06/Dec/22  Resolved: 20/Nov/19

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

Type: New Feature Priority: Major - P3
Reporter: Shi Kris Assignee: Backlog - Replication Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-18564 Allow resuming initial sync: resume d... Closed
related to SERVER-18565 Allow resuming initial sync: during a... Closed
Assigned Teams:
Replication
Participants:

 Description   

When secondary node's host crashes during MongoDB's initial sync, secondary needs to restart syncing data from scratch. This is an overhead and resumption of sync would be ideal for efficiency in terms of time and bandwidth.



 Comments   
Comment by Steven Vannelli [ 20/Nov/19 ]

Closing this ticket as all work related to this project is captured within other tickets.

Generated at Thu Feb 08 04:30:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.