[SERVER-5277] chunkSize per sharded collection option Created: 09/Mar/12 Updated: 06/Dec/22 Resolved: 21/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.0.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 5 |
| Labels: | balancer, chunks, mongos, splitting | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
Allow having a chunkSize per sharded collection instead of per sharded cluster. If not overridden per collection then inherit from cluster settings. |
| Comments |
| Comment by Matthieu Rigal [ 08/Dec/14 ] |
|
Would be especially useful for collections where we have one document per object making a summary/description of other numerous objects inside another collection, which is small but regularly updated, in order to dispatch the writes. For example, if you have a collection to keep the distinct values of subdocuments of another (big) collection. |