[SERVER-39328] Ensure unacked write starts and finishes before stepping down in last_error_reported_after_stepdown Created: 01/Feb/19  Updated: 29/Oct/23  Resolved: 11/Feb/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.1.8

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Matthew Russotto
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: Repl 2019-02-11, Repl 2019-02-25
Participants:
Linked BF Score: 19

 Description   

The last_error_reported_after_stepdown test currently waits for the operation to not be in progress. However, this allows for a race where the operation hasn't actually started by the time we check for it. We need to wait for it to definitely start, then definitely end, before stepping down.



 Comments   
Comment by Githook User [ 11/Feb/19 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@10gen.com', 'username': 'mtrussotto'}

Message: SERVER-39328 Ensure unacked write starts and finishes before stepping down in last_error_reported_after_stepdown
Branch: master
https://github.com/mongodb/mongo/commit/dc5efe65414ed7cb68049d67681afc590f23c7a1

Generated at Thu Feb 08 04:51:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.