hadoop-common-dev mailing list archives

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

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

Konstantin Shvachko commented on HADOOP-3239:
---------------------------------------------

> should go in 0.17?

Formally, it is not a regression in terms of performance or functionality.
Informally, it is an annoying message, and we will have to answer questions until people will
get used to it.
I'd schedule it for 0.17.

> 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