[SERVER-3344] shell query blocked on Mongos and no way to kill it Created: 28/Jun/11  Updated: 29/Feb/12  Resolved: 03/Sep/11

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

Type: Question Priority: Minor - P4
Reporter: Peter Thairu Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Centos 5.4 x86_64
3 shard


Participants:

 Description   

Date range query via mongo shell with a typo (missing "new" in date var declaration) blocked all other queries using mongos. db.currentOp() did not show query but issue resolved by restarting mongos. Attempts to reproduce so far have been unsuccessful ... do you know of any scenario where this occurs and how to avoid/resolve without causing 100% outage?

Query:
var enddate = Date(2011,11,30)
var tempdate = Date(2011,5,26)
db.UserIdentity.find({ "acctMgmt.createTime" : {$gte: tempdate, $lt: enddate}},

{username:1,'acctMgmt.createTime':1}

)

Abreviated doc schema:
> db.UserIdentity.findOne()
{
"_id" : ObjectId("4e09eb8d16887e33bb1be8e4"),
"field" : "yyyy",
"username" : "xxxx",
"acctMgmt" :

{ "createTime" : ISODate("2000-01-01T13:32:00Z"), <other fields ...> }

,

"xxxxx" :

{ "field" : yyy, <other fields ...> }

,
"xxxxx" :

{ "field" : yyy, <other fields ...> }

}



 Comments   
Comment by Eliot Horowitz (Inactive) [ 03/Sep/11 ]

I can't manage to get the system do this at all.
Have you seen it again?

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