Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 9913 invoked from network); 2 Nov 2010 19:08:19 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Nov 2010 19:08:19 -0000 Received: (qmail 63436 invoked by uid 500); 2 Nov 2010 19:08:51 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 63403 invoked by uid 500); 2 Nov 2010 19:08:51 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 63395 invoked by uid 99); 2 Nov 2010 19:08:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 19:08:51 +0000 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.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 19:08:50 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA2J8U0N002461 for ; Tue, 2 Nov 2010 19:08:30 GMT Message-ID: <7987708.201971288724910449.JavaMail.jira@thor> Date: Tue, 2 Nov 2010 15:08:30 -0400 (EDT) From: "stack (JIRA)" To: hdfs-issues@hadoop.apache.org Subject: [jira] Commented: (HDFS-895) Allow hflush/sync to occur in parallel with new writes to the file In-Reply-To: <1434004888.217191263401454505.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927552#action_12927552 ] stack commented on HDFS-895: ---------------------------- @Hairong He's out for a few days (wandering temples in foreign lands) > Allow hflush/sync to occur in parallel with new writes to the file > ------------------------------------------------------------------ > > Key: HDFS-895 > URL: https://issues.apache.org/jira/browse/HDFS-895 > Project: Hadoop HDFS > Issue Type: Improvement > Components: hdfs client > Affects Versions: 0.22.0 > Reporter: dhruba borthakur > Assignee: Todd Lipcon > Fix For: 0.22.0 > > Attachments: hdfs-895-0.20-append.txt, hdfs-895-20.txt, hdfs-895-review.txt, hdfs-895-trunk.txt, hdfs-895.txt, hdfs-895.txt > > > In the current trunk, the HDFS client methods writeChunk() and hflush./sync are syncronized. This means that if a hflush/sync is in progress, an applicationn cannot write data to the HDFS client buffer. This reduces the write throughput of the transaction log in HBase. > The hflush/sync should allow new writes to happen to the HDFS client even when a hflush/sync is in progress. It can record the seqno of the message for which it should receice the ack, indicate to the DataStream thread to star flushing those messages, exit the synchronized section and just wai for that ack to arrive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.