[SERVER-66859] Disable balancing during second run of defragmentation in collection_defragmentation.js Created: 30/May/22 Updated: 06/Dec/22 Resolved: 02/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Operating System: | ALL |
| Participants: |
| Description |
|
In the teardown of collection_defragmentation.js, we wait for ongoing defragmentation to end, then we turn on the balancer and wait for balanced, and then run defragmentation again and check the status. We need to re-disable the balancer after waiting for balanced, otherwise a migration could happen after defragmentation ends and before the checks run, causing a test failure. |