[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 |
||
| 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: ) Abreviated doc schema: , "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. |