[SERVER-69494] Fix chunk resizing semantics upon downgrade between 6.x versions Created: 07/Sep/22 Updated: 29/Oct/23 Resolved: 07/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding EMEA 2022-09-19 | ||||
| Participants: | |||||
| Linked BF Score: | 170 | ||||
| Description |
|
Since it was initially assumed that data size aware balancing would land in v6.0, the chunk resize policy was structured to unconditionally happen on downgrade (from v6.0 to v5.x). As data size aware balancing landed in v6.1, it is needed to adapt that part of the code to only resize chunks in case the downgrade is happening from v6.x (x>0) to v6.0. |
| Comments |
| Comment by Githook User [ 07/Sep/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |