[
https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739109#comment-13739109
]
Karthik Kambatla commented on YARN-1055:
----------------------------------------
>From a YARN-user POV, I see it differently. I want to control whether my app
>should be recovered on AM/RM failures separately. I might want to recover on
>RM restart but not on AM failures or viceversa:
# In case of AM failure, user might want to check for user errors and hence not
recover. But recover in case of RM failures.
# Like Oozie, might want to recover on AM failures but not on RM failures.
Also, is there a disadvantage to having two knobs for the two failures?
> 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
