Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-28482

backup_restore.js should run ReplSetTest.awaitSecondaryNodes before calling fsync on secondary.

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.5.6
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • 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.

      Attachments

        Activity

          People

            benety.goh@mongodb.com Benety Goh
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: