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

Update the stale comment in TenantMigrationRecipientOpObserver::aboutToDelete()

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.1.0-rc0
    • None
    • None
    • Fully Compatible
    • Server Serverless 2022-07-11

    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.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: