[SERVER-41212] snapshot_read_kill_operations.js should accept CursorKilled on currentOp Created: 17/May/19  Updated: 29/Oct/23  Resolved: 17/May/19

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

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2019-06-03
Participants:
Linked BF Score: 10

 Description   

Similarly to SERVER-40999, the cursor internally established by currentOp can be killed while being used, leading to a CursorKilled error. The test already handles CursorNotFound and Interrupted, so it should be updated to handle CursorKilled as well.



 Comments   
Comment by Githook User [ 17/May/19 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-41212 snapshot_read_kill_operations.js should accept CursorKilled on currentOp
Branch: master
https://github.com/mongodb/mongo/commit/006c92c7eef1c316b7ebef29d3e03e0ba6897c4a

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