Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Replication
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Operating System:ALL
-
Backport Requested:v3.6, v3.4
-
Sprint:Repl 2017-10-23, Repl 2017-11-13, Repl 2017-12-04
-
Linked BF Score:68
Attachments
Issue Links
- depends on
-
SERVER-31695 Support queries across collection renames
-
- Open
-
- is depended on by
-
SERVER-31466 CollectionCloner fails when a collection is dropped and re-created between getMores
-
- Closed
-
- is duplicated by
-
SERVER-31264 CollectionCloner should ignore NamespaceNotFound errors
-
- Closed
-
- related to
-
SERVER-32136 initial_sync_drop_collection.js should wait for system to stablize after restarting node
-
- Closed
-
-
SERVER-32783 CollectionCloner::shutdown() should not block on resetting _verifyCollectionDroppedScheduler
-
- Closed
-
-
SERVER-32089 Support rename collections during initial sync by retrying
-
- Open
-