[SERVER-49456] Race between auto reconfig and stepUp command in dont_read_oplog_hole_on_step_up.js Created: 10/Jul/20  Updated: 29/Oct/23  Resolved: 10/Jul/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.7.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
Participants:
Linked BF Score: 0

 Description   

The auto reconfig to remove the "newlyAdded" field from the config for the newly added third node (node 2) could interfere with the stepUp command issued to node 1, ending up failing the stepUp with "Not standing for election; processing a configuration change"



 Comments   
Comment by Githook User [ 10/Jul/20 ]

Author:

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

Message: SERVER-49456: wait for newlyAdded fields removals before stepUp in dont_read_oplog_hole_on_step_up.js
Branch: master
https://github.com/mongodb/mongo/commit/6653bf6dea2d03fa7075c56a19345804040440a9

Comment by Lingzhi Deng [ 10/Jul/20 ]

Ah, nice, I didnt know that helper exists. It should be an easy fix then, thanks.

Comment by Judah Schvimer [ 10/Jul/20 ]

I think we just need to call waitForAllNewlyAddedRemovals() after reInitiate().

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