hadoop-yarn-issues mailing list archives

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

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

Vinod Kumar Vavilapalli commented on YARN-701:
----------------------------------------------

[~tucu00], Unamanged AM was (always?) broken even before this JIRA in secure mode. Surely
this JIRA worsens it by breaking it in non-secure mode too, but YARN-701 isn't specifically
the only culprit. So not sure about linking the two. But if enough people care about Unmanaged
AM for the next release, we should fix it.
                
> 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