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

MoveChunk should recover any unfinished migration before starting a new one

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.3.0, 5.1.2, 5.0.6, 5.2.0-rc4
    • Sharding
    • None
    • Fully Compatible
    • v5.2, v5.1, v5.0
    • Sharding EMEA 2022-01-10

    Description

      When starting a moveChunk, it should be ensured that there is no unfinished migration pending recovery (even for other collections). Ensuring that will guarantee that there's never more than one document in config.migrationCoordinators. 

      This prevents the situation that led to SERVER-62245.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. SERVER-65371 MigrationSourceManager running on secondary node may trip invariant

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-62245 MigrationRecovery must not assume that only one migration needs to be recovered

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-60521 Deadlock on stepup due to moveChunk command running uninterrupted on secondary

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              jordi.serra-torrens@mongodb.com Jordi Serra Torrens
              jordi.serra-torrens@mongodb.com Jordi Serra Torrens
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: