Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue seeing long running queries run from robomong 0.9.0 in Mongo 2.6.3 #1259

Open
jeremycooper1 opened this issue Dec 12, 2016 · 4 comments
Open

Comments

@jeremycooper1
Copy link

@jeremycooper1 jeremycooper1 commented Dec 12, 2016

No description provided.

@jeremycooper1
Copy link
Author

@jeremycooper1 jeremycooper1 commented Dec 12, 2016

We are testing a means of identifying and killing long running queries in MongoDB 2.6.3.

We are running a query without an index , and then running our query to identify it.
If we run the query without an index in RoboMongo 0.8.4 we see it using our code, If we run it 0.9.0 we don't - Are you able to explain this ? Is it something to do with the mongo shell used in 0.9.0 ?

function used to identify long running queries:
db.currentOp().inprog.forEach( function(op) { if(op.secs_running > 5) printjson(op); } )

code run in RoboMongo 0.8.4 and 0.9.0
db.getCollection('company_profile').find({"data.company_number":"NI008994"}).explain()

Thanks.

@juliashibalko
Copy link
Collaborator

@juliashibalko juliashibalko commented Dec 13, 2016

Hi @jeremycooper1! Thanks a lot for reporting. It's one of the known issue and we are sorry for that.
Let me suggest you to check workaround described in the ticket #1106 (comment) (increase shellTimeoutSec value). I believe this should solve the problem so I'm closing ticket as duplicate.

Please let us know if it works for you and feel free to reopen in any case.

@jeremycooper1
Copy link
Author

@jeremycooper1 jeremycooper1 commented Dec 13, 2016

Thanks for the info.

@juliashibalko
Copy link
Collaborator

@juliashibalko juliashibalko commented Jan 4, 2017

Hi @jeremycooper1, sorry for long wait!
As far as I understand, the problem is next: Robomongo 0.9.0 embeds mongo shell version 3.2, and your operation requests mongo shell version 2.6 (as Robomongo 0.8.5 has) . You can read about it here http://blog.robomongo.org/robomongo-future/.
We are planning to implement such support, but now our main goal is Replica Set. Anyway we will get back to you with any updates.

Please let me know in case of any questions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants