[
https://issues.apache.org/jira/browse/YARN-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101901#comment-15101901
]
Sunil G commented on YARN-4389:
-------------------------------
bq.May be we can put a note there and track this later?
I think YARN-4576 is full solution for this. After thinking abt this, I feel a
note there is fine.
+1 for current patch here 0009.
> "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,
> 0009-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
(v6.3.4#6332)
