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-579) Make ApplicationToken part of Container's token list to help RM-restart
Date Thu, 25 Apr 2013 02:26:16 GMT

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

Bikas Saha commented on YARN-579:

appToken is attempt specific. So it needs to be store per app attempt. So it needs to be generated
when app attempt is assigned a container and saved in appAttemptStateData. Basically the code
needs to be moved from AMLauncher to the rmappattempimpl. AMLauncher will simply use the token
from the attempt.
> Make ApplicationToken part of Container's token list to help RM-restart
> -----------------------------------------------------------------------
>                 Key: YARN-579
>                 URL: https://issues.apache.org/jira/browse/YARN-579
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 2.0.4-alpha
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>         Attachments: YARN-579-20130422.1.txt, YARN-579-20130422.1_YARNChanges.txt
> Container is already persisted for helping RM restart. Instead of explicitly setting
ApplicationToken in AM's env, if we change it to be in Container, we can avoid env and can
also help restart.

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