[SERVER-68799] Fix recipient service access blocker logic for shard merge Created: 12/Aug/22  Updated: 27/Oct/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: Christopher Caplinger Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Gone away Votes: 0
Labels: shard-merge-milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-74613 Complete TODO listed in SERVER-68799 Closed
related to SERVER-74802 Complete TODO listed in SERVER-68799 Closed
Assigned Teams:
Serverless
Operating System: ALL
Sprint: Server Serverless 2022-08-22
Participants:

 Description   

see https://github.com/10gen/mongo/blob/4a3d3611873d1aab173aedf58947d76b6206db1a/src/mongo/db/repl/tenant_migration_recipient_service.cpp#L2729-L2748

on L2729-L2731, we call getTenantMigrationRecipientAccessBlocker with stateDoc.getTenantId(). For shard merge, tenant id here will be empty. as such we are not actually cleaning up the access blocker from the previous migration attempt.



 Comments   
Comment by Suganthi Mani [ 03/Mar/23 ]

After, SERVER-73397 is no longer needed.

Comment by Suganthi Mani [ 29/Aug/22 ]

christopher.caplinger@mongodb.com Please wait until milestone3 design gets approved for this ticket.

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