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

Use INode IDs to avoid conflicts when a file open for write is renamed

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.20.1
    • Fix Version/s: 2.5.0
    • Component/s: namenode
    • Labels:
      None
    • Target Version/s:

      Description

      Now that we have a unique INode ID for each INode, clients with files that are open for write can use this unique ID rather than a file path when they are requesting more blocks or closing the open file. This will avoid conflicts when a file which is open for write is renamed, and another file with that name is created.

        Attachments

        1. HDFS-6294.005.patch
          61 kB
          Colin McCabe
        2. HDFS-6294.005.patch
          61 kB
          Colin McCabe
        3. HDFS-6294.004.patch
          61 kB
          Colin McCabe
        4. HDFS-6294.003.patch
          55 kB
          Colin McCabe
        5. HDFS-6294.002.patch
          54 kB
          Colin McCabe
        6. HDFS-6294.001.patch
          45 kB
          Colin McCabe

          Issue Links

            Activity

              People

              • Assignee:
                cmccabe Colin McCabe
                Reporter:
                cmccabe Colin McCabe
              • Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: