[DOCS-8927] shardCollection should warn if numInitialChunks is used with non-hashed sharded key Created: 28/Sep/16 Updated: 30/Oct/23 Resolved: 19/Jul/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Emily Hall | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 30 weeks ago | ||||||||
| Epic Link: | 3.4: Sharding Updates | ||||||||
| Description |
|
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 |
| Comments |
| Comment by Githook User [ 19/Jul/17 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |