[jira] [Updated] (YARN-2005) Blacklisting support for scheduling AMs

["Anubhav Dhoot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anubhav Dhoot updated YARN-2005:
--------------------------------
    Attachment: YARN-2005.007.patch

Attached patch makes a couple of changes. Instead of adding a new scheduler api it uses the same allocate call to update the system blacklist. The scheduler updates and uses system/user blacklist based on whether its a AM launch or not. 
It also tracks the cause of the container failure to decide whether to blacklist the Node or not. If we need to consider other reasons for blacklisting I propose we use followup jiras in order to make progress on this one.

> 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, YARN-2005.005.patch, YARN-2005.006.patch, YARN-2005.006.patch, YARN-2005.007.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)