hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3239) exists() calls logs FileNotFoundException in namenode log
Date Fri, 11 Apr 2008 19:50:05 GMT

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

Raghu Angadi commented on HADOOP-3239:
--------------------------------------

getFileInfo() used to return null. This was changed couple of months back during fixes to
various shell commands and APIs. I am not sure the actual reason behind it, may be consistency.
Returning null for non-existent files is good.

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


Mime
View raw message