You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Daryn Sharp (JIRA)" <ji...@apache.org> on 2012/04/23 17:29:36 UTC

[jira] [Created] (HDFS-3312) Hftp selects wrong token service

Daryn Sharp created HDFS-3312:
---------------------------------

             Summary: Hftp selects wrong token service
                 Key: HDFS-3312
                 URL: https://issues.apache.org/jira/browse/HDFS-3312
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: hdfs client
    Affects Versions: 0.24.0, 0.23.3, 2.0.0
            Reporter: Daryn Sharp
            Assignee: Daryn Sharp
            Priority: Blocker


Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

        

[jira] [Updated] (HDFS-3312) Hftp selects wrong token service

Posted by "Daryn Sharp (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daryn Sharp updated HDFS-3312:
------------------------------

    Status: Patch Available  (was: Open)
    
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

        

[jira] [Closed] (HDFS-3312) Hftp selects wrong token service

Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun C Murthy closed HDFS-3312.
-------------------------------

    
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0-alpha
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>             Fix For: 0.23.3, 2.0.2-alpha
>
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

[jira] [Commented] (HDFS-3312) Hftp selects wrong token service

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259713#comment-13259713 ] 

Hadoop QA commented on HDFS-3312:
---------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12523807/HDFS-3312.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 1 new or modified test files.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit warnings.

    +1 core tests.  The patch passed unit tests in .

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2313//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2313//console

This message is automatically generated.
                
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

        

[jira] [Commented] (HDFS-3312) Hftp selects wrong token service

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260532#comment-13260532 ] 

Hudson commented on HDFS-3312:
------------------------------

Integrated in Hadoop-Mapreduce-trunk #1059 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1059/])
    HDFS-3312. In HftpFileSystem, the namenode URI is non-secure but the delegation tokens have to use secure URI.  Contributed by Daryn Sharp (Revision 1329462)

     Result = FAILURE
szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1329462
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HftpFileSystem.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HsftpFileSystem.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestHftpDelegationToken.java

                
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>             Fix For: 0.23.3
>
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

        

[jira] [Commented] (HDFS-3312) Hftp selects wrong token service

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260506#comment-13260506 ] 

Hudson commented on HDFS-3312:
------------------------------

Integrated in Hadoop-Hdfs-trunk #1024 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1024/])
    HDFS-3312. In HftpFileSystem, the namenode URI is non-secure but the delegation tokens have to use secure URI.  Contributed by Daryn Sharp (Revision 1329462)

     Result = FAILURE
szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1329462
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HftpFileSystem.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HsftpFileSystem.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestHftpDelegationToken.java

                
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>             Fix For: 0.23.3
>
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

        

[jira] [Commented] (HDFS-3312) Hftp selects wrong token service

Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259967#comment-13259967 ] 

Tsz Wo (Nicholas), SZE commented on HDFS-3312:
----------------------------------------------

For hftp, the NN URI is non-secure but the dt needs to use secure URI.
For hsftp, the NN URI is secure and the dt uses the same URI.

+1 patch looks good.

One minor suggestion for the future: we may use the scheme of nnUri in HftpFileSystem.getNamenodeURL(..).  Then HsftpFileSystem.openConnection(..) could also use HftpFileSystem.getNamenodeURL(..).
                
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

        

[jira] [Commented] (HDFS-3312) Hftp selects wrong token service

Posted by "Daryn Sharp (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260067#comment-13260067 ] 

Daryn Sharp commented on HDFS-3312:
-----------------------------------

bq. One minor suggestion for the future: we may use the scheme of nnUri in HftpFileSystem.getNamenodeURL(..). Then HsftpFileSystem.openConnection(..) could also use HftpFileSystem.getNamenodeURL(..).

I noticed that too.  Hsftp isn't using the secure port for data transfers.  I already made a patch and test for it, but when I tried to run the hftp tests with hsftp it produced some bizarre exceptions that I haven't had a chance to debug.
                
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>             Fix For: 0.23.3
>
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

        

[jira] [Updated] (HDFS-3312) Hftp selects wrong token service

Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo (Nicholas), SZE updated HDFS-3312:
-----------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.23.3
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

I have committed this.  Thanks, Daryn!
                
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>             Fix For: 0.23.3
>
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

        

[jira] [Commented] (HDFS-3312) Hftp selects wrong token service

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259979#comment-13259979 ] 

Hudson commented on HDFS-3312:
------------------------------

Integrated in Hadoop-Common-trunk-Commit #2120 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2120/])
    HDFS-3312. In HftpFileSystem, the namenode URI is non-secure but the delegation tokens have to use secure URI.  Contributed by Daryn Sharp (Revision 1329462)

     Result = SUCCESS
szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1329462
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HftpFileSystem.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HsftpFileSystem.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestHftpDelegationToken.java

                
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>             Fix For: 0.23.3
>
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

        

[jira] [Commented] (HDFS-3312) Hftp selects wrong token service

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259977#comment-13259977 ] 

Hudson commented on HDFS-3312:
------------------------------

Integrated in Hadoop-Hdfs-trunk-Commit #2194 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2194/])
    HDFS-3312. In HftpFileSystem, the namenode URI is non-secure but the delegation tokens have to use secure URI.  Contributed by Daryn Sharp (Revision 1329462)

     Result = SUCCESS
szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1329462
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HftpFileSystem.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HsftpFileSystem.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestHftpDelegationToken.java

                
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>             Fix For: 0.23.3
>
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

        

[jira] [Updated] (HDFS-3312) Hftp selects wrong token service

Posted by "Daryn Sharp (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daryn Sharp updated HDFS-3312:
------------------------------

    Attachment: HDFS-3312.patch

Update hftp to use secure port to find tokens.  Prior changes will select tokens based on uri, so updated hftp and hftps to store uris instead of socket addrs for the secure and non-secure uris.
                
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

        

[jira] [Commented] (HDFS-3312) Hftp selects wrong token service

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259997#comment-13259997 ] 

Hudson commented on HDFS-3312:
------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #2136 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2136/])
    HDFS-3312. In HftpFileSystem, the namenode URI is non-secure but the delegation tokens have to use secure URI.  Contributed by Daryn Sharp (Revision 1329462)

     Result = SUCCESS
szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1329462
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HftpFileSystem.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HsftpFileSystem.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestHftpDelegationToken.java

                
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>             Fix For: 0.23.3
>
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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

        

[jira] [Commented] (HDFS-3312) Hftp selects wrong token service

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HDFS-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260480#comment-13260480 ] 

Hudson commented on HDFS-3312:
------------------------------

Integrated in Hadoop-Hdfs-0.23-Build #237 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/237/])
    svn merge -c 1329462 from trunk for HDFS-3312. In HftpFileSystem, the namenode URI is non-secure but the delegation tokens have to use secure URI. (Revision 1329465)

     Result = SUCCESS
szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1329465
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs
* /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java
* /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HftpFileSystem.java
* /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HsftpFileSystem.java
* /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestHftpDelegationToken.java

                
> Hftp selects wrong token service
> --------------------------------
>
>                 Key: HDFS-3312
>                 URL: https://issues.apache.org/jira/browse/HDFS-3312
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.24.0, 0.23.3, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>             Fix For: 0.23.3
>
>         Attachments: HDFS-3312.patch
>
>
> Hftp tries to select a token based on the non-secure port in the uri, instead of the secure-port.  This breaks hftp on a secure cluster and there is no workaround.

--
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