You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Ryan (Jira)" <ji...@apache.org> on 2019/12/30 08:24:00 UTC
[jira] [Updated] (STORM-3560) Worker Process
2d4d998d-4a8c-43ca-aafd-19808c63e4da exited with code: 139
[ https://issues.apache.org/jira/browse/STORM-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan updated STORM-3560:
------------------------
Priority: Blocker (was: Major)
> Worker Process 2d4d998d-4a8c-43ca-aafd-19808c63e4da exited with code: 139
> -------------------------------------------------------------------------
>
> Key: STORM-3560
> URL: https://issues.apache.org/jira/browse/STORM-3560
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core, storm-server
> Affects Versions: 2.1.0
> Environment: online
> Reporter: Ryan
> Priority: Blocker
>
> Our online storm application has the problem of worker exiting abnormally. There is no abnormal information in worker.log. You can see the restart log in worker.log. It is found in supervisor.log:
> Worker Process 2d4d998d-4a8c-43ca-aafd-19808c63e4da exited with code: 139
> 2019-12-30 12: 33: 26.248 o.a.s.d.s. Slot SLOT_1801 [WARN] SLOT 1801: main process has exited
> Then the worker exits and is restarted by the supervisor. Is this a segment fault generated by the jni call to the C code?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)