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

NameNode should optionally exit if it detects FsImage corruption

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.1.0, 2.10.0, 2.9.1, 3.0.3
    • namenode
    • None
    • Reviewed

    Description

      The NameNode should optionally exit after writing an FsImage if it detects the following kinds of corruptions:

      1. INodeReference pointing to non-existent INode
      2. Duplicate entries in snapshot deleted diff list.

      Attachments

        1. HDFS-13314.01.patch
          15 kB
          Arpit Agarwal
        2. HDFS-13314.02.patch
          14 kB
          Arpit Agarwal
        3. HDFS-13314.03.patch
          15 kB
          Arpit Agarwal
        4. HDFS-13314.04.patch
          14 kB
          Arpit Agarwal
        5. HDFS-13314.05.patch
          12 kB
          Arpit Agarwal

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. HDFS-13101 Yet another fsimage corruption related to snapshot

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. HDFS-13813 Exit NameNode if dangling child inode is detected when saving FsImage

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              arp Arpit Agarwal
              arp Arpit Agarwal
              Votes:
              0 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: