Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <8137175.1091289367374529.JavaMail.jira@thor>
Date: Wed, 10 Nov 2010 00:36:14 -0500 (EST)
From: "sam rash (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1122) client block verification may result
 in blocks in DataBlockScanner prematurely
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

sam rash commented on HDFS-1122:
--------------------------------

it looks it does exist--has the same problem that if a BlockSender sends all the data for an open block, it gets added to the block scanner.

oddly, in retrospect, this doesn't produce an error since the DataBlockScanner itself is just another concurrent reader
(it does produce the warnings of adding a block more than once)


> client block verification may result in blocks in DataBlockScanner prematurely
> ------------------------------------------------------------------------------
>
>                 Key: HDFS-1122
>                 URL: https://issues.apache.org/jira/browse/HDFS-1122
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: 0.20-append
>            Reporter: sam rash
>            Assignee: sam rash
>         Attachments: hdfs-1122-for-0.20.txt
>
>
> found that when the DN uses client verification of a block that is open for writing, it will add it to the DataBlockScanner prematurely. 

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