Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-69094

Clean up TenantMigrationRecipientAccessBlockerRegistry

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Server Serverless 2022-09-05, Server Serverless 2022-09-19, Server Serverless 2022-10-03

    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.

      Attachments

        Activity

          People

            christopher.caplinger@mongodb.com Christopher Caplinger
            christopher.caplinger@mongodb.com Christopher Caplinger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: