Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
0
Description
|
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.