[
https://issues.apache.org/jira/browse/HDFS-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252563#comment-13252563
]
Todd Lipcon commented on HDFS-3255:
-----------------------------------
Hm, I'm just surprised, because it seemed to work when we tested running MR
against an HA cluster. But maybe there's some bug that happens when it comes
time to renew the token, or something?
bq. I can see if I can use Jitendra's feature to enable security for a unit
test if you'd like.
When I tried to use that feature, I couldn't get it to work. Maybe you'll have
better luck?
If you can describe a manual test scenario that seems good enough for me.
> HA DFS returns wrong token service
> ----------------------------------
>
> Key: HDFS-3255
> URL: https://issues.apache.org/jira/browse/HDFS-3255
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, hdfs client
> Affects Versions: 2.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HDFS-3255.patch
>
>
> {{fs.getCanonicalService()}} must be equal to
> {{fs.getDelegationToken(renewer).getService()}}. When HA is enabled, the DFS
> token's service is a logical uri, but {{dfs.getCanonicalService()}} is only
> returning the hostname of the logical uri.
--
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
