shard maxSize does not support draining well

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.2.2, 2.3.1
    • Affects Version/s: 2.2.1
    • Component/s: None
    • None
    • Minor Change
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When a shard exceeds it's maxSize, by having more data mapped than is specified in config.shards::maxSize, the shard immediately starts draining as the first priority of the balancer. Mapped is a poor substitute in this case for shards.

            Assignee:
            Greg Studer (Inactive)
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: