[SERVER-67523] Must clear _nextCall on reschedule failure in delayable_timeout_callback Created: 24/Jun/22  Updated: 29/Oct/23  Resolved: 29/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.1, 5.0.11, 6.1.0-rc0

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:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2022-07-11
Participants:
Linked BF Score: 153

 Description   

The invariant is that _nextCall should be clear (Date_t()) when no call is scheduled; if a reschedule fails when _nextCall has already been set, that is violated.



 Comments   
Comment by Githook User [ 29/Jun/22 ]

Author:

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

Message: SERVER-67523 Must clear _nextCall on reschedule failure in delayable_timeout_callback
Branch: master
https://github.com/mongodb/mongo/commit/87d6ec40779e3750a123efd941e16d159bf938bb

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