[SERVER-8489] Hashed Sharding pre-splitting behavior not to spec Created: 08/Feb/13  Updated: 11/Jul/16  Resolved: 11/Feb/13

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.4.0-rc0
Fix Version/s: 2.4.0-rc1

Type: Bug Priority: Critical - P2
Reporter: Osmar Olivo Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File server-8489.js    
Issue Links:
Depends
Duplicate
is duplicated by SERVER-8490 Hashed Sharding numInitialChunks opti... Closed
Operating System: ALL
Participants:

 Description   

1. Hashed pre-splitting behavior does not work when there is only 1 shard. If you have 1 shard instead of following the default and having 2 chunks it is 0. Furthermore, if you specify numInitialChunks to be a value, the value is completely ignored and again defaults to 0 chunks. In short, the spec is not followed if there is 1 shard and it is not documented as such.



 Comments   
Comment by auto [ 11/Feb/13 ]

Author:

{u'date': u'2013-02-11T22:42:00Z', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-8489 Hashed Sharding pre-splitting behavior not to spec
Branch: master
https://github.com/mongodb/mongo/commit/55653fa1a3a256f96d2098ffcad97eedab49fd56

Comment by Daniel Pasette (Inactive) [ 08/Feb/13 ]

Attached test case. Fails when there is a single shard.

Generated at Thu Feb 08 03:17:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.