[SERVER-1816] killop not robust Created: 20/Sep/10  Updated: 12/Jul/16  Resolved: 05/Oct/10

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

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Eliot Horowitz (Inactive)
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-387 currentOp() and killOp() don't work r... Closed
Operating System: ALL
Participants:

 Description   

The current killop implementation only tracks the op num of the most recently requested op to kill. This means that if I kill op 5 and then kill op 6 immediately afterward, and the execution of op 5 happens not to call checkForInterrupt() between the two killop requests, op 5 will not be killed.

It also appears there may be an issue if the op num of the last killed op is reused. It's possible that the op with the reused num will be killed immediately upon starting, though I haven't confirmed this with a test.



 Comments   
Comment by auto [ 05/Oct/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-1816 make sure it's possible to kill parent ops while child op is running
http://github.com/mongodb/mongo/commit/acee25a02a3ddfbf71fc3c230f2b671e290494b0

Comment by auto [ 05/Oct/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-1816 make killop robust by storing kill request in curop
http://github.com/mongodb/mongo/commit/4a7a23a29c2daca9eff29d252b3a4fa35b2b05e8

Generated at Thu Feb 08 02:58:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.