You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2008/04/12 00:04:04 UTC

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

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

rangadi edited comment on HADOOP-3239 at 4/11/08 3:02 PM:
---------------------------------------------------------------

You are right. What was changed recently was to throw FileNotFoundException rather than IOException.  The extra logging is because of DFSClient.exists() using getFileInfo().

I still think eventually it would be nice to be able to tell RPC not to log user exceptions or be able to tell which ones to log.

      was (Author: rangadi):
    You are right. What was changed recently was to throw FileNotFoundException rather than IOException.  The extra logging is because of DFSClient.exists() using getFileInfo().

I sting think eventually it would be nice to be able to tell RPC not to log user exceptions or be able to tell which ones to log.
  
> 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.