[jira] Commented: (HADOOP-3239) exists() calls logs FileNotFoundException in namenode log

["Doug Cutting (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588086#action_12588086 ] 

Doug Cutting commented on HADOOP-3239:
--------------------------------------

I think the namenode should return null for getFileInfo(), without having to catch an exception.  And the client should throw an exception for null in getFileStatus() but not in exists().

> 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.