[
https://issues.apache.org/jira/browse/HDFS-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654803#comment-13654803
]
Hadoop QA commented on HDFS-4805:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12582657/HDFS-4805.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/4377//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4377//console
This message is automatically generated.
> Webhdfs client is fragile to token renewal errors
> -------------------------------------------------
>
> Key: HDFS-4805
> URL: https://issues.apache.org/jira/browse/HDFS-4805
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HDFS-4805.patch
>
>
> Webhdfs internally acquires a token that will be used for DN-based
> operations. The token renewer in common will try to renew that token. If a
> renewal fails for any reason, it will try to get another token. If that
> fails, it gives up and the token webhdfs holds will soon expire.
> A transient network outage or a restart of the NN may cause webhdfs to be
> left holding an expired token, effectively rendering webhdfs useless. This
> is fatal for daemons.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
