hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6061) Add a customized uncaughtexceptionhandler for critical threads
Date Tue, 24 Jan 2017 22:27:26 GMT

    [ https://issues.apache.org/jira/browse/YARN-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836756#comment-15836756

Karthik Kambatla commented on YARN-6061:

Now I know why my perception of reality is different from reality. YARN-2579 has moved transitioning
the RM to standby from RMFatalEventDispatcher to RMStateStore to avoid a deadlock in the RM.

Can we have RMCriticalThreadUncaughtExceptionHandler mimic the same behavior? Maybe, share

> 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message