[SERVER-71788] Defragmentation should handle ChunkTooBig errors Created: 02/Dec/22 Updated: 29/Oct/23 Resolved: 05/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.1.0, 6.0.3, 6.2.0-rc2 |
| Fix Version/s: | 6.0.4, 6.2.0-rc3, 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | collection-defrag-bugs | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v6.2, v6.1, v6.0
|
||||
| Sprint: | Sharding EMEA 2022-12-12 | ||||
| Participants: | |||||
| Description |
|
Currently, the defragmentation policy is sending moveChunk commands with forceJumbo set to true. This is in the case that our datasize calculation is incorrect and the chunk we decide to move is very large. However, we don't actually want to move huge chunks for defragmentation, as we are trying to move small chunks only. Instead of sending the request with forceJumbo set to true, we should handle the ChunkTooBig and ExceededMemoryLimit errors to not retry these migrations. |
| Comments |
| Comment by Githook User [ 12/Dec/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: (cherry picked from commit 76d4cb7bd5b3654f7e3bba3aaf9fbb5c766476a4) |
| Comment by Githook User [ 05/Dec/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: (cherry picked from commit 76d4cb7bd5b3654f7e3bba3aaf9fbb5c766476a4) |
| Comment by Githook User [ 05/Dec/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |