[SERVER-23781] Segmentation fault Created: 18/Apr/16 Updated: 28/Sep/20 Resolved: 17/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, WiredTiger |
| Affects Version/s: | 3.0.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Burczyk | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
In a 3 node replica set, on of the secondary members just crashed after months of working correctly with the following stack trace:
Running mongo 3.0.8 with wiredTiger on all 3 nodes. I've seen similar issues a few times on your forum, but they were all closed in version 3.0.8. Any idea what might have caused this? |
| Comments |
| Comment by Kelsey Schubert [ 17/May/16 ] |
|
Thank you for the additional information. Unfortunately, at this time we are unable to determine to the root cause of this behavior. Please let us know if you encounter this seg fault again, so we can work together to construct a reproduction that would enable us to diagnose this issue. Thanks again for your help, |
| Comment by Robert Burczyk [ 05/May/16 ] |
|
Hi Thomas, No, we have not observed this issue ever before or since this incident. Also, we have deleted all the data from this secondary and restarted the node for resync, so we can't reproduce it anymore. Thanks, Robert |
| Comment by Kelsey Schubert [ 05/May/16 ] |
|
Thank you for reporting this issue. We have been discussing this segmentation fault internally, and are still investigating. However, without a reproduction the root cause will be difficult to determine. Have you observed this issue again since reporting it? Kind regards, |