[
https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740362#comment-13740362
]
Karthik Kambatla commented on YARN-1055:
----------------------------------------
As in my comment from above
(https://issues.apache.org/jira/browse/YARN-1055?focusedCommentId=13737487&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13737487),
max-am-retries is not enough for Oozie without significant changes to how
Oozie launcher is implemented.
To work around this, Oozie launcher will have to monitor the action and
re-submit the action in case the action AM fails
> 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
