[
https://issues.apache.org/jira/browse/HDFS-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198492#comment-14198492
]
Hudson commented on HDFS-7233:
------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1948 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1948/])
HDFS-7233. NN logs unnecessary
org.apache.hadoop.hdfs.protocol.UnresolvedPathException. Contributed by Rushabh
S Shah. (jing9: rev 5bd3a569f941ffcfc425a55288bec78a37a75aa1)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNodeRpcServer.java
> NN logs unnecessary org.apache.hadoop.hdfs.protocol.UnresolvedPathException
> ---------------------------------------------------------------------------
>
> Key: HDFS-7233
> URL: https://issues.apache.org/jira/browse/HDFS-7233
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 2.5.1
> Reporter: Rushabh S Shah
> Assignee: Rushabh S Shah
> Fix For: 2.6.0
>
> Attachments: HDFS-7233.patch
>
>
> Namenode logs the UnresolvedPathExceptioneven though that file exists in HDFS.
> Each time a symlink is accessed the NN will
> throw an UnresolvedPathException to have the client resolve it. This
> shouldn't
> be logged in the NN log and we could have really large NN logs if we
> don't fix this since every MR job on the cluster will access this symlink and
> cause a stacktrace to be logged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
