[SERVER-14723] Crash during query planning for geoNear with multiple 2dsphere indices Created: 29/Jul/14 Updated: 09/Oct/15 Resolved: 03/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo, Querying |
| Affects Version/s: | 2.6.3 |
| Fix Version/s: | 2.6.9, 3.0.1, 3.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mark Percy | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Completed: | |||||||||
| Participants: | |||||||||
| Description |
|
Hi, We installed Mongo Server 2.6.3 in our staging environment as a three member replica set in Amazon AWS. Around a day after the initial install, one of the Mongo members crashed with attached crash log. We then rolled back to 2.4.9 which we've been using in production since March 2014 without issue. Regards, Mark Percy |
| Comments |
| Comment by Githook User [ 05/Mar/15 ] | ||||||||||||||||||||||
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: (cherry picked from commit 965cbef869f8b864caaf3bf7705f8bd82c2b81ba) | ||||||||||||||||||||||
| Comment by Githook User [ 04/Mar/15 ] | ||||||||||||||||||||||
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: (cherry picked from commit 965cbef869f8b864caaf3bf7705f8bd82c2b81ba) | ||||||||||||||||||||||
| Comment by Githook User [ 03/Mar/15 ] | ||||||||||||||||||||||
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: | ||||||||||||||||||||||
| Comment by J Rassi [ 15/Aug/14 ] | ||||||||||||||||||||||
|
Hi Mark, We still need additional information from you to diagnose this problem. Would you be able to provide any of the information requested in my comment above? Thanks. | ||||||||||||||||||||||
| Comment by J Rassi [ 30/Jul/14 ] | ||||||||||||||||||||||
|
Hi Mark, Sorry to hear that you encountered this issue. I can infer from the stack trace that the crash occurred in the query planner, during planning of a query that included a $geoNear predicate (it could also be a $text predicate, but I would guess your application doesn't use $text if you're running the same application code on top of MongoDB 2.4). So, I would guess that there's a bug that generates a crash in the server when a certain kind of $geoNear predicate is run when certain indexes are present. I'd like to ask for some additional information to further diagnose this issue:
Thanks. | ||||||||||||||||||||||
| Comment by David Storch [ 29/Jul/14 ] | ||||||||||||||||||||||
|
Stack trace from the log:
|