[SERVER-53677] Stepping up secondaries could fail in tenant_migration_resume_collection_cloner_after_recipient_failover.js Created: 08/Jan/21  Updated: 29/Oct/23  Resolved: 12/Jan/21

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

Type: Bug Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
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
Sprint: Repl 2021-01-25
Participants:
Linked BF Score: 18

 Description   

If the secondary node we are stepping up is lagged, running replSetStepUp on it could fail because it is not able to get votes. I think we should call recipientRst.awaitLastOpCommitted() before stepping up a secondary node.



 Comments   
Comment by Githook User [ 12/Jan/21 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-53677: Call recipientRst.awaitLastOpCommitted() before stepping up a secondary node in tenant_migration_resume_collection_cloner_after_recipient_failover.js
Branch: master
https://github.com/mongodb/mongo/commit/3b8ae3847dc7021ed231c96a891d14fc6ed7d1a6

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