mongodb/mongo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

SERVER-113508 Should wait for old primary to complete stepdown in auto_reconfig_remove_newly_added_and_stepdown.js (#43616) (#46364)

Browse Source 
GitOrigin-RevId: c9af51a3bb367249a76c2de58a0780e9958d826d
This commit is contained in:
Moustafa Maher 2026-01-16 06:57:07 -08:00 committed by MongoDB Bot
parent 455604a26c
commit 35bac269ba
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
jstests/replsets/auto_reconfig_remove_newly_added_and_stepdown.js
View File

@ -81,4 +81,8 @@ jsTestLog("Proceeding with newlyAdded field removal");
checkLog.contains(primary, 'Safe reconfig rejected due to detected pending stepdown');
checkLog.containsJson(nodes[1], 4634504, {"memberId": 3});
blockHeartbeatStepdownFailPoint.off();
rst.stopSet();
// Wait for the old primary to fully step down, transition to a secondary, and catch up. This
// ensures it won't enter a rollback state when validation runs during the 'stopSet' procedure.
rst.awaitSecondaryNodes();
rst.awaitReplication();
rst.stopSet();