[SERVER-46419] Expand AlarmScheduler to work with ReactorTimers Created: 26/Feb/20  Updated: 24/Aug/23  Resolved: 24/Aug/23

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

Type: New Feature Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Backlog - Service Architecture
Resolution: Declined Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-45117 Guard NetworkInterfaceTL::setAlarm() ... Closed
Assigned Teams:
Service Arch
Participants:

 Description   

The AlarmScheduler is potentially a powerful interface we can hook up to the ReactorTimer. We might be able to potentially expose the background thread alarm scheduler as a ServiceContext decoration to provide more generic alarm functionality throughout the system.



 Comments   
Comment by Lauren Lewis (Inactive) [ 21/Dec/21 ]

We haven’t heard back from you in at least 1 year, so I'm going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Comment by Githook User [ 26/Feb/20 ]

Author:

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

Message: SERVER-45117 Guard NetworkInterfaceTL::setAlarm() more aggressively

The underlying issue is that NetworkInterfaceTL::_state and
NetworkInterfaceTL::_inProgressMutex do not synchronize with each other.
This is at best a temporary fix. Reasoning about alarm ordering in the
context of the NetworkInterface itself is messy. This approximates what
a proper composible AlarmScheudler type looks like. Hopefully, there
will be more consistent work under SERVER-46419.
Branch: master
https://github.com/mongodb/mongo/commit/57f6385025adf630a410f9d658f61b5afd140121

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