Operational Defect Database

BugZero found this defect 2516 days ago.

MongoDB | 372165

[SERVER-28699] ReplSetTest should always awaitSecondaryNodes() at the end of initiate

Last update date:

8/15/2017

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

3.4.4

3.5.6

Description:

Info

when initiate was broken up into initiateWithAnyNodeAsPrimary() and initiateWithNodeZeroAsPrimary(), initiateWithAnyNodeAsPrimary() lost the call to awaitSecondaryNodes() at the end. This was necessary to make sure initiate actually finished before moving on with the test.

Top User Comments

xgen-internal-githook commented on Thu, 13 Apr 2017 00:16:21 +0000: Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'} Message: SERVER-28699 ReplSetTest should always awaitSecondaryNodes() at the end of initiate (cherry picked from commit 2788b12816f9124cae6b35a0554361b232c27419) Branch: v3.4 https://github.com/mongodb/mongo/commit/c431782e66416e7dbbd9db457d9507b65c6304ba xgen-internal-githook commented on Wed, 12 Apr 2017 20:59:35 +0000: Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'} Message: SERVER-28699 ReplSetTest should always awaitSecondaryNodes() at the end of initiate Branch: master https://github.com/mongodb/mongo/commit/2788b12816f9124cae6b35a0554361b232c27419

Additional Resources / Links

Share:

BugZero Risk Score

Coming soon

Status

Closed

Have you been affected by this bug?

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Discussion

Login to read and write comments.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...