[SERVER-48363] dont_read_oplog_hole_on_step_up should wait for new primary after stepUp Created: 21/May/20  Updated: 29/Oct/23  Resolved: 29/May/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.4.0-rc8, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Gregory Wlodarek
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:
v4.4
Sprint: Execution Team 2020-06-15
Participants:
Linked BF Score: 18

 Description   

Instead of stepping-up and immediately asserting the new primary has transitioned, we should replace the assertion with a waitForState that gives the node time to fully-transition.



 Comments   
Comment by Githook User [ 29/May/20 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-48363 dont_read_oplog_hole_on_step_up.js should wait for new primary after stepping up

(cherry picked from commit 1c09f3f2a6736d183058ab38519f6675c14f7efc)
Branch: v4.4
https://github.com/mongodb/mongo/commit/7ee8a2e319267008cd2c720ceb2e841b186f4769

Comment by Githook User [ 29/May/20 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-48363 dont_read_oplog_hole_on_step_up.js should wait for new primary after stepping up
Branch: master
https://github.com/mongodb/mongo/commit/1c09f3f2a6736d183058ab38519f6675c14f7efc

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