You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-dev@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2013/04/30 20:12:15 UTC

[jira] [Resolved] (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:all-tabpanel ]

Vinod Kumar Vavilapalli resolved YARN-579.
------------------------------------------

    Resolution: Fixed

I can consistently reproduce this on branch-2 but trunk is fine.

Not sure if this was caused indeed by this ticket itself or not. Still investigating. Closing this and continuing investigation on YARN-626.
                
> 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
>             Fix For: 2.0.5-beta
>
>         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