Operational Defect Database

BugZero found this defect 2527 days ago.

MongoDB | 367565

[SERVER-28482] backup_restore.js should run ReplSetTest.awaitSecondaryNodes before calling fsync on secondary.

Last update date:

12/6/2017

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

3.5.6

Description:

Info

https://github.com/mongodb/mongo/blob/07ddacf92a2c53bd5a02878917ab8ebb35874413/jstests/noPassthrough/libs/backup_restore.js#L259 backup_restore.js 257   258 // Perform the data backup to new secondary 259 if (options.backup == 'fsyncLock') { 260 // Test that the secondary supports fsyncLock 261 var ret = secondary.getDB("admin").fsyncLock(); 262 if (!ret.ok) { Due to the load from the CRUD and FSM clients, we should wait for the non-primary nodes to become SECONDARY before running the fsync command. This should stabilize the test in the face of any rollbacks.

Top User Comments

xgen-internal-githook commented on Fri, 31 Mar 2017 19:01:59 +0000: Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'} Message: SERVER-28482 backup_restore.js should run ReplSetTest.awaitSecondaryNodes before calling fsync on secondary Branch: master https://github.com/mongodb/mongo/commit/1b012113fce67b22808097b9c2261317bb915093

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:

...