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

MigrationManager::finishRecovery will attempt and fail to remove migration documents, which is good, but it shouldn't be trying

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding
    • Sharding 2017-01-02

    Description

      This isn't causing any issues, because when the MigrationManager is interrupted the write will fail. But it shouldn't do it.

      When the finishRecovery waits for the moveChunk commands to finish here, it should check the error code and run ScopedMigrationRequest::keepDocumentOnDestruct.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: