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

Mismatch in displaying the "MissingBlock" count in fsck and in other metric reports

    XMLWordPrintableJSON

    Details

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

      Description

      Number of DN = 2
      Step 1: Write a file with replication factor - 3 .
      Step 2: Corrupt a replica in DN1
      Step 3: DN2 is down.

      Missing Block count in report is as follows
      Fsck report : 0
      Jmx, "dfsadmin -report" , UI, logs : 1

      In fsck , only block whose replicas are all missed and not been corrupted are counted

      if (totalReplicasPerBlock == 0 && !isCorrupt) {
              // If the block is corrupted, it means all its available replicas are
              // corrupted. We don't mark it as missing given these available replicas
              // might still be accessible as the block might be incorrectly marked as
              // corrupted by client machines.
      

      While in other reports even if all the replicas are corrupted , block is been considered as missed.

      Please provide your thoughts : can we make missing block count consistent across all the reports same as implemented for fsck?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                andreina J.Andreina
                Reporter:
                andreina J.Andreina
              • Votes:
                6 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: