Remove 3.2 shard compatibility from MigrationManager in 3.6

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding
    • Sharding 2018-02-26
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: