[
https://issues.apache.org/jira/browse/HDFS-7394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214682#comment-14214682
]
Hudson commented on HDFS-7394:
------------------------------
SUCCESS: Integrated in Hadoop-Hdfs-trunk #1936 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1936/])
HDFS-7394. Log at INFO level, not WARN level, when InvalidToken is seen in
ShortCircuitCache (Keith Pak via Colin P. McCabe) (cmccabe: rev
26d3b7e6ae867596bbced0bfddde22d3c0d976bb)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/shortcircuit/ShortCircuitCache.java
> Log at INFO level, not WARN level, when InvalidToken is seen in
> ShortCircuitCache
> ---------------------------------------------------------------------------------
>
> Key: HDFS-7394
> URL: https://issues.apache.org/jira/browse/HDFS-7394
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Kihwal Lee
> Assignee: Keith Pak
> Priority: Minor
> Fix For: 2.7.0
>
> Attachments: HDFS-7394.patch
>
>
> For long running clients, getting an {{InvalidToken}} exception is expected
> and the client refetches a block token when it happens. The related events
> are logged at INFO except the ones in {{ShortCircuitCache}}. It will be
> better if they are also made to log at INFO.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
