[SERVER-25015] Sharding balancer does not correctly obey tag ranges, which end in MaxKey Created: 12/Jul/16 Updated: 19/Jul/16 Resolved: 14/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.8, 3.3.9 |
| Fix Version/s: | 3.3.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 17 (07/15/16) |
| Participants: |
| 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. |
| Comments |
| Comment by Githook User [ 14/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: Also, tighten the assertions and enhance unit-testing. |