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
- is duplicated by
-
SERVER-14313 Warn if numInitialChunks used for shardCollection on non-empty collection
- Closed