[
https://issues.apache.org/jira/browse/HADOOP-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588109#action_12588109
]
Konstantin Shvachko commented on HADOOP-3239:
---------------------------------------------
> Is it enough if RPC does not log these?
That would be enough if RPC could distinguish between exceptions that need to
be logged and those that don't.
But this is impossible in general. E.g. the FileNotFoundException being thrown
in case of open() needs to be logged while thrown in exists() should not be.
> exists() calls logs FileNotFoundException in namenode log
> ---------------------------------------------------------
>
> Key: HADOOP-3239
> URL: https://issues.apache.org/jira/browse/HADOOP-3239
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.17.0
> Reporter: lohit vijayarenu
>
> exists() was modified to invoke getFileStatus() internally. But
> getFileStatus() throws FileNotFoundException for files which does not exists
> and this is logged in RPC$Server for each exists() call. One way to get rid
> of these messages is at the Name Node, catch FileNotFoundException and return
> null. In this case, RPC would not log it in namenode log. But at the client
> end we might have to check for null on all calls of getFileStatus(). Other
> option at client end is to construct FileNotFoundException() when
> getFileInfo() returns null.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
