[SERVER-75578] collection_defragmentation.js should disallow balancing before running defragmentation a second time Created: 03/Apr/23 Updated: 29/Oct/23 Resolved: 03/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding EMEA 2023-04-03 | ||||||||
| Participants: | |||||||||
| Description |
|
In collection_defragmentation.js, we wait for defragmentation to finish, enable balancing, wait for balanced, and then reenable defragmentation. After reenabling defragmentation, we wait for it to complete and then check the defragmentation state. However, since balancing is still enabled, migrations can happen between defragmentation finishing and the final state checks happening. We should re-disable balancing after waiting for the collection to be balanced. |
| Comments |
| Comment by Githook User [ 03/Apr/23 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |