hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5027) Block report processing should compare gneration stamp
Date Fri, 16 Jan 2009 01:52:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664362#action_12664362
] 

Raghu Angadi commented on HADOOP-5027:
--------------------------------------

> What do you mean "done by NN"?

I meant all the changes go through NN. 

Note that a patch was attached but the fix is not described anywhere in the jira. Finally
I read the patch.

Looking at the patch now, it looks like you do (correctly) consider it  an error if reported
gs is larger than stored gs.From the description of the jira, I thought NN might consider
new reported gs as the correct one.  Btw, the patch just ignores such a block with a warning...,
should it also delete such a block?



> Block report processing should compare gneration stamp
> ------------------------------------------------------
>
>                 Key: HADOOP-5027
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5027
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: Tsz Wo (Nicholas), SZE
>             Fix For: 0.19.1
>
>         Attachments: 5027_20090114.patch
>
>
> If a reported block has a different generation stamp then the one stored in the NameNode,
the reported block will be considered as invalid.  This is incorrect since blocks with larger
generation stamp are valid.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message