Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 22 Nov 2013 15:46:36 +0000 (UTC)
From: "Himanshu Vashishtha (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12680131.1384936000711.15168.1385135196922@arcas>
In-Reply-To: <JIRA.12680131.1384936000711@arcas>
References: <JIRA.12680131.1384936000711@arcas>
Subject: [jira] [Commented] (HBASE-10010) eliminate the put latency spike on
 the new log file beginning
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Himanshu Vashishtha commented on HBASE-10010:
---------------------------------------------

I think post 0.94.x, we only need to sync the new writer outside of lock because we write a header on init(). No empty HLog entry.

> eliminate the put latency spike on the new log file beginning
> -------------------------------------------------------------
>
>                 Key: HBASE-10010
>                 URL: https://issues.apache.org/jira/browse/HBASE-10010
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 0.94.13
>            Reporter: Liang Xie
>            Assignee: Liang Xie
>         Attachments: HBase-10010-0.94-v2.txt, HBase-10010-0.94.txt, HBase-10010-trunk.txt
>
>
> In deed, the original finding came from fb, see HBASE-6813 for detailed discussion.
> Through this improvement doesn't expect obvious gain on 95th or 99th latency, it still could make the response time more stable to me.


--
This message was sent by Atlassian JIRA
(v6.1#6144)