-
Type: Task
-
Resolution: Done
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: Server
-
Labels:None
Currently if a user shards a collection and includes numInitialChunks without a hashed shard key, everything will succeed but the initial chunks value will be ignored. The user in this case could be rightly confused as to what has happened, and reviewing the logs will only indicate that "numChunks : 1".
Suggest a warning be given that numInitialChunks is being ignored in these cases
- documents
-
SERVER-23327 shardCollection should warn if numInitialChunks is used with non-hashed sharded key
- Closed