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-701) ApplicationTokens should be used irrespective of kerberos
Date Wed, 24 Jul 2013 05:59:49 GMT

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

Bikas Saha commented on YARN-701:
---------------------------------

How does this affect RM restart in general? Do the new AMRMTokens need to be added to the
stored app attempt? How does this change if the RM is restarted on a different node? Is the
service address check based on whats encoded in the token or based on the current node?
                
> ApplicationTokens should be used irrespective of kerberos
> ---------------------------------------------------------
>
>                 Key: YARN-701
>                 URL: https://issues.apache.org/jira/browse/YARN-701
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 2.1.0-beta
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>            Priority: Blocker
>             Fix For: 2.1.0-beta
>
>         Attachments: YARN-701-20130520.txt, YARN-701-20130709.3.txt, YARN-701-20130710.txt,
YARN-701-20130712.txt, YARN-701-20130717.txt, yarn-ojoshi-resourcemanager-HW10351.local.log
>
>
>  - Single code path for secure and non-secure cases is useful for testing, coverage.
>  - Having this in non-secure mode will help us avoid accidental bugs in AMs DDos'ing
and bringing down RM.

--
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

Mime
View raw message