[
https://issues.apache.org/jira/browse/YARN-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130324#comment-15130324
]
Sunil G commented on YARN-4635:
-------------------------------
Thanks [~jianhe] for the comments and thanks [~djp] for the clarifications.
bq.Do you think it’s ok to just use the threshold number only ? 0 means
disabled, and numbers larger than 0 means enabled
Adding one more minor advantage using a threshold. If app specifies
{{AMBlackListingRequest}} flag as false, then global blacklisting will not be
applicable for this app. Such control is easier with a flag i think, how do you
feel.
> Add global blacklist tracking for AM container failure.
> -------------------------------------------------------
>
> Key: YARN-4635
> URL: https://issues.apache.org/jira/browse/YARN-4635
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Junping Du
> Assignee: Junping Du
> Priority: Critical
> Attachments: YARN-4635-v2.patch, YARN-4635.patch
>
>
> We need a global blacklist in addition to each app’s blacklist to track AM
> container failures in global
> affection. That means we need to differentiate the non-succeed
> ContainerExitStatus reasoning from
> NM or more related to App.
> For more details, please refer the document in YARN-4576.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
