[
https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648488#comment-14648488
]
Arun Suresh commented on YARN-2005:
-----------------------------------
Thanks for the patch [~adhoot],
Couple of comments:
# noBlacklist in DisabledBlacklistManager can be made static final.
# {{getNumClusterHosts()}} in AbstractYarnScheduler : Any reason we are
creating a new set ? think returning this.nodes.size() should suffice right ?
# Instead of removing from the shared blacklist cause problems if the shared
blacklist already contained the blacklisted node ?
> Blacklisting support for scheduling AMs
> ---------------------------------------
>
> Key: YARN-2005
> URL: https://issues.apache.org/jira/browse/YARN-2005
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
> Affects Versions: 0.23.10, 2.4.0
> Reporter: Jason Lowe
> Assignee: Anubhav Dhoot
> Attachments: YARN-2005.001.patch, YARN-2005.002.patch,
> YARN-2005.003.patch, YARN-2005.004.patch
>
>
> It would be nice if the RM supported blacklisting a node for an AM launch
> after the same node fails a configurable number of AM attempts. This would
> be similar to the blacklisting support for scheduling task attempts in the
> MapReduce AM but for scheduling AM attempts on the RM side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
