[SERVER-13733] Mongo 2.6.0 crashing during Geo searches Created: 25/Apr/14  Updated: 10/Dec/14  Resolved: 27/Apr/14

Status: Closed
Project: Core Server
Component/s: Geo
Affects Version/s: 2.6.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Nick Jennings Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

Not sure how to reliably recreate the issue, but if I run a series of geo searches it's bound to happen at some point.

Participants:

 Description   

I just upgraded to Mongo 2.6.0 and suddenly started getting intermittent crashes during geo searches. This does not happen all the time, but does happen quite consistently - just a matter of time when under moderate load.

This never happened on the 2.4.x branch, and I'm just wondering if anyone else has run into this problem or it's a known issue that will be fixed in the next patch release?

Here's an example of a search then crash (Mongoose debugging on):

    Mongoose: records.find({ 'locations.geo': { '$nearSphere': [ 82.2, 122.21 ], '$maxDistance': 0.02 } }) { fields: undefined }  
    connection error: [Error: failed to connect to [localhost:27017]]
    #

Let me know if I can provide any more details and how to do so. This is happening both on my Linux dev machine (Arch x86_64) and a colleagues Macbook Pro.



 Comments   
Comment by Nick Jennings [ 26/Apr/14 ]

Problem seems to be fixed in the 2.6.1 rc0 build! Thanks!

Comment by Nick Jennings [ 25/Apr/14 ]

Thanks for the quick response, downloading 2.6.1-rc1 now, will report back.

Comment by hari.khalsa@10gen.com [ 25/Apr/14 ]

Hi, silverbucket. I wonder if this is really the problem in SERVER-13666? We removed an in-bounds check in 2.6 by mistake. Can you try using the release candidate of 2.6.1 and see if you have the same problem?

Comment by Scott Hernandez (Inactive) [ 25/Apr/14 ]

Please provide the server logs, with verbose logging.

Comment by Nick Jennings [ 25/Apr/14 ]

After running my tests again, it crashed on the exact same query, even though there were Geo searches before that as well. Could it have something to do with invalid coordinates causing the crash? We purposefully do some invalid coordinate searches in our integration tests.

Generated at Thu Feb 08 03:32:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.