[SERVER-67022] txn_two_phase_commit_wait_for_majority_commit_after_stepup.js should not depend on timing Created: 03/Jun/22  Updated: 29/Oct/23  Resolved: 20/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc11, 6.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: Andrew Shuvalov (Inactive)
Resolution: Fixed 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   

The timeout in this fragment

const stepDownSecs = 1;
assert.commandWorked(coordPrimary.adminCommand({replSetStepDown: stepDownSecs, force: true}));

is not essential for the test correctness. As the test failed with:

"errmsg" : "By the time we were ready to step down, we were already past the time we were supposed to step down until",

we should give more time to the step down command



 Comments   
Comment by Githook User [ 19/Sep/22 ]

Author:

{'name': 'Andrew Shuvalov', 'email': '71660459+shuvalov-mdb@users.noreply.github.com', 'username': 'shuvalov-mdb'}

Message: SERVER-67022 forced step down and then up should not depend on timing
Branch: master
https://github.com/mongodb/mongo/commit/512400836de867eb4cccfb226159b3f721c792e5

Comment by Githook User [ 07/Jun/22 ]

Author:

{'name': 'Andrew Shuvalov', 'email': 'andrew.shuvalov@mongodb.com', 'username': 'shuvalov-mdb'}

Message: SERVER-67022 relax tight timeout in test
Branch: master
https://github.com/mongodb/mongo/commit/be3cfbd6d6c195f0179066b111a39291f0f15df7

Comment by Max Hirschhorn [ 03/Jun/22 ]

We should see about using a more reliable procedure like the approach taken in SERVER-51810 to step down the current primary and have it step back up shortly thereafter.

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