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

Newly added NN storage directory won't get initialized and cause space exhaustion

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.7.3
    • Fix Version/s: 2.9.0, 2.7.4, 3.0.0-alpha4, 2.8.2
    • Component/s: None
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      When an empty namenode storage directory is detected on normal NN startup, it may not be fully initialized. The new directory is still part of "in-service" NNStrage and when a checkpoint image is uploaded, a copy will also be written there. However, the retention manager won't be able to purge old files since it is lacking a VERSION file. This causes fsimages to pile up in the directory. With a big name space, the disk will be filled in the order of days or weeks.

        Attachments

        1. HDFS-11714.trunk.patch
          7 kB
          Kihwal Lee
        2. HDFS-11714.v2.branch-2.patch
          6 kB
          Kihwal Lee
        3. HDFS-11714.v2.trunk.patch
          6 kB
          Kihwal Lee
        4. HDFS-11714.v3.branch-2.patch
          6 kB
          Kihwal Lee
        5. HDFS-11714.v3.trunk.patch
          6 kB
          Kihwal Lee

          Activity

            People

            • Assignee:
              kihwal Kihwal Lee
              Reporter:
              kihwal Kihwal Lee
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: