[
https://issues.apache.org/jira/browse/STORM-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383861#comment-15383861
]
ASF GitHub Bot commented on STORM-1600:
---------------------------------------
GitHub user abhishekagarwal87 opened a pull request:
https://github.com/apache/storm/pull/1575
STORM-1600: Do not report exceptions after jvm shutdown
@HeartSaVioR - Here is the proposed change. Can you suggest some way to
reproduce a scenario which I could also add as a test case?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/abhishekagarwal87/storm STORM-1600
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1575.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1575
----
commit 04ea50f676855b47e86f00ba0d320fabc51dbdf1
Author: Abhishek Agarwal <[email protected]>
Date: 2016-07-19T09:35:38Z
STORM-1600: Do not report exceptions after jvm shutdown
----
> Do not report errors when the worker shutdown is in progress
> ------------------------------------------------------------
>
> Key: STORM-1600
> URL: https://issues.apache.org/jira/browse/STORM-1600
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Abhishek Agarwal
> Assignee: Abhishek Agarwal
>
> Usually in a worker, some uncaught exception in an executor threads leads to
> process exit. Process exit is not instantaneous and it first triggers the
> shutdown. The shutdown initiation usually results in network connections
> closing e.g. zookeeper, hdfs in other threads causing other exceptions. These
> threads end up reporting their exceptions as well. It confuses the user who
> can these errors on UI but not the actual root cause of shutdown hidden
> beneath new errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
