[SERVER-10550] CurOp::_killPending not always cleared between client operations Created: 16/Aug/13  Updated: 12/Jan/16  Resolved: 12/Jan/16

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: 2.5.1
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: J Rassi Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-2212 Server automatically abort queries/co... Closed
Related
is related to SERVER-14758 killOp on foreground index build does... Closed
Operating System: ALL
Participants:

 Description   

CurOp::_reset() is not called before running $cmd.sys operations. This can cause $cmd.sys operations to be erroneously killed if they are run directly following another operation that is killed. The interruption could occur, for example, in an auth-enabled system during the killCurrentOp.checkForInterrupt() call in BtreeCursor::advance(), if the authorization check for the $cmd.sys op has to fetch a privilege document from disk.



 Comments   
Comment by J Rassi [ 12/Jan/16 ]

As of changes made for 3.2 in SERVER-18277, CurOp::_reset() no longer exists, and CurOp is a decoration on an OperationContext. This alleviates the issue describes in this ticket.

Closing as "Gone Away".

Generated at Thu Feb 08 03:23:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.