[SERVER-71756] Defragmentation policy should issue dataSize commands with estimate true Created: 01/Dec/22 Updated: 29/Oct/23 Resolved: 07/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.1.0, 6.0.3, 6.2.0-rc1 |
| 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 issuing datasize commands with estimate set to false. This can make the operation very slow for large chunks. We should change this field to true. We also need to ensure that potential errors caused by incorrect datasize after this change are handled - for example, if the defragmentation tries to issue a move for a chunk that is too large, we should ensure the defragmenter is not continuously retrying this operation. |
| Comments |
| Comment by Githook User [ 12/Dec/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: (cherry picked from commit 49c71b36991b5eb765f66e03d09af6673c9aead7) |
| Comment by Githook User [ 07/Dec/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: (cherry picked from commit 49c71b36991b5eb765f66e03d09af6673c9aead7) |
| Comment by Githook User [ 07/Dec/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |