-
Type:
Improvement
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Labels:
-
Replication
-
Repl 15 (06/03/16), Repl 16 (06/24/16)
Note: With the refactoring of initial sync in the data replicator this should fall out of the work since we no longer have special apply phases, so once we start applying we can simply follow the normal recovery process. We need to make sure we have tests to ensure this works as designed (might be covered in other testing). In addition, we need to make sure we apply with fetching missing documents on failed updates, which causes the minvalid window to be extended on each fetch.
- is duplicated by
-
-
- Closed
-
- is related to
-
SERVER-32357 When secondary node's host crashes during MongoDB's initial sync, secondary needs to restart syncing data from scratch
-
- Closed
-
- related to
-
-
- Closed
-