[SERVER-79192] Fix migration_coordinator_commit_failover.js to use awaitReplicationBeforeStepUp: false Created: 21/Jul/23  Updated: 07/Feb/24  Resolved: 06/Feb/24

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.6, 8.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Vishnu Kaushik Assignee: Huayu Ouyang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: Repl 2023-07-24, Repl 2023-08-07, Repl 2023-08-21, Repl 2023-09-04, Repl 2023-09-18, Repl 2023-10-02, Repl 2023-10-16, Repl 2023-10-30, Repl 2023-11-13, Repl 2023-11-27, Repl 2023-12-11, Repl 2024-01-08, Repl 2024-02-05, Repl 2024-02-19
Participants:
Linked BF Score: 7

 Description   

Since this method is called in a period when there isn't a primary, when the default value of this flag is used (true), the method ends up waiting for a primary to appear first instead of stepping up the passed in node.

See comments for more info.



 Comments   
Comment by Githook User [ 07/Feb/24 ]

Author:

{'name': 'huayu-ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}

Message: SERVER-79192 Fix migration_coordinator_failover_include.js to freeze and unfreeze primary (#18669)

(cherry picked from commit 6bbb8fa55ff198a56c61153b5676ee1a131d13a0)

GitOrigin-RevId: 9e5ae5b6a641b14ef01739f6c2834a7aea171b54
Branch: v7.0
https://github.com/mongodb/mongo/commit/68d0453ad1df065eea5d048efb4d1d16a6119c7c

Comment by Githook User [ 05/Feb/24 ]

Author:

{'name': 'huayu-ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}

Message: SERVER-79192 Fix migration_coordinator_failover_include.js to freeze and unfreeze primary (#18669)

GitOrigin-RevId: 6bbb8fa55ff198a56c61153b5676ee1a131d13a0
Branch: master
https://github.com/mongodb/mongo/commit/40c8c5638477b043a4739ac0529443b38173ce0c

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