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

["lohit vijayarenu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

lohit vijayarenu updated HADOOP-3239:
-------------------------------------

    Attachment: HADOOP-3239-1.patch

Attached patch does these
- getFileInfo at namenode returns null if file not found
- getFileInfo at DFSClient passes null above as is
- exists uses null to identify if file exists
- getFileStatus checks for null and throws FileNotFoundException
- added a testcase to make sure getFileInfo returns null for non existing files

> 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
>            Assignee: lohit vijayarenu
>         Attachments: HADOOP-3239-1.patch
>
>
> 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.