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

Rolling restart can create inconsistency between blockMap and corrupt replicas map

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.6.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      After a NN rolling restart several HDFS files started showing block problems. Running FSCK for one of the files or for the directory that contained it would complete with a FAILED message but without any details of the failure.

      The NameNode log showed the following:

      2017-10-10 16:58:32,147 INFO org.apache.hadoop.hdfs.server.namenode.NameNode: FSCK started by hdfs (auth:KERBEROS_SSL) from /10.92.128.4 for path /user/prod/data/file_20171010092201.csv at Tue Oct 10 16:58:32 PDT 2017
      2017-10-10 16:58:32,147 WARN org.apache.hadoop.hdfs.server.blockmanagement.BlockManager: Inconsistent number of corrupt replicas for blk_1941920008_1133195379 blockMap has 1 but corrupt replicas map has 2
      2017-10-10 16:58:32,147 WARN org.apache.hadoop.hdfs.server.namenode.NameNode: Fsck on path '/user/prod/data/file_20171010092201.csv' FAILED
      java.lang.ArrayIndexOutOfBoundsException
      

      After triggering a full block report for all the DNs the problem went away.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                asdaraujo Andre Araujo
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: