hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-582) Restore appToken and clientToken for app attempt after RM restart
Date Mon, 29 Apr 2013 20:44:16 GMT

    [ https://issues.apache.org/jira/browse/YARN-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644845#comment-13644845

Bikas Saha commented on YARN-582:

The RMStore stores applications and their attempts. And it is used to restore applications
and their attempts from the data that they had earlier stored. This allows the recovery code
to follow existing code paths to the fullest extent and prevent recovery logic from diverging
from the "normal" code path. So I would like to avoid storing tokens separately from apps/attempts
and then have to manage their relationship later on during recovery. As far as saving appToken
and clientToken, I agree it would be nice to have a single object store all attempt tokens
in one place. At AppSubmitContext does that for app tokens.
> Restore appToken and clientToken for app attempt after RM restart
> -----------------------------------------------------------------
>                 Key: YARN-582
>                 URL: https://issues.apache.org/jira/browse/YARN-582
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Bikas Saha
>            Assignee: Jian He
>         Attachments: YARN-582.1.patch
> These need to be saved and restored on a per app attempt basis. This is required only
when work preserving restart is implemented for secure clusters. In non-preserving restart
app attempts are killed and so this does not matter.

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

View raw message