[
https://issues.apache.org/jira/browse/HDFS-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572203#comment-14572203
]
J.Andreina commented on HDFS-5189:
----------------------------------
I would like to work on this issue.
[~qwertymaniac] and [[email protected]] please reassign to you if you are
working on this.
> 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
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
