[ https://issues.apache.org/jira/browse/HDFS-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166589#comment-14166589 ]
Hadoop QA commented on HDFS-7165: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12674116/HDFS-7165-20141009-v1.patch against trunk revision d3afd73. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:red}-1 release audit{color}. The applied patch generated 1 release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.TestMissingBlocksAlert org.apache.hadoop.hdfs.server.namenode.ha.TestDNFencing org.apache.hadoop.hdfs.server.namenode.ha.TestDNFencingWithReplication {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/8387//testReport/ Release audit warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/8387//artifact/patchprocess/patchReleaseAuditProblems.txt Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8387//console This message is automatically generated. > 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 > Reporter: Andrew Wang > Assignee: Zhe Zhang > Attachments: HDFS-7165-20141003-v1.patch, HDFS-7165-20141009-v1.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)