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

Sharding balancer does not correctly obey tag ranges, which end in MaxKey

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.8, 3.3.9
    • Fix Version/s: 3.3.10
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 17 (07/15/16)

      Description

      If a tag includes MaxKey as the max key, the logic in BalancerPolicy::getTagForChunk will misidentify the tag in which a chunk should go in certain cases. We should fix this and tighten the unit-tests around it.

        Attachments

          Activity

            People

            Assignee:
            kaloian.manassiev Kaloian Manassiev
            Reporter:
            kaloian.manassiev Kaloian Manassiev
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: