hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5027) Block report processing should compare gneration stamp
Date Sat, 17 Jan 2009 01:41:59 GMT

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

Tsz Wo (Nicholas), SZE commented on HADOOP-5027:
------------------------------------------------

As suggested by Rob, if the reported block is ignored in NN, the data available guarantee
will not be as good as before.   Specifically, the existing data stored in the last block
being reopened may not be replicated.  I think we need to work on the design first.

> 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