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 "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/04/16 18:39:16 UTC
[jira] [Commented] (YARN-579) Make ApplicationToken part of
Container's token list to help RM-restart
[ https://issues.apache.org/jira/browse/YARN-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632992#comment-13632992 ]
Bikas Saha commented on YARN-579:
---------------------------------
In order to help restart, creation of appToken needs to move out from AMLauncher. AppToken needs to be set before the app attempt is saved. App attempt is saved after masterContainer is received from scheduler.
> 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
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> 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