[
https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739073#comment-13739073
]
Bikas Saha commented on YARN-1055:
----------------------------------
Restart on am failure is already determined by the default value of max am
retries in yarn config. Setting that to 1 will prevent RM from restarting AM's
on failure. Thus no need for new config. Restart after RM restart is already
covered by setting max am retries to 1 by the app client on app submission. If
an app cannot handle this situation it should create its own config and set the
correct value of 1 on submission. YARN should not add a config IMO. If I
remember right, this config is being imported from hadoop 1 and the impl of
this config in hadoop 1 is what RM already does to handle user defined max am
retries.
> 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
