-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Internal Code
-
Server Programmability
-
ALL
-
Service Arch 2022-06-13, Service Arch 2022-06-27, Service Arch 2022-07-11
-
145
Originally reported by matthew.saltz@mongodb.com: I'm not sure if this actually leads to a bug or not, but since we rely on the AsyncWorkScheduler to shut down transaction coordinators, it might be a problem that we also do work on the Grid's fixed executor. We should investigate whether this is a problem and then fix it if it is.
- depends on
-
SERVER-54206 Create a non-blocking API for the Fetcher class (or create an alternate class)
- Closed
-
SERVER-57292 Introduce onStepDown cancelation token to fix shutdown memory leak
- Closed
- related to
-
SERVER-67732 mongod shutdown procedure doesn't shutdown the Grid::getExecutorPool()
- Closed
-
SERVER-58487 Join TransactionCoordinatorService stepdown tasks during shutdown
- Closed
- split from
-
SERVER-51317 Change TransactionCoordinator to use executor from AsynchWorkScheduler
- Closed