[SERVER-45630] Allow specifying a chunkSize setting per collection Created: 17/Jan/20 Updated: 06/Dec/22 Resolved: 21/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently, the chunkSize setting is global for all collections, which means that if there is a collection with a relatively small number of documents but heavy load (such as the sessions collection), the shard that owns the chunk(s) for the collection can become hot even though there other shards that could be used to distribute the load. |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 21/Jan/20 ] |
|
Thanks kevin.pulo, closing this one and |