[
https://issues.apache.org/jira/browse/HDFS-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213101#comment-13213101
]
Todd Lipcon commented on HDFS-2904:
-----------------------------------
{quote}
> logical URI is "hdfs://my-ha-cluster/"
You don't literally mean "my-ha-cluster" as a logical name for a cluster since
a cluster can have multiple NN int federation, Perhaps by this you mean using
the namespaceid has the logical name of the NN.
{quote}
Right - I should have written "hdfs://my-ha-namespace/". But the implementation
is the same.
{quote}
Another related issue: when a customer moves from a Non-HA NN to HA-NN then it
does NOT expect its URIs to change. In this case they could use old NN dns name
as the logical name of the NN.
{quote}
Yep - this is discussed in HDFS-2839.
----
I couldn't tell from your comment - are you OK with the current design/patch?
> 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
