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-5192) Block reciever should not remove a finalized block when block replication fails
Date Wed, 11 Feb 2009 22:29:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672811#action_12672811

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

> In our case, if a block is invalid, it remains invalid forever. So we may not need a

Every block becomes valid once.. i.e. it is invalid before that instant. The above statement
is not correct I think.

You are right.  Hairong also pointed this out.  I think we could check whether the block is
valid inside unfinalizeBlock(..).

> Block reciever should not remove a finalized block when block replication fails
> -------------------------------------------------------------------------------
>                 Key: HADOOP-5192
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5192
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.18.3
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>            Priority: Blocker
>             Fix For: 0.18.4, 0.19.1
>         Attachments: blockCleanup.patch, blockRemove.patch
> HADOOP-4702 makes block receivers to remove the received block in case of a block replication
failure. But the block should not be removed if the cause of the failure is that the block
to be received already exists. The key is that a block receiver should allow to remove only
partial blocks in case of block replication failures. 

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

View raw message