Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <885084090.1256843159488.JavaMail.jira@brutus>
Date: Thu, 29 Oct 2009 19:05:59 +0000 (UTC)
From: "Jean-Daniel Cryans (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1939) HLog group commit
In-Reply-To: <84711109.1256689559386.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771563#action_12771563 ] 

Jean-Daniel Cryans commented on HBASE-1939:
-------------------------------------------

Raghu,

Again thanks a lot for spending some time looking at my work.

So the background is that the catalog tables like .META. must never lose any edits so, even if we sync every 100 edits for some reason, when this catalog edit comes in we want to make sure it's safely registered. 

And you are right, this is not the right place to set force as you pointed out.

> HLog group commit
> -----------------
>
>                 Key: HBASE-1939
>                 URL: https://issues.apache.org/jira/browse/HBASE-1939
>             Project: Hadoop HBase
>          Issue Type: New Feature
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.21.0
>
>         Attachments: HBASE-1939-v2.patch, HBASE-1939.patch
>
>
> Currently multiple clients writing to a RS are serialized when sync'ing their appends. Implementing group commit can help this by being aware of all the clients in that queue.

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