[SERVER-38647] backup_restore_rolling.js can fail due to stepdown Created: 14/Dec/18  Updated: 29/Oct/23  Resolved: 14/Dec/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.11, 4.0.6, 4.1.7

Type: Bug Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: A. Jesse Jiryu Davis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Operating System: ALL
Backport Requested:
v4.0, v3.6
Sprint: Repl 2019-01-14
Participants:
Linked BF Score: 18

 Description   

If test machine load is high enough to delay heartbeats by over 10 seconds, a replica can call for an election and cause the primary to step down. BackupRestoreTest doesn't anticipate this and can fail. In one observed case, it fails when calling listDatabases on a replica it thought was still the primary - this results in "not master" and aborts the test.

Let's increase the electionTimeoutMillis when setting up the replica set to prevent elections.



 Comments   
Comment by Githook User [ 25/Jan/19 ]

Author:

{'username': 'ajdavis', 'email': 'jesse@mongodb.com', 'name': 'A. Jesse Jiryu Davis'}

Message: SERVER-38647 Avoid stepdown in backup_restore_rolling.js
Branch: v3.6
https://github.com/mongodb/mongo/commit/1446a8c4d4a093f6ac8487796905389d60506725

Comment by Githook User [ 10/Jan/19 ]

Author:

{'username': 'ajdavis', 'email': 'jesse@mongodb.com', 'name': 'A. Jesse Jiryu Davis'}

Message: SERVER-38647 Avoid stepdown in backup_restore_rolling.js
Branch: v4.0
https://github.com/mongodb/mongo/commit/f7d0b7102f90b9a2d13265245b1a848c5cdb27c7

Comment by A. Jesse Jiryu Davis [ 14/Dec/18 ]

Apologies for the bad commit message:

https://github.com/mongodb/mongo/commit/333b35057d35230ad5bc868bd0eaa7423d9aceb4

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