[SERVER-51810] Make sure the donor primary can step down reliably in tenant_migration_donor_resume_on_stepup_and_restart.js Created: 22/Oct/20  Updated: 29/Oct/23  Resolved: 22/Oct/20

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

Type: Bug Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-11-02
Participants:
Linked BF Score: 11

 Description   

The test currently runs replSetStepDown with a short stepdownTime of 1 second to 
make it more likely for the old primary to step back up. However, if the old primary spends more than 1 second to kill background operations while stepping down, the replSetStepdown will fail with LockTimeout since when force: true, the stepdownTime is the lock timeout for the RSTL (ReplicationStateTransition lock). To avoid this error, we should instead run replSetStepDown with stepdownTime of ReplSetTest.kForeverSecs and immediately then run a

{replSetFreeze: 0}

command so the old primary is immediately eligible to step back up. 



 Comments   
Comment by Githook User [ 22/Oct/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}

Message: SERVER-51810 Make sure the donor primary can step down reliably in tenant_migration_donor_resume_on_stepup_and_restart.js
Branch: master
https://github.com/mongodb/mongo/commit/8a959d0af935d5dcca6a8e573f1f74e0b6be7b2b

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