[
https://issues.apache.org/jira/browse/HDFS-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425175#comment-13425175
]
Colin Patrick McCabe commented on HDFS-2554:
--------------------------------------------
bq. MissingBlocksR1: r=1, n=0, c=0:
Perhaps "MissingSingleReplBlocks"?
bq. MissingBlocksRN
Perhaps "MissingMultiReplBlocks"?
bq. CorruptBlocksRN: r>1, n=0, c>0:
Perhaps "CorruptMultiReplBlocks"?
bq. CorruptBlocksR1: r=1, n=0, c=1:
Perhaps "CorruptSingleReplBlocks"?
I think SingleRepl / MultiRepl are the most concise terms I can think of for
blocks with r=1 and r>1, respectively. It might be nice if we had standardized
terminology like "scratch" for blocks with r=1. (Does anyone know if we have a
special term for these blocks?)
Also, should we split CorruptBlocksRN into a "CriticallyCorruptMultiReplBlocks"
which is r>1, n=0, c=r, and a PartiallyCorruptMultiReplBlocks which is r>1,
n=0, r>c>0? It seems like the distinction between "some replicas are
corrupted" and "all replicas are corrupted" is an important one from a system
administrator's perspective.
> Add separate metrics for missing blocks with desired replication level 1
> ------------------------------------------------------------------------
>
> Key: HDFS-2554
> URL: https://issues.apache.org/jira/browse/HDFS-2554
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Affects Versions: 2.0.0-alpha
> Reporter: Todd Lipcon
> Assignee: Andy Isaacson
> Priority: Minor
>
> Some users use replication level set to 1 for datasets which are unimportant
> and can be lost with no worry (eg the output of terasort tests). But other
> data on the cluster is important and should not be lost. It would be useful
> to separate the metric for missing blocks by the desired replication level of
> those blocks, so that one could ignore missing blocks at repl 1 while still
> alerting on missing blocks with higher desired replication.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
