hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2074) Preemption of AM containers shouldn't count towards AM failures
Date Thu, 22 May 2014 03:08:38 GMT

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

Jian He commented on YARN-2074:
-------------------------------

bq. Use this condition to decide whether this RMAppAttempt is isLastAttempt
Actually the isLastAttempt boolean is not used for determining whether to restart the AM ,
the method getAttemptFailureCount is used to do that. Will rename this boolean flag to avoid
confusion.
bq. maybe we could use a more general way to check whether the AM is isPreempted, (check ContainerExitStatus
instead
 thinking about this. To do this we need to persist the ContainerExitStatus in state store
also.

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

Mime
View raw message