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.
Sharding balancer does not correctly obey tag ranges, which end in MaxKey
- Assignee:
-
Kaloian Manassiev
- Reporter:
-
Kaloian Manassiev
- Votes:
-
0 Vote for this issue - Watchers:
-
4 Start watching this issue
- Created:
- Updated:
- Resolved: