Ensure that resumeMigrationCoordinationsOnStepUp() does not interfere with ongoing migrations

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding EMEA
    • ALL
    • 135
    • None
    • None
    • None
    • None
    • None
    • None
    • None

       SERVER-64979 introduce a change to make the execution of resumeMigrationCoordinationsOnStepUp() asynchronous.
      This may raise issues if the resumed migrations concerns collections that are currently being involved in R/W operations or chunk migration requests, since such function contains logic to invalidate the collection filtering metadatata.

      (One example is the activation of this invariant, as observed in BF-24833).

            Assignee:
            [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: