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

Add an upper bound for how long a tenant migration donor can block operations

    XMLWordPrintable

Details

    • Fully Compatible
    • Sharding 2020-12-14, Sharding 2020-12-28, Sharding 2021-01-11, Sharding 2021-01-25

    Description

      We decided at the 6 week review that the donor should bound how long it blocks operations.

      This is useful in general to limit the impact of a tenant migration on a user workload, but in particular is useful in case the donor starts blocking very soon after writing a commitIndexBuild oplog entry. This is because the recipient will not start building the index until seeing commitIndexBuild in the oplog; will not report that it has majority-committed the commitIndexBuild oplog entry until finishing building the index; and building the index can take a long time (hours).

      suganthi.mani or matthew.russotto , could you confirm that this is the plan for how the recipient will handle two-phase index builds?

      evin.roesle, could you propose a default upper bound for how long the donor should block operations? The upper bound should be settable via a server parameter.

      Attachments

        Issue Links

          Activity

            People

              andrew.shuvalov@mongodb.com Andrew Shuvalov
              esha.maharishi@mongodb.com Esha Maharishi
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: