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

Use InodeID as as an identifier of a file in HDFS protocols and APIs

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

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.0-beta
    • Component/s: namenode
    • Labels:
      None

      Description

      The benefit of using InodeID to uniquely identify a file can be multiple folds. Here are a few of them:

      1. uniquely identify a file cross rename, related JIRAs include HDFS-4258, HDFS-4437.
      2. modification checks in tools like distcp. Since a file could have been replaced or renamed to, the file name and size combination is no t reliable, but the combination of file id and size is unique.
      3. id based protocol support (e.g., NFS)
      4. to make the pluggable block placement policy use fileid instead of filename (HDFS-385).

        Attachments

        1. 4434.optimized.patch
          82 kB
          Suresh Srinivas

        Issue Links

          Activity

            People

            • Assignee:
              brandonli Brandon Li
              Reporter:
              brandonli Brandon Li

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment