Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sat, 4 Jun 2011 05:06:47 +0000 (UTC)
From: "John George (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <2130177984.68077.1307164007553.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1321652620.68068.1307162687352.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-2034) reading from currently being written
 block does not work
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John George updated HDFS-2034:
------------------------------

    Attachment: HDFS-2034.patch

Taking clues from what Daryn, Nicholas and Todd were suggesting/finding in HDFS-1907.

This patch addresses the case where length could go negative under certain circumstances.

> reading from currently being written block does not work 
> ---------------------------------------------------------
>
>                 Key: HDFS-2034
>                 URL: https://issues.apache.org/jira/browse/HDFS-2034
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: John George
>            Assignee: John George
>         Attachments: HDFS-2034.patch
>
>
> This came up during HDFS-1907. Posting an example that Todd posted in HDFS-1907 that brought out this issue.
> {quote}
> Here's an example sequence to describe what I mean:
> 1. open file, write one and a half blocks
> 2. call hflush
> 3. another reader asks for the first byte of the second block
> {quote}
> In this case since offset is greater than the completed block length, the math in getBlockRange() of DFSInputStreamer.java will set "length" to negative.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira