[SERVER-8490] Hashed Sharding numInitialChunks option produces inconsistant results Created: 08/Feb/13 Updated: 15/Feb/13 Resolved: 11/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Osmar Olivo | Assignee: | Randolph Tan |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
When dealing with higher number of shards(5+) the actual number of chunks produced does not coincide with the value passed into numInitialChunks. When it fails, it is generally less than the numInitialChunks value (I have yet to see it be higher). A test script proving this is attached. This test will go into an infinite loop on failure but produces useful information in it's output about the state of the system at that time. |