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

Sunil G commented on YARN-2074:
-------------------------------

Hi Vinod

As per the description I understood that the AM container can get preempted as 
happening now, and the resultant kill/preemption should not result in Job 
failures.
In this scenario also, we may kill some AM containers and it has to re-launch. 
By keeping a lower priority for all AM's may help to kill map/reducer container 
from other applications in similar scenario.

As Carlo has mentioned in YARN-2022, there can be extreme corner cases for this 
approach. But may help in avoiding the cost of re-launching AM container again.
Could you please consider this point also in this Jira.

> Preemption of AM containers shouldn't count towards AM failures
> ---------------------------------------------------------------
>
>                 Key: YARN-2074
>                 URL: https://issues.apache.org/jira/browse/YARN-2074
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>
> One orthogonal concern with issues like YARN-2055 and YARN-2022 is that AM 
> containers getting preempted shouldn't count towards AM failures and thus 
> shouldn't eventually fail applications.
> We should explicitly handle AM container preemption/kill as a separate issue 
> and not count it towards the limit on AM failures.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to