[
https://issues.apache.org/jira/browse/HDFS-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158875#comment-13158875
]
Jitendra Nath Pandey commented on HDFS-2589:
--------------------------------------------
I am not too sure about remoteIsInsecure check, because it will be set to true
for any kind of exception.
The patch looks ok to me, otherwise.
> unnecessary hftp token fetch and renewal thread
> -----------------------------------------------
>
> Key: HDFS-2589
> URL: https://issues.apache.org/jira/browse/HDFS-2589
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Attachments: HDFS-2589.patch
>
>
> Instantiation of the hftp filesystem is causing a token to be implicitly
> created and added to a custom token renewal thread. With the new token
> renewal feature in the JT, this causes the mapreduce
> {{obtainTokensForNamenodes}} to fetch two tokens (an implicit and uncancelled
> token, and an explicit token) and leave a spurious renewal thread running.
> This thread should not be running in the JT.
> After speaking with Owen, the quick solution is to lazy fetch the token, and
> to lazy start the renewer thread.
--
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
