[SERVER-62853] Report configured chunk size in collectionBalancerStatus Created: 21/Jan/22 Updated: 29/Oct/23 Resolved: 17/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Paolo Polato |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v5.3
|
||||
| Sprint: | Sharding EMEA 2022-02-21 | ||||
| Participants: | |||||
| Story Points: | 9 | ||||
| Description |
|
The chunk size for a specific collection is calculated according to the following rules in order of precedence:
So currently it is not straightforward for a user checking which is the currently configured chunk size setting for a specific collection. |
| Comments |
| Comment by Githook User [ 18/Feb/22 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: (cherry picked from commit eee82fa3dc2b0e370a21f9855b74b30937dd859c) |
| Comment by Githook User [ 16/Feb/22 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |