[SERVER-73586] Harmonize `ChunkTooBig` handling for automatic and manual migrations Created: 03/Feb/23 Updated: 27/Oct/23 Resolved: 20/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Pierlauro Sciarelli | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Operating System: | ALL |
| Participants: |
| Description |
|
When a migration issued by the balancer fails because of an unsplittable chunk, the chunk is marked as jumbo. However, when a manual migration fails because of the same reason, the chunk does not get marked as jumbo. Purpose of this ticket is to harmonize the handling of ChunkTooBig so that also manual migrations call into splitOrMarkJumbo. |
| Comments |
| Comment by Garaudy Etienne [ 09/Feb/23 ] |
|
It's technically an improvement. But it's doing something dumb so I'm calling it a bug. |