Anubhav Dhoot commented on YARN-2005:

Hi [~kasha] thanks for your comments.

2.4 - we do not need to update the systemBlacklist as its updated by the 
RMAppAttemptImpl#ScheduleTransition call every time to the complete list. 
11, 12 - The changes were needed because now we need a valid submission context 
for isWaitingForAMContainer.
9 - Is needed by the new test added in TestAMRestart.
8.3 - Yes i can file a follow up for that
Addressed rest of them

> 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, 
> YARN-2005.008.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

Reply via email to