Fix recipient service access blocker logic for shard merge

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Serverless
    • ALL
    • Server Serverless 2022-08-22
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Server Serverless (Inactive)
              Reporter:
              Christopher Caplinger
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: