Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 12 Sep 2013 03:50:52 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12668199.1378957844669.120921.1378957852352@arcas>
In-Reply-To: <JIRA.12668199.1378957844669@arcas>
References: <JIRA.12668199.1378957844669@arcas>
Subject: [jira] [Created] (HDFS-5189) Rename the "CorruptBlocks" metric to
 "CorruptReplicas"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Harsh J created HDFS-5189:
-----------------------------

             Summary: Rename the "CorruptBlocks" metric to "CorruptReplicas"
                 Key: HDFS-5189
                 URL: https://issues.apache.org/jira/browse/HDFS-5189
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: namenode
    Affects Versions: 2.1.0-beta
            Reporter: Harsh J
            Assignee: Harsh J
            Priority: Minor


The NameNode increments a "CorruptBlocks" metric even if only one of the block's
replicas is reported corrupt (genuine checksum fail, or even if a
replica has a bad genstamp). In cases where this is incremented, fsck
still reports a healthy state.

This is confusing to users and causes false alarm as they feel this is to be monitored (instead of MissingBlocks). The metric is truly trying to report only corrupt replicas, not whole blocks, and ought to be renamed.

FWIW, the "dfsadmin -report" reports a proper string of "Blocks with corrupt replicas:" when printing this count.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira