Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1340769351.1207943884868.JavaMail.jira@brutus>
Date: Fri, 11 Apr 2008 12:58:04 -0700 (PDT)
From: "Raghu Angadi (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3239) exists() calls logs
 FileNotFoundException in namenode log
In-Reply-To: <906041294.1207941725050.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Is it enough if RPC does not log these?

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