Strange Exception since upgrade to 2.6 and Java Driver V2.12.0

[Stephan]

Hi,

I cannot really tell, what triggers that exception as it's a bit empty.

Anybody has a clue, what triggers that?

Thanks...

com.mongodb.MongoException: assertion src/mongo/db/query/planner_analysis.cpp:114

        at com.mongodb.QueryResultIterator.throwOnQueryFailure(QueryResultIterator.java:214)

        at com.mongodb.QueryResultIterator.init(QueryResultIterator.java:198)

        at com.mongodb.QueryResultIterator.initFromQueryResponse(QueryResultIterator.java:176)

        at com.mongodb.QueryResultIterator.<init>(QueryResultIterator.java:64)

        at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:80)

        at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:61)

        at com.mongodb.DBCursor._check(DBCursor.java:458)

        at com.mongodb.DBCursor._hasNext(DBCursor.java:546)

        at com.mongodb.DBCursor.hasNext(DBCursor.java:571)

[Dan Pasette]

what is the query that is triggering the exception?

[Stephan]

hmmm... we don't log every query. But it's actually a quite simple one like: db.vc.find({key:"123454A"}).sort({timestamp:-1}).

there is an index for key:1, timestamp:-1

[Asya Kamsky]

This is likely https://jira.mongodb.org/browse/SERVER-13752

Are you passing any {$in: [ ] } with a sort  where the $in list might be empty?

Asya

--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
 
For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user...@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.

To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/bdde7be0-ded1-4cda-ad10-ff5e175e6f26%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Asya Kamsky]

This assertion would be logged in the mongod log regardless of log level, so you can find exactly what parameters triggered this there.

Asya

On Wed, Apr 23, 2014 at 2:43 AM, Stephan <sboes...@googlemail.com> wrote:

[Stephan]

You're right, there is somehow an empty $in-Query built... I'll have to check that.

Thanks for the help!