hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (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 Tue, 24 Nov 2015 17:55:11 GMT

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

Sunil G commented on YARN-4389:
-------------------------------

I could give a hand here if you haven't started. 

> "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
>            Priority: Critical
>
> "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
(v6.3.4#6332)

Mime
View raw message