[SERVER-69274] .maxTimeMs leaks shard cursor Created: 31/Aug/22 Updated: 14/Jan/23 Resolved: 05/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Romans Kasperovics | Assignee: | Romans Kasperovics |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
max_time_ms_does_not_leak_shard_cursor.js fails periodically (3% of evergreen runs), because there is an open cursor on shards after the mongoS query (correctly) failed with MaxTimeMSExpired. The test was added in 6.0 in response to Possible solution idea: the remaining time is transferred from the cursor to the opCtx. Perhaps, the timeout should be removed from opCtx at the end of getMore. |