You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Rushabh S Shah (JIRA)" <ji...@apache.org> on 2014/10/11 00:34:34 UTC

[jira] [Updated] (HDFS-7233) NN logs unnecessary org.apache.hadoop.hdfs.protocol.UnresolvedPathException

     [ https://issues.apache.org/jira/browse/HDFS-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rushabh S Shah updated HDFS-7233:
---------------------------------
    Attachment: HDFS-7233.patch

Adding UnresolvedPathException to the list of TerseExceptions.
There is no test case in the patch but verified on my single node setup and confirmed that there is no stack trace in the log.

> 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: Bug
>    Affects Versions: 2.5.1
>            Reporter: Rushabh S Shah
>            Assignee: Rushabh S Shah
>         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)