hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3380) Token infrastructure for running clients which are not kerberos authenticated
Date Wed, 11 Jan 2012 00:38:40 GMT

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

Vinod Kumar Vavilapalli updated MAPREDUCE-3380:
-----------------------------------------------

    Attachment: MAPREDUCE-3380-20120110.1.txt


+1 overall. Cleaned the patch a bit.
 - Adding extra check for Kerberos authentication when asking for delegation tokens
 - Reusing the same record DelegationToken for both RM side and JHS side tokens
 - Removed unnecessary changes to minimize the patch size and to make it tractable for review.
 - There may be better ways to populate the history related delegation tokens but the current
one to pass around info via conf should do the trick for now.
                
> Token infrastructure for running clients which are not kerberos authenticated
> -----------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3380
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3380
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: mr-am, mrv2
>    Affects Versions: 0.23.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Mahadev konar
>            Priority: Blocker
>             Fix For: 0.23.1
>
>         Attachments: MAPREDUCE-3380-20120110.1.txt, MAPREDUCE-3380.branch-0.23.patch,
MAPREDUCE-3380.branch-0.23.patch, MAPREDUCE-3380.patch, MAPREDUCE-3380.patch, MAPREDUCE-3380.patch,
MAPREDUCE-3380.patch, MAPREDUCE-3380.patch, MAPREDUCE-3380_v1.patch
>
>
> The JobClient.getDelegationToken() method is returning NULL, this makes Oozie fail when
trying to get the delegation token to use it for starting a job.
> What is seems to be happing is that Jobclient.getDelegationToken() calls Cluster.getDelegationToken()
that calls YarnRunner.getDelegationToken() that calls ResourceMgrDelegate.getDelegationToken().
And the last one is not implemented. (Thanks Ahmed for tracing this in MR2 code)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message