[SERVER-28316] Related to SERVER-27753 - Custom build crashes. Created: 15/Mar/17 Updated: 31/May/17 Resolved: 27/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.11 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Luke Morfitt | Assignee: | Kelsey Schubert |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | crash, custom, mongodb | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Hello, We have seen two crash's of the custom build provided on
|
| Comments |
| Comment by Luke Morfitt [ 16/Mar/17 ] | ||||||||||||||||||||||||||||||||||||||||
|
Thank you for the update. On a side node the custom build took around 3 hours to start on one of the clusters(has 18,000 databases) vs 3.2.11 which usually starts in 45-60 mins. Will test out 3.4rc when it is available and provide feedback. Thank you for your help, | ||||||||||||||||||||||||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 16/Mar/17 ] | ||||||||||||||||||||||||||||||||||||||||
|
lukemorfitt, the current plan is to roll these changes in a 3.4.3-rc2 release candidate that you'll be able to download and test soon. This will provide you with the best path to transition to using a stable release (3.4.3). | ||||||||||||||||||||||||||||||||||||||||
| Comment by Luke Morfitt [ 16/Mar/17 ] | ||||||||||||||||||||||||||||||||||||||||
|
Hello Michael Cahill, Please can you provide a new build for ubuntu 14.04. The change in cache performance has significant benefits for us and we would like to try out a new custom build. Kind regards, | ||||||||||||||||||||||||||||||||||||||||
| Comment by Michael Cahill (Inactive) [ 16/Mar/17 ] | ||||||||||||||||||||||||||||||||||||||||
|
lukemorfitt, thank you for this bug report. We had seen this issue in There is no need to upload further information. We fixed | ||||||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 15/Mar/17 ] | ||||||||||||||||||||||||||||||||||||||||
|
Hi lukemorfitt, Thanks for uploading the diagnostic.data and log files. So we can continue to investigate, would you please upload the following files from gsp-mew?
This will enable us to examine what checkpoints are in the file and the meta-data files will let us know what WiredTiger expects to be in the file. Thank you, | ||||||||||||||||||||||||||||||||||||||||
| Comment by Luke Morfitt [ 15/Mar/17 ] | ||||||||||||||||||||||||||||||||||||||||
|
Hello. I've uploaded two tar balls from different clusters which have experienced these issues. gsp-aeu001 has a small number of databases (relative to the other) and was accidently promoted to master. We was using it as a backup node with mongo dump. gsp-mew is our analytics cluster so has a very large number of databases and collections. We added the custom build to try and perform a large export of data, which (on 3.2.11) will grind to a halt when the cache becomes full. Kind regards, | ||||||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 15/Mar/17 ] | ||||||||||||||||||||||||||||||||||||||||
|
Hi lukemorfitt, Thank you for reporting this behavior. I've created a secure upload portal for the complete log files and diagnostic.data. Thanks again, | ||||||||||||||||||||||||||||||||||||||||
| Comment by Luke Morfitt [ 15/Mar/17 ] | ||||||||||||||||||||||||||||||||||||||||
|
These are the logs from the other failed server.
| ||||||||||||||||||||||||||||||||||||||||
| Comment by Luke Morfitt [ 15/Mar/17 ] | ||||||||||||||||||||||||||||||||||||||||
|
The issue is for the custom build version " mongo-mongodb_mongo_v3.2_ubuntu1404_95d4a0a472e436dad9380db917145f121d8c3720_17_02_20_04_43_56"
Please provide a secure upload location and I will send full log files and diagnostic data for the servers. Thanks, |