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

Multiple concurrent migration recoveries after step-up can race for the fixed Lsid/TxnNumber

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: Sharding
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2020-08-10

      Description

      All MigrationCoordinator(s) started from a single MongoD instance share the same logical session id for any operations that they perform (for the lifetime of that instance). Because of this, it is never correct that two migration coordinators exist at the same time.

      Under normal circumstances, this is guaranteed by the acquisition of the MigrationBlockingGuard at the beginning of each migration. However, in the case where an incomplete migration needs to be recovered, we don't take it. Because of this, it is possible that a migration for a completely unrelated collection can start while a different collection is still running recovery.

        Attachments

          Activity

            People

            Assignee:
            kaloian.manassiev Kaloian Manassiev
            Reporter:
            kaloian.manassiev Kaloian Manassiev
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: