Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Wed, 15 Jan 2014 09:31:20 +0000 (UTC)
From: "Feng Honghua (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12688974.1389778241526.4905.1389778280325@arcas>
In-Reply-To: <JIRA.12688974.1389778241526@arcas>
References: <JIRA.12688974.1389778241526@arcas>
Subject: [jira] [Created] (HBASE-10344) Improve writer performance by
 ignoring sync to hdfs when an asyncer's writes have been synced by other
 asyncer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Feng Honghua created HBASE-10344:
------------------------------------

             Summary: Improve writer performance by ignoring sync to hdfs when an asyncer's writes have been synced by other asyncer
                 Key: HBASE-10344
                 URL: https://issues.apache.org/jira/browse/HBASE-10344
             Project: HBase
          Issue Type: Improvement
            Reporter: Feng Honghua
            Assignee: Feng Honghua


By fixing [HBASE-10329|https://issues.apache.org/jira/browse/HBASE-10329], we know it's possible an asyncer's writes have been synced by other asyncer before it starts to do the sync. We distinguish this case and handle accordingly when the writer is null.
But when writer is not null(most of the time), we also can check and ignore the sync if asyncer's writes have been synced by other asyncer before doing sync. Since sync is a quite heavy operation(together with following notifying notifier thread and log roll check) we can have some performance gain by ignoring it for such case.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)