[SERVER-69094] Clean up TenantMigrationRecipientAccessBlockerRegistry Created: 23/Aug/22  Updated: 29/Oct/23  Resolved: 28/Sep/22

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

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

Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2022-09-05, Server Serverless 2022-09-19, Server Serverless 2022-10-03
Participants:

 Description   

shard merge has started polluting TenantMigrationAccessBlockerRegistry and made the API a bit confusing. TenantMigrationAccessBlockerRegistry should expose APIs that are generic to donor and recipient. And, tenant_migration_access_blocker_util.cpp will have (if actually needed... we should evaluate how useful these specific util methods actually are) recipient or donor specific methods, like getTenantMigrationRecipientAccessBlocker().

Additionally, we should clean up the singleton shard merge donor access blocker (donorAccessBlocker) in favor of using the existing map of tenant id-to-access blocker with some sort of special DONOR_ key.



 Comments   
Comment by Githook User [ 28/Sep/22 ]

Author:

{'name': 'Christopher Caplinger', 'email': 'christopher.caplinger@mongodb.com', 'username': 'UnicodeSnowman'}

Message: SERVER-69094: Clean up TenantMigrationRecipientAccessBlockerRegistry
Branch: master
https://github.com/mongodb/mongo/commit/8c39533bc7af757abc5247870a7863beee4f8f88

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