Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-3239

exists() calls logs FileNotFoundException in namenode log

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.17.0
    • 0.17.0
    • None
    • None
    • Incompatible change, Reviewed
    • getFileInfo returns null for File not found instead of throwing FileNotFoundException

    Description

      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.

      Attachments

        1. HADOOP-3239-1.patch
          8 kB
          Lohit Vijaya Renu
        2. HADOOP-3239-2.patch
          8 kB
          Lohit Vijaya Renu

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            lohit Lohit Vijaya Renu
            lohit Lohit Vijaya Renu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment