[SERVER-76618] Robustify shard_split_change_collections_test.js Created: 27/Apr/23 Updated: 29/Oct/23 Resolved: 01/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mickey Winters | Assignee: | Mickey Winters |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | QE 2023-05-15 |
| Participants: |
| Description |
|
this is a problem with a test and not the server itself. https://github.com/10gen/mongo/blob/master/jstests/serverless/shard_split_change_collections_test.js#L103 we do a drop after we forget the split operation with `operation.forget()` but the code doesn't wait for the access blockers to be cleaned up after the forget operation so its possible they could still be in place. this drop failed in a patch build i ran so i noticed it, but I haven't seen it fail in the waterfall. |
| Comments |
| Comment by Githook User [ 29/Apr/23 ] |
|
Author: {'name': 'Mickey. J Winters', 'email': 'mickey.winters@mongodb.com', 'username': 'mjrb'}Message: |