hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-534) AM max attempts is not checked when RM restart and try to recover attempts
Date Thu, 04 Apr 2013 19:22:15 GMT

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

Bikas Saha commented on YARN-534:
---------------------------------

Turns out that the max attempts limit is checked when job fails (and tries to launch new attempt)
and not when the new attempt is actually being launched. 
The RM on restart, could choose to remove applications that have already hit the limit.
                
> AM max attempts is not checked when RM restart and try to recover attempts
> --------------------------------------------------------------------------
>
>                 Key: YARN-534
>                 URL: https://issues.apache.org/jira/browse/YARN-534
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Jian He
>            Assignee: Jian He
>
> Currently,AM max attempts is only checked if the current attempt fails and check to see
whether to create new attempt. If the RM restarts before the max-attempt fails, it'll not
clean the state store, when RM comes back, it will retry attempt again.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message