[SERVER-67322] Update the stale comment in TenantMigrationRecipientOpObserver::aboutToDelete() Created: 15/Jun/22  Updated: 29/Oct/23  Resolved: 07/Jul/22

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

Type: Task Priority: Major - P3
Reporter: Suganthi Mani Assignee: Christopher Caplinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-67334 Accessing the opCtx decoration 'tenan... Closed
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2022-07-11
Participants:

 Description   

This comment is misleading and it's not entirely true. We create recipient tenant access blocker at the start of the migration (i,e state doc state is 'kStarted') and not just after the cloning phase completes. But, if the recipient primary receives a recipientForgetMigration before recipientSyncData cmd, we start the instance with state as kDone to avoid creating unnecessary access blocker for the tenant. In such cases, mtab might not present for the tenant while deleting that state document.



 Comments   
Comment by Christopher Caplinger [ 28/Jun/22 ]

will handle this as part of https://jira.mongodb.org/browse/SERVER-65820

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