Need Fix for SERVER-13714

70 views
Skip to first unread message

confused

unread,
Jun 13, 2014, 2:36:13 PM6/13/14
to mongod...@googlegroups.com
Our product is about to release, but we have hit a block bug similar to SERVER-13714.  Is it possible for us to obtain a fix to this problem?  I understand mongodb 2.6.1-rc1 does not have this fix.  If not, we may need to roll back to 2.4, which would caused another bug.

confused

unread,
Jun 13, 2014, 2:39:23 PM6/13/14
to mongod...@googlegroups.com
I am sorry, 2.6.2-rc1 does have SERVER-13714 fix.  Can someone tell me if it is stable to be used for production?  Thanks!

confused

unread,
Jun 13, 2014, 3:00:03 PM6/13/14
to mongod...@googlegroups.com
I have tested on mongodb 2.6.2-rc1, the problem still exists.  Here is the stack trace:

com.mongodb.CommandResult$CommandFailure: command failed [count]: { "serverUsed" : "localhost/127.0.0.1:27017" , "errmsg" : "exception: assertion src/mongo/db/query/plan_enumerator.cpp:1011" , "code" : 0 , "ok" : 0.0}
        at com.mongodb.CommandResult.getException(CommandResult.java:88)
        at com.mongodb.CommandResult.throwOnError(CommandResult.java:134)
        at com.mongodb.DBCollection.getCount(DBCollection.java:977)
        at com.mongodb.DBCollection.getCount(DBCollection.java:938)
        at com.mongodb.DBCollection.getCount(DBCollection.java:913)
        at com.mongodb.DBCollection.count(DBCollection.java:860)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

confused

unread,
Jun 13, 2014, 3:19:13 PM6/13/14
to mongod...@googlegroups.com
I installed mongodb 2.6.2-rc1, the problem still exists. 

I then installed mongodb 2.7.1, mongodb would not even come up.

Then I installed mongodb 2.6.2-rc1 again, this time the problem disappeared.

Thanks!

confused

unread,
Jun 13, 2014, 3:33:59 PM6/13/14
to mongod...@googlegroups.com
Is there a final release date for mongodb 2.6.2, please?

Asya Kamsky

unread,
Jun 13, 2014, 4:58:08 PM6/13/14
to mongod...@googlegroups.com
Are you sure you've diagnosed your actual problem correctly?
If it happened when you tried 2.6.2-rc1 then it probably hasn't been fixed...

Can you provide exactly what query triggers this for you?
--
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/5e557bac-cf2f-433e-a2bb-7e98b741f6cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Tiffany

unread,
Jun 13, 2014, 6:57:33 PM6/13/14
to mongod...@googlegroups.com
Hello Asya:

I have installed 2.6.2-rc1 again, and this time it worked.  So the problem has been fixed.  Thanks!

My supervisor wants to know when would you release 2.6.2, we'd like to ship our product with official release of mongodb 2.6.2, not 2.6.2-rc1.

Thanks!


Asya Kamsky

unread,
Jun 14, 2014, 10:06:41 PM6/14/14
to mongodb-user
I have no crystal ball, but according to Jira it will be released tomorrow.

If I were a betting person though, I would bet on Monday, rather than Sunday.

Asya



Reply all
Reply to author
Forward
0 new messages