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

Make moveChunk robust to being killOp'd after commit has been sent to the config but before the node has found out the commit decision

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.4
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2020-02-10

    Description

      Currently, if the MigrationSourceManager's thread is killOp'd after commit has been sent to the config but before this node has found out the decision, then the range deletion tasks and migration coordinator doc won't be updated.

      This is because _cleanup won't set an abort decision on the MigrationCoordinator, and _cleanup will call MigrationCoordinator::completeMigration without a decision having been set, which will just log an error and return without doing anything.

      Attachments

        Activity

          People

            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: