[
https://issues.apache.org/jira/browse/HADOOP-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588088#action_12588088
]
Raghu Angadi commented on HADOOP-3239:
--------------------------------------
I don't think RPC should dictate what exception NameNode should throw. I think
it should still throw FileNotFound. There is probably a way not to log
selected exceptions at the RPC server. In fact the server should not log the
exceptions that it is sending the client actually! may be except
RuntimeExceptions.
> 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.
