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

MigrationManager can keep a migration document when not in stepdown / shutdown because it can't differentiate between its own error codes and those of the shard with which it communicates

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.0-rc1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2016-10-10, Sharding 2016-10-31
    • 0

      The Balancer will keep config.migrations documents on shard stepdown / shutdown errors. And return BalancerInterrupted to the mongos, though it isn't stepping down. The mongos will retry the moveChunk command, so it doesn't appear to be a big problem, though it isn't what we intended to happen / really want.

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: