[
https://issues.apache.org/jira/browse/YARN-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505427#comment-13505427
]
Tom White commented on YARN-230:
--------------------------------
bq. But it could make sense to remove application attempts but not remove the
application, couldn't it? Say we want to remove some attempt from the saved
state before the application is done.
Let's add it when we need it then.
bq. We also need to change the AM retry default to > 1. Otherwise, even with RM
restart enabled, the restarted attempts will fail because the previous AM will
delete job files. What is your suggestion for that?
I think this is where the killed/failed distinction comes in. If the app
attempt was killed (because the RM died), then the app will be retried since
the first attempt didn't count (from the point of view of
yarn.resourcemanager.am.max-retries). This should be taken care of in YARN-218
- does that sound OK to you?
> Make changes for RM restart phase 1
> -----------------------------------
>
> Key: YARN-230
> URL: https://issues.apache.org/jira/browse/YARN-230
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: PB-impl.patch, Recovery.patch, Store.patch, Test.patch,
> YARN-230.1.patch
>
>
> As described in YARN-128, phase 1 of RM restart puts in place mechanisms to
> save application state and read them back after restart. Upon restart, the
> NM's are asked to reboot and the previously running AM's are restarted.
> After this is done, RM HA and work preserving restart can continue in
> parallel. For more details please refer to the design document in YARN-128
--
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
