[SERVER-18855] Mongo fails to respond after upgrade to 2.6.10 Created: 06/Jun/15  Updated: 07/Jun/15  Resolved: 07/Jun/15

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

Type: Bug Priority: Major - P3
Reporter: Volodymyr Gren Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

we recently upgraded to mongo 2.6.10 one of our replica set, after some time the master became unresponsive - it means that all queries were gathering into queue and mongo was not doing anything with queries, and replica set became in fact broken, so we rolled back to 2.4.10

https://mms.mongodb.com/host/detail/4e44f4be14587819403c9268/8980bca521bb5812857cbdc30eb06774

there you can see the queue size of 20k +

please fix asap - it's very critical



 Comments   
Comment by Ramon Fernandez Marina [ 07/Jun/15 ]

Thanks for your report abramovich@nimble.com. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

Comment by Volodymyr Gren [ 06/Jun/15 ]

P.S

nothing in logs while it's happening - in systems logs or mongo logs, also it's not possible even to shutdown normally mongo, just kill -9 works

while on 2.4.10 all is ok

we're on 3.14.27-25.47.amzn1.x86_64, the OS is Amazon Linux AMI release 2014.09

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