[SERVER-28482] backup_restore.js should run ReplSetTest.awaitSecondaryNodes before calling fsync on secondary. Created: 24/Mar/17  Updated: 06/Dec/17  Resolved: 31/Mar/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.5.6

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

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.



 Comments   
Comment by Githook User [ 31/Mar/17 ]

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

Generated at Thu Feb 08 04:18:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.