Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 19726 invoked from network); 23 Jan 2009 10:27:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Jan 2009 10:27:26 -0000 Received: (qmail 65972 invoked by uid 500); 23 Jan 2009 10:27:24 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 65719 invoked by uid 500); 23 Jan 2009 10:27:23 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 65693 invoked by uid 99); 23 Jan 2009 10:27:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jan 2009 02:27:23 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jan 2009 10:27:22 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 35284234C4AC for ; Fri, 23 Jan 2009 02:27:02 -0800 (PST) Message-ID: <1761644734.1232706422216.JavaMail.jira@brutus> Date: Fri, 23 Jan 2009 02:27:02 -0800 (PST) From: "dhruba borthakur (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Updated: (HADOOP-4379) In HDFS, sync() not yet guarantees data available to the new readers In-Reply-To: <901820613.1223514224222.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HADOOP-4379: ------------------------------------- Attachment: fsyncConcurrentReaders3.patch This patch implements the following (as specified in the design doc for Appends, HADOOP-1700): A reader checks to see if the file is being written to by another writer. if so, it fetches the size of the last block from the primary datanode. This does not have any performance impact for non-concurrent readers not does it have any impact on sync(). > In HDFS, sync() not yet guarantees data available to the new readers > -------------------------------------------------------------------- > > Key: HADOOP-4379 > URL: https://issues.apache.org/jira/browse/HADOOP-4379 > Project: Hadoop Core > Issue Type: New Feature > Components: dfs > Reporter: Tsz Wo (Nicholas), SZE > Assignee: dhruba borthakur > Fix For: 0.19.1 > > Attachments: 4379_20081010TC3.java, fsyncConcurrentReaders.txt, fsyncConcurrentReaders3.patch, Reader.java, Writer.java > > > In the append design doc (https://issues.apache.org/jira/secure/attachment/12370562/Appends.doc), it says > * A reader is guaranteed to be able to read data that was 'flushed' before the reader opened the file > However, this feature is not yet implemented. Note that the operation 'flushed' is now called "sync". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.