[
https://issues.apache.org/jira/browse/HDFS-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105380#comment-13105380
]
Daryn Sharp commented on HDFS-2336:
-----------------------------------
While it may have been intended for hdfs, I do not see a nn limitation that
would prevent it from using an alternate filesystem. Whereas the new renewal
assumes hdfs, and as such will force a hftp token kind to be hdfs. As best I
can tell, and perhaps I'm wrong, the nn uses the default filesystem for hftp.
This is because the nn servlets create a proxy to the nn to perform
filesystem-based requests. Am I misreading the code?
> hftp only supports remote hdfs servers
> --------------------------------------
>
> Key: HDFS-2336
> URL: https://issues.apache.org/jira/browse/HDFS-2336
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.20.205.0, 0.23.0
> Reporter: Daryn Sharp
> Fix For: 0.23.0
>
>
> The new token renewal implementation appears to introduce invalid assumptions
> regarding token kinds.
> Any token acquired over http is assumed to be hftp, so the kind is
> unconditionally changed to hftp. This precludes the acquisition of any other
> token types over http. This new limitation was added to a generic method in
> a public class. It should have been encapsulated in the hftp class, not the
> generic http token fetching methods.
> Furthermore, hftp will unconditionally change a hftp token's kind to hdfs. I
> believe this assumption means that hftp is now broken if the remote cluster's
> default filesystem is not hdfs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
