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

Sharding balancer schedules multiple migrations with the same conflicting source or destination

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.11, 3.6.3, 3.7.2
    • Affects Version/s: 3.4.4
    • Component/s: Sharding
    • Labels:
    • Fully Compatible
    • ALL
    • v3.6, v3.4
    • Sharding 2018-01-29

      The sharding balancer policy avoids producing multiple migrations for the same shard.

      However, the policy runs per collection and doesn't save any state across collections. Because of this, if there are multiple collections which need balancing, it may produce overlapping shards.

      There is no correctness problem with this, but it will cause useless ConflictingOperationInProgress errors to pollute the config server and shard's logs on each balancer round.

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            4 Vote for this issue
            24 Start watching this issue