[
https://issues.apache.org/jira/browse/YARN-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830858#comment-15830858
]
ASF GitHub Bot commented on YARN-6061:
--------------------------------------
GitHub user flyrain opened a pull request:
https://github.com/apache/hadoop/pull/182
YARN-6061. Add a customized uncaughtexceptionhandler for critical threads
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/flyrain/hadoop yarn-6061
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hadoop/pull/182.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 #182
----
commit fbbc209b1450c7c22b04568f53b716e727df750a
Author: Yufei Gu <[email protected]>
Date: 2017-01-19T23:50:55Z
YARN-6061. Add a customized uncaughtexceptionhandler for critical threads.
----
> Add a customized uncaughtexceptionhandler for critical threads
> --------------------------------------------------------------
>
> Key: YARN-6061
> URL: https://issues.apache.org/jira/browse/YARN-6061
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
> Reporter: Yufei Gu
> Assignee: Yufei Gu
> Attachments: YARN-6061.001.patch, YARN-6061.002.patch
>
>
> There are several threads in fair scheduler. The thread will quit when there
> is a runtime exception inside it. We should bring down the RM when that
> happens. Otherwise, there may be some weird behavior in RM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
