[
https://issues.apache.org/jira/browse/STORM-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376752#comment-15376752
]
Abhishek Agarwal commented on STORM-1600:
-----------------------------------------
Incorporate the check into
https://github.com/apache/storm/pull/1543
> 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)
