[SERVER-74405] Set a maximum number of chunks to merge within an auto-merging round Created: 27/Feb/23 Updated: 29/Oct/23 Resolved: 03/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | 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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-03-06 |
| Participants: |
| Description |
|
Currently, there is no limit to the number of chunks that can be squashed together during an auto-merging round. This implies that it is possible to auto merge hundreds of thousand of chunks in one shot causing a relevant stall on the next routing table refresh. Purpose of this ticket is to limit the amount of chunks that can be merged in one shot and to return to the balancer the number of chunks that were merged |
| Comments |
| Comment by Githook User [ 03/Mar/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |