[ https://issues.apache.org/jira/browse/HADOOP-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707588#action_12707588 ]
Hadoop QA commented on HADOOP-5780: ----------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12407573/HADOOP-5780.patch against trunk revision 772960. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no tests are needed for this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 Eclipse classpath. The patch retains Eclipse classpath integrity. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. -1 contrib tests. The patch failed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/309/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/309/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/309/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/309/console This message is automatically generated. > Fix slightly confusing log from "-metaSave" on NameNode > ------------------------------------------------------- > > Key: HADOOP-5780 > URL: https://issues.apache.org/jira/browse/HADOOP-5780 > Project: Hadoop Core > Issue Type: Bug > Components: dfs > Affects Versions: 0.20.0 > Reporter: Raghu Angadi > Assignee: Raghu Angadi > Priority: Minor > Fix For: 0.21.0 > > Attachments: HADOOP-5780.patch, HADOOP-5780.patch, HADOOP-5780.patch > > > After HADOOP-4103, "-metaSave" on NameNode prints "MISSING" in the line for a > block that does not have any good replicas left. > e.g. : {noformat} > Metasave: Blocks waiting for replication: 1 > blk_6735500019364591152_0 (replicas: l: 0 d: 0 c: 2 e: 0 MISSING) > 74.6.132.200:50010 : 192.168.0.107:50010 : > {noformat} > "0 MISSING" in the log might imply to the user that there is no missing > block, though it implies "e(xcess replicas) : 0". > We should fix that. Also as part of this I would like to indicate which > datanodes are decommissioned or contain the corrupt replicas. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.