[SERVER-63911] Allow balancer to run and re-run defragmentation at the end of collection_defragmentation.js Created: 23/Feb/22 Updated: 29/Oct/23 Resolved: 03/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | 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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-03-07 |
| Participants: |
| Description |
|
In order to test that defragmentation leaves the balancer in a consistent state, we should turn the balancer on for the collection being defragmented at the end of defragmentation and ensure that the balancer reaches a compliant state. We should also check that if defragmentation is then run again without the concurrent operations, the collection runs defragmentation again successfully and reaches a correct defragmented state. |
| Comments |
| Comment by Githook User [ 03/Mar/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |