[SERVER-68159] Tenant migration recipient needs to interrupt all operations on recipientForgetMigration Created: 19/Jul/22  Updated: 04/Aug/23  Resolved: 03/Mar/23

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

Type: Bug Priority: Major - P3
Reporter: Mathis Bessa Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Duplicate Votes: 0
Labels: shard-merge-milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-76750 Make import quorum wait Interruptible... Closed
Related
related to SERVER-68192 Skip opening the backup cursor  on mi... Closed
related to SERVER-68195 Improve logging in TenantFileImporter... Closed
related to SERVER-74618 Complete TODO listed in SERVER-68159 Closed
is related to SERVER-68156 Do not run ShardMerge protocol on ten... Closed
Assigned Teams:
Serverless
Operating System: ALL
Participants:
Linked BF Score: 149

 Description   

We should make sure to set the _importedFilesPromise when the shard merge is interrupted when receiving "recipientForgetMigration" command from the donor if the shard merge has not yet finished (the shard merge wasn't waiting yet for the forget command)

We can add a new test to cover the fact that after a shard merge is interrupted during _waitForOplogApplierToStop due to a step up on a recipient secondary. After the step up calling `forgetMigration` on the donor should no longer hang (just like in this test for example)

Part of this change should also to address the existing test that was just mentioned. We should no longer use the tag `incompatible_with_shard_merge` within that test.

 


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