[
https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740576#comment-13740576
]
Vinod Kumar Vavilapalli commented on YARN-1055:
-----------------------------------------------
Same here :) We do really understand the underlying issue, was just trying to
converge on the correct solution. To summarize
- For the restart-case, work preserving case solves the problem of not killing
AM unnecessarily
- For node failures or AM crashing, we already have a knob. To avoid split
brain issues, oozie/Pig/Hive all need to implement restartability for their
launchers.
Given the later isn't coming in a rush, we should make oozie set max-attempts
to 1 for the launcher.
Regarding the question of dependent AMs, dependent or not, YARN will only
restart AM by AM. If the apps care, they need to implement recoverability.
> 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
