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] [Updated] (YARN-701) ApplicationTokens should be used irrespective of kerberos
Date Tue, 09 Jul 2013 22:45:52 GMT

     [ https://issues.apache.org/jira/browse/YARN-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated YARN-701:
-----------------------------------------

    Attachment: YARN-701-20130709.3.txt

Updated patch against latest code base.
 - Enforcing token auth always on ApplicationMasterProtocol
 - Using AMRMToken irrespective of kerberos
 - Fixed tests

One side effect is that Unmanaged AM is completely broken now, even in non-secure mode. Commented
out the test. Will fix it separately.
                
> 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
>
>
>  - 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