[SERVER-39513] NetworkInterface::setAlarm should be cancellable Created: 11/Feb/19  Updated: 29/Oct/23  Resolved: 27/Feb/19

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

Type: Bug Priority: Major - P3
Reporter: Mira Carey Assignee: Benjamin Caimano (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-39479 Increase number of executions in "Lin... Closed
Duplicate
is duplicated by SERVER-39570 Separate NITP::consumeTasks into an e... Closed
Problem/Incident
causes SERVER-51337 use-after-move in NetworkInterfaceMock Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Service Arch 2019-02-25, Service Arch 2019-03-11
Participants:
Linked BF Score: 7

 Description   

The NetworkInterface::setAlarm method isn't cancellable, while TaskExecutor::scheduleWorkAt is.

And because scheduleWorkAt wraps setAlarm, this causes patterns that repeatedly schedule work and then cancel it to slowly accumulate many many timers that eventually time out.



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

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-39513 NetworkInterface::setAlarm should be cancellable
Branch: master
https://github.com/mongodb/mongo/commit/6403ca518b832a49d66352620a23606348595fac

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