Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <130263009.1255478371393.JavaMail.jira@brutus>
Date: Tue, 13 Oct 2009 16:59:31 -0700 (PDT)
From: "Hairong Kuang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-29) In Datanode, update block may fail due
 to length inconsistency
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765317#action_12765317 ] 

Hairong Kuang commented on HDFS-29:
-----------------------------------

+1. The patch looks good.

> In Datanode, update block may fail due to length inconsistency
> --------------------------------------------------------------
>
>                 Key: HDFS-29
>                 URL: https://issues.apache.org/jira/browse/HDFS-29
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>             Fix For: 0.21.0, 0.22.0
>
>         Attachments: h29_20091012.patch, h29_20091012b.patch, h29_20091012c.patch
>
>
> When a primary datanode tries to recover a block.  It calls getBlockMetaDataInfo(..) to obtains information like block length from each datanode.  Then, it calls updateBlock(..).
> The block length returned in getBlockMetaDataInfo(..) may be obtained from a unclosed local block file F.   However, in updateBlock(..), it first closes F (if F is open) and then gets the length.  These two lengths may be different.  In such case, updateBlock(..) throws an exception.

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