[
https://issues.apache.org/jira/browse/HDFS-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169131#comment-13169131
]
Hadoop QA commented on HDFS-2673:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12507227/HDFS-2673.patch
against trunk revision .
+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 new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1712//console
This message is automatically generated.
> While Namenode processing the blocksBeingWrittenReport, it will log incorrect
> number blocks count
> -------------------------------------------------------------------------------------------------
>
> Key: HDFS-2673
> URL: https://issues.apache.org/jira/browse/HDFS-2673
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 1.0.0
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Priority: Trivial
> Attachments: HDFS-2673.patch
>
>
> In NameNode#blocksBeingWrittenReport
> we have the following stateChangeLog
> {code}
> stateChangeLog.info("*BLOCK* NameNode.blocksBeingWrittenReport: "
> +"from "+nodeReg.getName()+" "+blocks.length +" blocks");
> {code}
> here blocks is long array. Every consecutive 3 elements represents a block (
> length, blockid, genstamp).
> So, here in log message, blocks.length should be blocks.length/3.
>
--
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
