[SERVER-64302] Improve cancellation for tenant migration recipient. Created: 07/Mar/22  Updated: 04/Oct/23  Resolved: 04/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Suganthi Mani Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-57991 Architecture Guide updates for PM-2353 Closed
Assigned Teams:
Serverless
Participants:

 Description   

Currently, for some async task in tenant migration recipient, we passĀ CancellationToken::uncancelable(), like this. This implies, we aren't canceling the async tasks using CancellationToken, instead we currently relying on shutting down the_scopedExecutor to interrupt those tasks. Investigate whether we can improve the cancellation using cancelation token for tenant migration recipient, just like we did for donor (see SERVER-55780)



 Comments   
Comment by Didier Nadeau [ 04/Oct/23 ]

Closing as we're planning to remove TMRS in the short term.

Comment by Suganthi Mani [ 09/Mar/22 ]

Note: As part of this ticket, check if we can improve the cancellation design for tenant migration (donor & recipient) by using class CancelableOperationContextFactory

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