Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.4.2, 3.5.2
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Completed:

3.4.2
Backport Requested:

v3.4
Sprint:
Repl 2017-01-23
Linked BF Score:
0
Confidence Status:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: Benety Goh

Reporter:: Benety Goh

Participants:: Benety Goh, Githook User

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: Jan 13 2017 05:26:19 PM UTC

Updated:: Apr 05 2017 11:44:25 AM UTC

Resolved:: Jan 21 2017 01:54:54 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates