hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5192) Block reciever should not remove a finalized block when block replication fails
Date Tue, 10 Feb 2009 21:23:59 GMT

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

Hairong Kuang commented on HADOOP-5192:

The essence of the problem with HADOOP-4702 is that it gives a chance for a thread to delete
a block which is not created by itself. BlockAlreadyExistedException prevents this from happening.
With the validity check, it allows the writer to remove a block that it is writing to if the
block is not finalized when error occurs. I agree what you proposed is a good practice, but
cleanupBlock does not aim at a multi-threads situation.

> 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
>             Fix For: 0.18.4
>         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