You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jian He (JIRA)" <ji...@apache.org> on 2015/01/15 01:08:36 UTC

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

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

Jian He commented on YARN-1055:
-------------------------------

With work-preserving RM restart, the max-attempts is not required any more. we may close this out ?

> Handle app recovery differently for AM failures and RM restart
> --------------------------------------------------------------
>
>                 Key: YARN-1055
>                 URL: https://issues.apache.org/jira/browse/YARN-1055
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 2.1.0-beta
>            Reporter: Karthik Kambatla
>
> Ideally, we would like to tolerate container, AM, RM failures. App recovery for AM and RM currently relies on the max-attempts config; tolerating AM failures requires it to be > 1 and tolerating RM failure/restart requires it to be = 1.
> We should handle these two differently, with two separate configs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)