[
https://issues.apache.org/jira/browse/HDFS-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181961#comment-14181961
]
Zhe Zhang commented on HDFS-7165:
---------------------------------
[~andrew.wang] Great, hanks reviewing!
One question here: when HDFS-6252 was ported to branch-2, a customer branch-2
patch was created which excluded changes to {{TestMissingBlocksAlert}}. However
our patch depends on those changes. Usually how do we handle situations like
that? Should I manually copy the HDFS-6252 changes into
{{TestMissingBlocksAlert}}, or ask its authors to do so?
> Separate block metrics for files with replication count 1
> ---------------------------------------------------------
>
> Key: HDFS-7165
> URL: https://issues.apache.org/jira/browse/HDFS-7165
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 2.5.1
> Reporter: Andrew Wang
> Assignee: Zhe Zhang
> Fix For: 3.0.0
>
> Attachments: HDFS-7165-20141003-v1.patch,
> HDFS-7165-20141009-v1.patch, HDFS-7165-20141010-v1.patch,
> HDFS-7165-20141015-v1.patch, HDFS-7165-20141021-v1.patch,
> HDFS-7165-20141021-v2.patch
>
>
> We see a lot of escalations because someone has written teragen output with a
> replication factor of 1, a DN goes down, and a bunch of missing blocks show
> up. These are normally false positives, since teragen output is disposable,
> and generally speaking, users should understand this is true for all repl=1
> files.
> It'd be nice to be able to separate out these repl=1 missing blocks from
> missing blocks with higher replication factors..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
