[
https://issues.apache.org/jira/browse/HADOOP-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668136#action_12668136
]
Konstantin Shvachko commented on HADOOP-5027:
---------------------------------------------
I see at least 6 currently open issues, which seem to be different, but
actually being about the same problem.
HADOOP-4663
HADOOP-5027 (states 2 problems)
HADOOP-5133
HADOOP-4379
HADOOP-4692
The problem is *consistent handling incomplete blocks* or another way to say it
*consistent handling block replication*.
Trying to fix the issues separately is imHo a mistake.
I am advocating to step back, get a general view, design a proposal, make sure
it works and then fix issues.
Gradually changing the code may destabilize the main hdfs functionality, which
is not related to synchs or appends.
Although I am not personally in favor of gradual changes in this particular
case, you can still go this path
e.g. in a separate branch with a potential to merging it back to trunk when it
is done.
I think people should have a choice to sacrifice certain functionality in favor
of reliability if they want to.
Gradual changes close this alternative.
I'll link this comment from the related issues.
> 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.
