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

Rename of Being Written Files

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 3.0.0-alpha1
    • Fix Version/s: None
    • Component/s: hdfs-client, namenode
    • Labels:
      None

      Description

      When a being written file or it's ancestor directories is renamed, the path in the file lease is also renamed. Then the writer of the file usually will fail since the file path in the writer is not updated.

      Moreover, I think there is a bug as follow:

      1. Client writes 0's to F_0="/foo/file" and writes 1's to F_1="/bar/file" at the same time.
      2. Rename /bar to /baz
      3. Rename /foo to /bar

      Then, writing to F_0 will fail since /foo/file does not exist anymore but writing to F_1 may succeed since /bar/file exits as a different file. In such case, the content of /bar/file could be partly 0's and partly 1's.

        Attachments

        1. HDFS-4258.patch
          84 kB
          Brandon Li
        2. HDFS-4258.patch
          89 kB
          Brandon Li
        3. HDFS-4258.patch
          103 kB
          Brandon Li
        4. HDFS-4258.patch
          103 kB
          Brandon Li

          Issue Links

            Activity

              People

              • Assignee:
                brandonli Brandon Li
                Reporter:
                szetszwo Tsz-wo Sze
              • Votes:
                0 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: