-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Internal Code
-
None
-
Service Arch 2021-02-22, Service Arch 2021-03-08
-
2
This ticket is to investigate SERVER-52750 to see whether there are certain PrimaryOnlyServices that rely on the ScopedTaskExecutor shutdown for cleanup rather than using CancelationTokens, and if so, to create tickets to modify that functionality to use CancelationTokens instead so that we can do SERVER-52750.
- depends on
-
SERVER-54932 Modify BaseCloner to accept a cancellation token in its runOnExecutorEvent method
- Backlog
-
SERVER-54933 AbstractAsyncComponent should support cancellation semantics
- Backlog
-
SERVER-54934 Modify ReshardingCoordinatorService to support cancellation using the CancellationToken framework
- Backlog
-
SERVER-54943 Modify Resharding{Recipient|Donor}Service to support cancellation using the CancellationToken framework
- Backlog
-
SERVER-54931 AsyncRequestsSender should be modified to accept and support cancellation tokens
- Closed
-
SERVER-53389 TenantMigration{Donor, Recipient}Service should use it's base PrimaryOnlyService's cancelation source to pass tokens in calls to WaitForMajorityService::waitUntilMajority
- Backlog
-
SERVER-53931 Investigate how to cancel recipients cloning/applying in resharding
- Closed