[SERVER-53961] Restarting heartbeats in RollbackTest.transitionToSyncSourceOperationsDuringRollback can fail to run if the node is already in rollback Created: 21/Jan/21  Updated: 17/Feb/21  Resolved: 17/Feb/21

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

Type: Bug Priority: Major - P3
Reporter: Gregory Noma Assignee: Huayu Ouyang
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-54540 Allow for network errors when restart... Closed
Operating System: ALL
Sprint: Repl 2021-02-22
Participants:
Linked BF Score: 11

 Description   

When transitioning to kSyncSourceOpsDuringRollback, the rollback test fixture restarts heartbeats on the secondary after it is reconnected. However, it appears that if the node goes into rollback before this restartHeartbeats command goes through, it can fail with

uncaught exception: Error: error doing query: failed: network error while attempting to run command 'replSetTest' on host 'ip-10-122-83-72:20520'  :
DB.prototype.runCommand@src/mongo/shell/db.js:177:19
Mongo.prototype.adminCommand@src/mongo/shell/mongo.js:159:12
RollbackTest/this.transitionToSyncSourceOperationsDuringRollback@jstests/replsets/libs/rollback_test.js:572:30



 Comments   
Comment by Judah Schvimer [ 25/Jan/21 ]

We can probably just switch the order of the two linked javascript lines.

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