[SERVER-8347] Cannot move min chunk on hashed shard key Created: 25/Jan/13 Updated: 09/Jul/16 Resolved: 25/Jan/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.3.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Comments |
| Comment by Randolph Tan [ 25/Jan/13 ] |
|
moveChunk for hash shard keys should use bounds instead of find -> this should be documented if not yet. |
| Comment by Randolph Tan [ 25/Jan/13 ] |
|
Note: same problem also exist with the max shard (just change sort order to the opposite direction on the test script). |
| Comment by Randolph Tan [ 25/Jan/13 ] |
|
Attached test file. Running the test file would result in: Cmd failed: { "ok" : 0, "errmsg" : "that chunk is already on that shard" } |