[
https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740446#comment-13740446
]
Robert Kanter commented on YARN-1055:
-------------------------------------
Another way of phrasing this: when the action's AM dies, we want to recover it
(and the launcher can still monitor it with JobClient as-is), but if the action
and launcher AMs both die due to an RM restart, we don't want to recover the
action's AM. Hence in the first case, we'd want the max-am-retries set to >1
and in the second case we'd want it set to =1. But it can't be both.
> 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 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
