hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2326) hftp token renewal uses wrong port
Date Tue, 13 Sep 2011 15:14:09 GMT

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

Daryn Sharp commented on HDFS-2326:

I did not actually see/test for this possible issue.  It's based on reading the code while
ensuring that the changes are compatible with the ip->host change.  The multiple code paths
for the token's service manipulation is a bit tricky.  Did you also test the cases where a
{{HarFileSystem}} is directly instantiated, that it works when it acquires the token itself
and schedules its own renewal?

> hftp token renewal uses wrong port
> ----------------------------------
>                 Key: HDFS-2326
>                 URL: https://issues.apache.org/jira/browse/HDFS-2326
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions:
>            Reporter: Daryn Sharp
>            Priority: Critical
>             Fix For:
> MAPREDUCE-2764 introduced a new method for token renewal.  The change appears to have
a problem renewing hftp tokens.  The {{setDelegationToken}} method will reset the token's
service to contain the remote rpc port.  However, the renewer expects it to be the remote
https port.

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


View raw message