-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v3.4
-
Repl 2017-01-23
-
0
Once CollectionCloner starts fetching documents from the remote server, there are two parallel threads of execution within the CollectionCloner that can lead to _finishCallback() being invoked. We should ensure that _finishCallback() is called with the first completion/failure status AFTER both threads of execution have been joined.
- depends on
-
SERVER-27677 CollectionBulkLoader::_releaseResources() should ensure there is a Client available
- Closed
- is depended on by
-
SERVER-27611 DatabaseCloner::shutdown() does not shut down CollectionCloner
- Closed
-
SERVER-27775 fix race in collection_cloner_test CollectionClonerTest::CollectionClonerCannotBeRestartedAfterPreviousFailure
- Closed
- is duplicated by
-
SERVER-27944 mongodb 3.4.1 OOM when add new node to replica set
- Closed
-
SERVER-28241 OOM error while adding a member to replica set
- Closed