[SERVER-63901] Disable collection checks at the end of collection_defragmentation.js Created: 23/Feb/22 Updated: 29/Oct/23 Resolved: 24/Feb/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 |
|
Currently, the collection_defragmentation fsm workload checks that the collection was correctly defragmented at the end of the workload in the teardown. However, if defragmentation finishes before the test is over, other operations (move, merge, and split) can be run on the collection before these checks are run, thus making the final state invalid with respect to defragmentation. This checks should be removed from the end of the FSM workload |
| Comments |
| Comment by Githook User [ 24/Feb/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |