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

Anubhav Dhoot commented on YARN-2005:
-------------------------------------

Thanks for your comments Sunil. 
1. Yes we can make it configurable.
2. The nodes are removed from blacklist once the launch of the AM happens to 
limit this issue. (see 
{noformat} // Remove the blacklist added by AM blacklist from shared blacklist) 
{noformat}
The root cause is there is no difference in YARN for scheduling AM vs normal 
containers. They hence share the blacklist as well.
Let me know if you still feel this is an issue, otherwise i can fix 1 and 
upload a new iteration.

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

Reply via email to