hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster
Date Fri, 15 Jan 2016 15:10:39 GMT

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

Junping Du commented on YARN-4389:

Hi [~rohithsharma], this is on my mind too when I raise my previous comments. However, in
YARN-4576, we are talking about have a real global blacklist tracking rather than per app
list. May be we can put a note there and track this later?

> "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should
be app specific rather than a setting for whole YARN cluster
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>                 Key: YARN-4389
>                 URL: https://issues.apache.org/jira/browse/YARN-4389
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: applications
>            Reporter: Junping Du
>            Assignee: Sunil G
>            Priority: Critical
>         Attachments: 0001-YARN-4389.patch, 0002-YARN-4389.patch, 0003-YARN-4389.patch,
0004-YARN-4389.patch, 0005-YARN-4389.patch, 0006-YARN-4389.patch, 0007-YARN-4389.patch, 0008-YARN-4389.patch,
> "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should
be application specific rather than a setting in cluster level, or we should't maintain amBlacklistingEnabled
and blacklistDisableThreshold in per rmApp level. We should allow each am to override this
config, i.e. via submissionContext.

This message was sent by Atlassian JIRA

View raw message