hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jitendra Nath Pandey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2764) Fix renewal of dfs delegation tokens
Date Fri, 05 Aug 2011 18:29:27 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080128#comment-13080128

Jitendra Nath Pandey commented on MAPREDUCE-2764:

> I'll probably need to add a FileSystem.getDelegationToken-s- which will return a collection
of tokens.
 I didn't get that, how will multiple tokens solve this problem? Currently, only one token
can be passed in the URL for hftp calls, and it is that token which needs to be renewed by
JT and the same token is eventually used for rpc.

> Iff we are going back to copy-n-paste...
 There may be some code repeated in current code base. All I am recommending is to do that
refactoring in a separate jira. My point was that, if we don't do that refactoring in this
patch only DelegationTokenSelector will need to change. 

> The getServiceAuthority() is extracting the authority from the service if it's a uri,
else it uses the 
> service itself if it's not a uri.
>The the service is currently "authority", and I changed it to be either "authority" or
>"scheme://authority". I'd like to eventually move everything to "scheme://authority" hence
the >compatibility.

 The problem is that we can't use same authority for both rpc and hftp, because ports are

> Fix renewal of dfs delegation tokens
> ------------------------------------
>                 Key: MAPREDUCE-2764
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2764
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>             Fix For:
>         Attachments: MAPREDUCE-2764.patch
> The JT may have issues renewing hftp tokens which disrupt long distcp jobs.  The problem
is the JT's delegation token renewal code is built on brittle assumptions.  The token's service
field contains only the "ip:port" pair.  The renewal process assumes that the scheme must
be hdfs.  If that fails due to a {{VersionMismatchException}}, it tries https based on another
assumption that it must be hftp if it's not hdfs.  A number of other exceptions, most commonly
{{IOExceptions}}, can be generated which fouls up the renewal since it won't fallback to https.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message