hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-701) ApplicationTokens should be used irrespective of kerberos
Date Wed, 17 Jul 2013 21:47:46 GMT

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

Alejandro Abdelnur commented on YARN-701:
-----------------------------------------

on my previous comment, fixing the unmanaged AM should be a blocker if this JIRA (YARN-701)
goes in. In other words, both JIRAs should be committed in tandem (in the same release).


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