[SERVER-33283] Add test coverage for case where pinned cursor is killed after all calls to checkForInterrupt on mongos Created: 12/Feb/18  Updated: 29/Oct/23  Resolved: 30/Mar/18

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Improvement Priority: Major - P3
Reporter: Ian Boros Assignee: Ian Boros
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-18094 currentOp on a mongoS should also sho... Closed
Related
related to SERVER-38418 Add waitWithPinnedCursorDuringGetMore... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: Query 2018-03-26, Query 2018-04-09
Participants:

 Description   

Without some kind of "local" curOp on mongos, it's impossible to tell whether a failpoint has been hit. Because of this, we cannot have (non-flaky) test coverage for the case where a pinned cursor is killed at a point where the operation using the cursor won't call checkForInterrupt again.

Once we have a "local" curOp, it will be easy to modify jstests/sharding/kill_pinned_cursor.js to check this case.



 Comments   
Comment by Githook User [ 30/Mar/18 ]

Author:

{'email': 'ian.boros@10gen.com', 'name': 'Ian Boros'}

Message: SERVER-33283 Add test coverage for case where pinned cursor is killed after interrupt checks
Branch: master
https://github.com/mongodb/mongo/commit/431ef23420797fb0956fae4e3d5149e2224bbaee

Generated at Thu Feb 08 04:32:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.