[jira] [Commented] (YARN-2074) Preemption of AM containers shouldn't count towards AM failures

["Wangda Tan (JIRA)" <ji...@apache.org>]

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

Wangda Tan commented on YARN-2074:
----------------------------------

Can we populate "attemptFailureCount" to AM when AM registering? This should be a valuable fix, other applications besides MR can benefit from this too. I think it's better to create a separated JIRA to track this.
[~jianhe], [~mayank_bansal] Any thoughts? 

> 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: Jian He
>         Attachments: YARN-2074.1.patch, YARN-2074.2.patch, YARN-2074.3.patch
>
>
> 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)