[
https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646612#comment-14646612
]
Anubhav Dhoot commented on YARN-2005:
-------------------------------------
I think blacklisting can have lots of policies and constraints and will
probably change over time. Since RMAppAttemptImpl#ScheduleTransition drops the
locality constraint it seems ok for the current blacklisting to also be
locality constraint unaware. Should we start simple and keep a separate jira
for honoring am locality in scheduling and blacklisting at the same time?
[~jianhe],[~bikassaha] let me know if you agree and I can file that jira.
> 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)
