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

MigrationDestinationManager should not blindly dereference _sessionMigration on recovery error handling

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.3.0
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Show
      repro-server-62701.patch
    • Sharding EMEA 2022-01-24
    • 0

    Description

      If a new migration recipient primary steps-up and then fails (e.g. stepsdown too) during migration recovery, indeed _migrateThread will throw. On cleanup, it will dereference _sessionMigration, which if that node instance had never been the recipient of a migration, will be nullptr.
      It is fine that _sessionMigration is nullptr on recovery. We should just not blindly dereference it in the error handling path.

      Attachments

        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: