[
https://issues.apache.org/jira/browse/HDFS-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656955#comment-13656955
]
Hudson commented on HDFS-4805:
------------------------------
Integrated in Hadoop-Yarn-trunk #209 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/209/])
HDFS-4805. Webhdfs client is fragile to token renewal errors. Contributed
by Daryn Sharp. (Revision 1482121)
Result = SUCCESS
kihwal : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1482121
Files :
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/DelegationTokenRenewer.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/web/WebHdfsFileSystem.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/web/TestWebHdfsTokens.java
> 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
