[SERVER-54349] Run st.configRS.awaitReplication() before running replSetStepUp in sharded_index_consistency_metrics.js Created: 05/Feb/21  Updated: 29/Oct/23  Resolved: 05/Feb/21

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: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-02-08
Participants:
Linked BF Score: 10

 Description   

It's possible that st.config1's lastApplied opTime is behind the lastApplied opTime of the other config server nodes, and that would cause replSetStepUp to fail the dry-run election. To ensure that the command succeeds, we need to run st.configRS.awaitReplication() right before running replSetStepUp just like in ReplSetTest.stepUp.



 Comments   
Comment by Githook User [ 05/Feb/21 ]

Author:

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

Message: SERVER-54349 Run st.configRS.awaitReplication() before running replSetStepUp in sharded_index_consistency_metrics.js
Branch: master
https://github.com/mongodb/mongo/commit/5ee73f447aaa1e1b9503aff6ff031f240708c711

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