[SERVER-74742] collection_uuid.js should not leave open cursors Created: 10/Mar/23 Updated: 27/Oct/23 Resolved: 28/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03 |
| Participants: |
| Description |
|
The crud operations leave cursors open in this test which can block range deletions and therefore migrations. We should modify the operations in this test so that they don't leave cursors open and check collection_uuid_sharded.js to see if it has the same problem. |
| Comments |
| Comment by Allison Easton [ 28/Mar/23 ] |
|
This test is not leaving cursors open that are blocking the range deleter after all. The finds are already using singleBatch to prevent cursors from being left open. |