-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
Sharding 2021-07-12, Sharding 2021-07-26, Sharding 2021-08-09, Sharding 2021-08-23, Sharding 2022-03-07, Sharding NYC 2022-03-21, Sharding NYC 2022-04-04, Sharding NYC 2022-04-18, Sharding 2022-05-02, Sharding NYC 2022-05-16, Sharding NYC 2022-05-30, Service Arch 2022-06-13
-
5
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.
This ticket changes TransactionCoordinator to use the executor from AsynchWorkScheduler. The above is tracked by SERVER-67077.
- split to
-
SERVER-67077 TransactionCoordinator uses both the Grid fixed executor and the executor on the AsyncWorkScheduler
- Open