Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-5802

NameNode does not check for inode type before traversing down a path

    Details

    • Hadoop Flags:
      Reviewed

      Description

      This came up during the discussion on a forum at http://community.cloudera.com/t5/Batch-Processing-and-Workflow/Permission-denied-access-EXECUTE-on-getting-the-status-of-a-file/m-p/5049#M162 surrounding an fs.exists(…) check running on a path /foo/bar, where /foo is a file and not a directory.

      In such a case, NameNode yields a user-confusing message of Permission denied: user=foo, access=EXECUTE, inode="/foo":foo:foo:rw-rr- instead of clearly saying (and realising) "/foo is not a directory" or "/foo is a file" before it tries to traverse further down to locate the requested path.

        Attachments

        1. HDFS-5802.006.patch
          4 kB
          Xiao Chen
        2. HDFS-5802.005.patch
          4 kB
          Xiao Chen
        3. HDFS-5802.004.patch
          4 kB
          Xiao Chen
        4. HDFS-5802.003.patch
          4 kB
          Xiao Chen
        5. HDFS-5802.002.patch
          4 kB
          Xiao Chen
        6. HDFS-5802.001.patch
          4 kB
          Xiao Chen

          Issue Links

            Activity

              People

              • Assignee:
                xiaochen Xiao Chen
                Reporter:
                qwertymaniac Harsh J
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: