[
https://issues.apache.org/jira/browse/HDFS-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209010#comment-13209010
]
Todd Lipcon commented on HDFS-2904:
-----------------------------------
{quote}
when the JT renews delegation tokens on behalf of the job, does it pass the
job's jobconf or the jobtracker's local conf? If the latter, it may not have a
local configuration that has the same clusters configured, which would be
problematic.
{quote}
I talked to Mahadev about this and looked in the source. Unfortunately the
RM/JT use their local conf, not the job conf, when renewing delegation tokens.
This means that all HA clusters that will be accessed from MR jobs need to be
present/configured in the conf on the RM for now. Mahadev and I agree this
should not be a blocker for merging HA to trunk, but I will file a follow-up to
figure out a better solution for this when this is committed.
> 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, 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
