[SERVER-4251] db.killOp doesn't work right on mongos with authentication Created: 10/Nov/11  Updated: 11/Jul/16  Resolved: 11/Nov/11

Status: Closed
Project: Core Server
Component/s: Security, Sharding
Affects Version/s: None
Fix Version/s: 2.1.0

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Kristina Chodorow (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-4237 Enable the full js test suite to run ... Closed
Operating System: ALL
Participants:

 Description   

Run features3.js.

That test spawns a separate shell process that runs a long-running query in an infinite loop that only breaks when the query throws an exception.

The main test program then goes and kills that query with db.killOp(), which should cause an interrupted exception in the other shell process, causing it to terminate, but it doesn't. Because of this, when the main test program tries to join() with the child shell process, it waits forever and the test never terminates. Without authentication this works fine.



 Comments   
Comment by auto [ 24/Jan/12 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: fix killOp in mongos with or without auth SERVER-4251
Branch: master
https://github.com/mongodb/mongo/commit/7fc7559750e36985407b5471de2d7136ded81354

Comment by auto [ 11/Nov/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: Fix killOp to actually work with sharding SERVER-4251
Branch: master
https://github.com/mongodb/mongo/commit/58dcee3a0000a3bafc49afb074bba4fd20f6bbde

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