[SERVER-38786] Invariant failure Hit a MONGO_UNREACHABLE! src/mongo/db/query/collation/collation_spec.cpp 75 Created: 27/Dec/18  Updated: 28/Feb/19  Resolved: 28/Feb/19

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

Type: Bug Priority: Major - P3
Reporter: ravi pithadiya Assignee: Danny Hatcher (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 16.04, PyMongo3.5


Attachments: Text File amzissue.txt    
Participants:

 Description   

Hi, 

mongodb suddenly stopped with the following error logs.

2018-12-27T07:26:33.336+0000 F -        [conn443555] Invariant failure Hit a MONGO_UNREACHABLE! src/mongo/db/query/collation/collation_spec.cpp 75

2018-12-27T07:26:33.336+0000 F -        [conn443555]

2018-12-27T07:26:33.419+0000 F -        [conn443555] Got signal: 6 (Aborted).

 



 Comments   
Comment by Danny Hatcher (Inactive) [ 28/Feb/19 ]

Hello,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Thanks,

Danny

Comment by Danny Hatcher (Inactive) [ 01/Feb/19 ]

Hi Ravi,

We still need additional information to diagnose the problem. If this is still an issue for you, would you please check the Collation documents for the caseFirst field?

Thanks,

Danny

Comment by Danny Hatcher (Inactive) [ 02/Jan/19 ]

Hello Ravi,

Thank you for the extended logs. This invariant occurs when the caseFirst field in a Collation document is not set to one of the three values of "upper", "lower", or "off". Unfortunately I cannot tell against which namespace the query that triggered the problem was run.

For any operations, indexes, or collections that have collations, can you please check the Collation documents for the caseFirst field to see if there are any discrepancies?

Thank you,

Danny

Comment by ravi pithadiya [ 29/Dec/18 ]

Hi Daniel,

here is the link to the requested logs file. https://drive.google.com/open?id=1f5DEMR6gTSlljO_J_yW3-x6aifyx0az_

Thanks & Regards,

{ name : ravi pithadiya | principal engineer, phone : 8401253847, linkedin : ravi pithadiya <https://www.linkedin.com/in/ravi-pithadiya-0199b120/>, skype : ravi.pithadiya }

On Fri, Dec 28, 2018 at 8:35 PM Daniel Hatcher (Jira) <jira@mongodb.org>

Comment by Danny Hatcher (Inactive) [ 28/Dec/18 ]

Hello Ravi,

Can you please attach the mongod log covering the timeframe right before the query run through the crash?

Thank you,

Danny

Comment by ravi pithadiya [ 28/Dec/18 ]

Hi Kevin,

It is just a simple aggregate project query.

I have attached the query in txt file.amzissue.txt

mongodb service stops as soon as we execute the query.

 

Comment by Kevin Albertson [ 27/Dec/18 ]

Hi Ravi,

Thank you for the bug report, but the CXX project is for the MongoDB C++ driver. I'm moving this ticket to the SERVER project.

Can you provide steps to reproduce this? What operations led to this invariant failure?

Best,
Kevin

Generated at Thu Feb 08 04:50:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.