[
https://issues.apache.org/jira/browse/HDFS-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley updated HDFS-2673:
-----------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
Target Version/s: 1.0.0 (was: 1.1.0)
Status: Resolved (was: Patch Available)
Agree. +1 for code review. Committed to 1.0.0 and branch-1.
Thanks, Uma!
Please check if similar fix is needed in 0.23 and trunk.
> 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
> Fix For: 1.0.0
>
> 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
