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

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

One more doubt here, I do not feel we need to deprecate or remove 
"yarn.am.blacklisting.enabled" and 
"yarn.am.blacklisting.disable-failure-threshold". It can be kept, and we can 
also override if we specify via submission context. This will satisfy both 
cases, will this approach be fine [~djp]

> "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)

Reply via email to