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

Investigate presence of multiple migration coordinator documents

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 5.0.5, 5.1.1
    • Component/s: None
    • None
    • Sharding EMEA 2021-12-27

      It has been observed on a cluster the presence of 4 migration coordinator documents on one shard that led to hit this invariant on step-up.

      The documents were all relative to migrations for different namespaces and the states were:

      • 2 aborted
      • 1 committed
      • 1 without decision

      The range deletions seemed to have been correctly handled both on donor and recipients:

      • No range deletion documents for the aborted migrations (range deletion tasks already executed)
      • Ready range deletion task on the donor for the committed migration
      • Pending range deletions on donor/receiver for the migration without decision

      Given the state of "decided" migrations, we can consider that:

      It is then very likely that something odd happened right after, as part of the call to forgetMigration that did not remove the migration coordinators.

            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            0 Vote for this issue
            4 Start watching this issue