hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2673) While Namenode processing the blocksBeingWrittenReport, it will log incorrect number blocks count
Date Fri, 16 Dec 2011 09:04:30 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170841#comment-13170841
] 

Uma Maheswara Rao G commented on HDFS-2673:
-------------------------------------------

Thanks a lot, Matt for the reviews,
 In trunk, there wont be separate blockBeingWritten report. There is one place where we are
serialining blocks as long array is blockReport. Here we already handled it.

{code}
 + "from " + nodeReg.getName() + " " + blist.getNumberOfBlocks()
{code}

Thanks
Uma
                
> 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

        

Mime
View raw message