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

Remove 3.2 shard compatibility from MigrationManager in 3.6

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Minor - P4 Minor - P4
    • None
    • None
    • Sharding
    • Sharding
    • Sharding 2018-02-26

    Description

      This should simplify the MigrationManager logic.

      There is probably some clean up that could happen on the MigrationSourceManager, as well, like the takeDistLock parameter in the shard moveChunk command.

      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:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: