[SERVER-67077] TransactionCoordinator uses both the Grid fixed executor and the executor on the AsyncWorkScheduler Created: 07/Jun/22  Updated: 06/Dec/22

Status: Open
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Amirsaman Memaripour Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-54206 Create a non-blocking API for the Fet... Closed
depends on SERVER-57292 Introduce onStepDown cancelation toke... Closed
Issue split
split from SERVER-51317 Change TransactionCoordinator to use ... Closed
Related
related to SERVER-67732 mongod shutdown procedure doesn't shu... Closed
related to SERVER-58487 Join TransactionCoordinatorService st... Closed
Assigned Teams:
Service Arch
Operating System: ALL
Sprint: Service Arch 2022-06-13, Service Arch 2022-06-27, Service Arch 2022-07-11
Participants:
Linked BF Score: 145

 Description   

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.


Generated at Thu Feb 08 06:07:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.