[SERVER-25465] Mongos crashing due to segmentation error. Created: 05/Aug/16 Updated: 08/Jan/24 Resolved: 22/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | 3.2.7 |
| Fix Version/s: | 3.2.10, 3.3.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Davenson Lombard | Assignee: | Mira Carey |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-and-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Completed: | |||||||||||||||||
| Sprint: | Platforms 2016-08-26 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
The following Segmentation Fault occured on a mongos 3.2.8
Thanks |
| Comments |
| Comment by Ramon Fernandez Marina [ 30/Sep/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Unfortunately we found additional issues in the 3.2.10-rc release candidates. The good news is that we're in the process of releasing 3.2.10, which is currently scheduled for Monday, October 1st. Thanks everyone for their patience, | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 23/Sep/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
A quick note to watchers of this ticket: The issue that wxiaoguang@gmail.com encountered had a different cause and was addressed in | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Xiaoguang Wang [ 19/Sep/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Still crashes with 3.2.10-rc0
| ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Daniel Pasette (Inactive) [ 14/Sep/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
3.2.10-rc0 was released yesterday. It would be great if you are in a position to test this version in a non-production environment. The production release of 3.2.10 should be out within a week. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Jeff Poole [ 14/Sep/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
We've been getting bitten by this quite a bit ourselves. Since "two weeks" is tomorrow, is there an updated expectation of when 3.2.10 will be released? | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Daniel Pasette (Inactive) [ 01/Sep/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Jon, we're preparing a release candidate for 3.2.10, which includes this patch, within the next two weeks. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Jon Hyman [ 01/Sep/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
We are experiencing this under heavy load. Is there a timeline for 3.2.10 or can a hotfix version be released? | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Githook User [ 23/Aug/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}Message: Under enough load, asio can get behind in timeout management. Make sure to bump timer generation to (cherry picked from commit 226a65c73b821760053c58a174e06aa769c59a2d) | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Githook User [ 22/Aug/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}Message: Under enough load, asio can get behind in timeout management. Make sure to bump timer generation to | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Andrew Morrow (Inactive) [ 18/Aug/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
davenson.lombard - Yes, as this appears to be a regression, a backport to 3.2 is almost certain - once we have identified, resolved, and written regression tests for the issue on the master branch. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Andrew Morrow (Inactive) [ 18/Aug/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
mira.carey@mongodb.com - A report of a very similar crash has been posted to mongodb-user, and it includes some very useful details. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Davenson Lombard [ 12/Aug/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Jason, Thanks for the update! | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Mira Carey [ 11/Aug/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Still investigating at the moment, unfortunately. Based on the callstack, we're attempting to cancel an attempt to connect a socket for an operation that's been cancelled in the meantime. It's a fairly narrow race that I thought we'd covered in |