[SERVER-67007] shard_split_rejects_multiple_ops test is failing due to a race condition with unexpected garbage collection Created: 03/Jun/22 Updated: 29/Oct/23 Resolved: 06/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathis Bessa | Assignee: | Mathis Bessa |
| 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: | Server Serverless 2022-06-13 | ||||
| Participants: | |||||
| Linked BF Score: | 48 | ||||
| Description |
|
The test wrongfully tests that the split hasn’t been garbage collected even though we do a join of the split thread way before and we also test at that point that there is a ConflictingOperationInProgress
The test complains that it did not fail to run the commitShardSplit and that is because the garbage collection already happened and we fail to reject with `ConflictingOperationInProgress` |
| Comments |
| Comment by Githook User [ 06/Jun/22 ] |
|
Author: {'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |