balancer ignoring maxSize setting?

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Minor - P4
    • None
    • Affects Version/s: 3.2.12
    • Component/s: Sharding
    • None
    • ALL
    • Hide

      Initial setup.
      Two shards: shard1 and shard2
      shard1 with maxSize A, already full.
      shard2 without maxSize.

      1. change maxSize of shard1 to A/2
      2. use moveChunks to move chunks from shard1 to shard2 until in getShardDistribution() you get A/2 of usage.
      3. compact shard1 to free disk space.

      After that the load balancer will start moving from shard2 to shard1 until 'A' size is reached, even if maxSize was changed to A/2.

      Show
      Initial setup. Two shards: shard1 and shard2 shard1 with maxSize A, already full. shard2 without maxSize. 1. change maxSize of shard1 to A/2 2. use moveChunks to move chunks from shard1 to shard2 until in getShardDistribution() you get A/2 of usage. 3. compact shard1 to free disk space. After that the load balancer will start moving from shard2 to shard1 until 'A' size is reached, even if maxSize was changed to A/2.
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      maxSize setting is ignored by the balancer.
      I think, (but I'm not sure), that after than update in the maxSize setting, one has to restart the loadbalancer so that it reads the new maxSize setting.
      If this is true, then is not reflected in the documentation.

      When does the balancer get notified of a maxSize change?

            Assignee:
            Randolph Tan
            Reporter:
            Crimson Glory
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: