[
https://issues.apache.org/jira/browse/HDFS-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216126#comment-13216126
]
Jitendra Nath Pandey commented on HDFS-2904:
--------------------------------------------
bq. This seems similar to your JIRA HDFS-2839, right? I don't disagree with you
that it would be nice to generalize the concept of logical URIs further, but as
it stands today, it is not general - this patch just works with the existing
design, rather than seeking to change it.
I am concerned that if someone wants to downgrade their cluster from ha to
non-ha and remove proxy provider configuration, they will have to also change
the fs.defaultFS of the cluster from logical uri to actual hostname based uri.
That essentially means it becomes a different cluster because file paths for
this cluster will stop working.
bq. Not sure I follow what you mean here. Before the
ConfiguredFailoverProxyProvider creates a new proxy, it calls this method to
clone the logical-service DT to the physical-address DT it's about to connect
to. So this works with any number of standby nodes.
I see, that makes sense. I understood it differently.
bq. Currently the only thing that can "map to actual service addresses" is the
proxy provider.
Exactly, IMO it shouldn't be the proxy provider, rather a different entity that
proxy provider uses.
I agree these issues should be discussed in a different jira.
+1 for the patch as it makes delegation tokens work for now.
> 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
