[SERVER-9690] SplitVector fails to find the mid-point of a chunk Created: 15/May/13 Updated: 10/Dec/14 Resolved: 05/Jun/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.2.4, 2.4.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Weibull | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
SplitVector fails to find the mid-point of a chunk if it is forced and there are more than 250000 records in the chunk. To test this run the following from the mongo shell: > use test );} ) > db.adminCommand({"splitVector": "test.col", "keyPattern": {i:1}, "min": {i:0}, "max": {i: 250001}, force: true}) it will output something like this: {"timeMillis" : 81, "splitKeys": [ {"i": 250000}], "ok": 1} so the split point it suggests is the record just before the last one, which is pretty far from the middle. |
| Comments |
| Comment by David Weibull [ 15/May/13 ] |
|
This is related to https://jira.mongodb.org/browse/SERVER-9498 |