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

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.1.0-beta
    • namenode
    • 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

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

          People

            brandonli Brandon Li
            brandonli Brandon Li
            Votes:
            0 Vote for this issue
            Watchers:
            18 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment