hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2904) HA: Client support for getting delegation tokens to an HA cluster
Date Fri, 17 Feb 2012 21:28:57 GMT

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

Todd Lipcon commented on HDFS-2904:

bq. Currently, hftp and webhdfs actually set a different service in the token (port is https
port instead of rpc port). Tokens issued by hftp, and webhdfs may not work with the logical
namespaceid in the service, because logical namespaceid would resolve to ipc port only?

I'm not sure I follow what you mean here... given that HFTP and webhdfs are HTTP-based, they
fall under the scope of HDFS-2292. We should address those there along with the rest of HA
for those services.

bq.  The main problem is that the service is set at the client where information about the
standby may not be available.

Given that, does the current design seem like the best option? Since this design choice doesn't
get exposed to users anyway, I think it's reasonable to commit as is, and if we figure out
a better way later we can change it would changing anything user-facing.
> HA: Client support for getting delegation tokens to an HA cluster
> -----------------------------------------------------------------
>                 Key: HDFS-2904
>                 URL: https://issues.apache.org/jira/browse/HDFS-2904
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha, hdfs client, name-node, security
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>         Attachments: hdfs-2904.txt, hdfs-2904.txt, hdfs-2904.txt, test-dt.sh
> Currently we have server-side support for delegation tokens in HA, and some tests to
verify it, but the client throws NPEs when trying to fetch a DT. This is because the cluster
doesn't have a single hostname, but instead a logical nameservice name.

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


View raw message