[SERVER-47892] DiagnosticInfo for latches doesn't integrate well with unit-tests which create and destroy ServiceContexts Created: 01/May/20 Updated: 29/Oct/23 Resolved: 13/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.0-rc3 |
| Fix Version/s: | 4.4.1, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | servicearch-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||
| Sprint: | Service arch 2020-06-29, Service arch 2020-07-13 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
AuthorizationManager owns a ThreadPool (see here) that is stopped/deleted at the end of the its lifetime. It also holds a reference to the ServiceContext, which is reset in here before the ServiceContext is deleted. Since the ThreadPool outlives ServiceContext, and it can schedule tasks that manage opCtxs locally (see here for example), AuthorizationManager should stop the ThreadPool before ServiceContext is deleted. |
| Comments |
| Comment by Githook User [ 18/Aug/20 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: |
| Comment by Githook User [ 13/Jul/20 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: |