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

Support back-to-back migration of the same tenant

    XMLWordPrintable

Details

    • Fully Compatible
    • v4.9
    • Repl 2021-04-05, Repl 2021-04-19

    Description

      It looks like there is a case where we need both a donor and recipient TenantMigrationAccessBlocker.  This is when we do a successful migration of A->B, then immediately (before the garbage collection period has elapsed) do a migration of B->C.  The migration B->C currently would fail due to conflicting migration errors (until after the garbage collection period). We can handle this by

      1. Immediately GCing the recipient mtab (but this opens up old reads)
        • We could instead¬†replace the recipient mtab with a donor mtab (with a special flag?) that also block old reads
      2. Combining the two access blockers
      3. Allowing both to exist simultaneously

      But before we do any of these, we should confirm with Cloud on whether this is something Cloud is expected to do.

      Attachments

        Issue Links

          Activity

            People

              jason.chan@mongodb.com Jason Chan
              lingzhi.deng@mongodb.com Lingzhi Deng
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: