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

No results returned, when it should #1201

Closed
hrgerber opened this Issue Sep 29, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@hrgerber

hrgerber commented Sep 29, 2016

Slightly longer running queries (many inserts, distinct, aggregate, and count) over a few million records regularly "fail" by returning no results "Script executed successfully, but there are no results to show". Rerunning these queries multiple times will eventually return a result.

Mongo 3.2, Mac OS X 10.10, Robomongo 0.9 R10

Don't believe I experience this issue with 0.8.x versions.

Example query that return no result:
db.getCollection('deed').distinct('PropertyType')

while mongo log shows:
2016-09-29T10:34:09.412+0200 I COMMAND [conn4108] command consumer.deed command: distinct { distinct: "deed", key: "PropertyType", query: {} } keyUpdates:0 writeConflicts:0 numYields:79619 reslen:234 locks:{ Global: { acquireCount: { r: 159240 } }, Database: { acquireCount: { r: 79620 } }, Collection: { acquireCount: { r: 79620 } } } protocol:op_command 26877ms

same command from mongo client have logs show:
2016-09-29T10:38:56.878+0200 I COMMAND [conn4096] command consumer.deed command: distinct { distinct: "deed", key: "PropertyType", query: {} } keyUpdates:0 writeConflicts:0 numYields:79600 reslen:234 locks:{ Global: { acquireCount: { r: 159202 } }, Database: { acquireCount: { r: 79601 } }, Collection: { acquireCount: { r: 79601 } } } protocol:op_command 19155ms

and results
[ "E", "U", "F", "H", "C", "S", "A", "R", "T", "" ]
This is correct.

@juliashibalko

This comment has been minimized.

Show comment
Hide comment
@juliashibalko

juliashibalko Sep 29, 2016

Collaborator

Hi @hrgerber! It's known issue, so let me suggest you to check workaround described in the ticket #1106 (comment) (increase shellTimeoutSec value) . I believe this should solve the problem. Please let us know if it works for you.

Collaborator

juliashibalko commented Sep 29, 2016

Hi @hrgerber! It's known issue, so let me suggest you to check workaround described in the ticket #1106 (comment) (increase shellTimeoutSec value) . I believe this should solve the problem. Please let us know if it works for you.

@yarrr-ru

This comment has been minimized.

Show comment
Hide comment
@yarrr-ru

yarrr-ru Oct 26, 2016

@juliashibalko faced same problem with no results for "count".
Increasing shellTimeoutSec helped me.

yarrr-ru commented Oct 26, 2016

@juliashibalko faced same problem with no results for "count".
Increasing shellTimeoutSec helped me.

@juliashibalko

This comment has been minimized.

Show comment
Hide comment
@juliashibalko

juliashibalko Oct 26, 2016

Collaborator

@yarrr-ru thanks a lot for sharing! Glad to hear workaround helped :)

Collaborator

juliashibalko commented Oct 26, 2016

@yarrr-ru thanks a lot for sharing! Glad to hear workaround helped :)

@juliashibalko

This comment has been minimized.

Show comment
Hide comment
@juliashibalko

juliashibalko Jan 4, 2017

Collaborator

I'm closing this ticket as fixed. Please don't hesitate to re-open it in any case!

Collaborator

juliashibalko commented Jan 4, 2017

I'm closing this ticket as fixed. Please don't hesitate to re-open it in any case!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment