[
https://issues.apache.org/jira/browse/HDFS-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156217#comment-13156217
]
Hadoop QA commented on HDFS-2589:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12504914/HDFS-2589.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1607//console
This message is automatically generated.
> 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: 0.20.205.1
> 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
