[SERVER-68464] Jumbo chunk flag doesn't automatically clear if a chunk size is now below the cluster chunk size Created: 01/Aug/22 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Garaudy Etienne | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea, shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding EMEA 2022-08-22, Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12 | ||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
If I have a 200MB chunk that the balancer tried to move and marked as jumbo and I change the cluster chunk size to 256MB, that chunk will still not be migrated by the balancer. |
| Comments |
| Comment by Kaloian Manassiev [ 02/Aug/22 ] |
|
Just for completeness, the workaround for such situation currently would be to run the clearJumboFlag command on the chunk. |