You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Subru Krishnan (JIRA)" <ji...@apache.org> on 2016/06/01 19:07:59 UTC
[jira] [Updated] (YARN-1815) Work preserving recovery of Unmanged
AMs
[ https://issues.apache.org/jira/browse/YARN-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Subru Krishnan updated YARN-1815:
---------------------------------
Attachment: YARN-1815-v5.patch
Attaching new patch (v5) with minor update to *TestRMAppAttemptTransitions* to check if UAM final state is saved in RMStateStore
> Work preserving recovery of Unmanged AMs
> ----------------------------------------
>
> Key: YARN-1815
> URL: https://issues.apache.org/jira/browse/YARN-1815
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.3.0
> Reporter: Karthik Kambatla
> Assignee: Subru Krishnan
> Priority: Critical
> Attachments: Unmanaged AM recovery.png, YARN-1815-v3.patch, YARN-1815-v4.patch, YARN-1815-v5.patch, yarn-1815-1.patch, yarn-1815-2.patch, yarn-1815-2.patch
>
>
> Currently work preserving RM restart recovers unmanaged AMs but it has a couple of shortcomings - all running containers are killed and completed unmanaged AMs are also recovered as we do _not_ record final state for unmanaged AMs in the RM StateStore. This JIRA proposes to address both the shortcomings so that work preserving unmanaged AM recovery works exactly like with managed AMs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org