[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: |
|
||||||||||||||||||||||||
| 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: |