[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:
Backports
Depends
Related
is related to SERVER-48650 Unit tests' ServiceContext's NetworkI... Closed
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: SERVER-47892 DiagnosticInfo should use Client to acquire timestamps
Branch: v4.4
https://github.com/mongodb/mongo/commit/0f7e57d419dc95323ed25c1d70e9368bfce8ea30

Comment by Githook User [ 13/Jul/20 ]

Author:

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

Message: SERVER-47892 DiagnosticInfo should use Client to acquire timestamps
Branch: master
https://github.com/mongodb/mongo/commit/dbc867c4cfdadac4503658060c0a17a7cc249bbc

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