hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4487) The increment operation can release the rowlock before sync-ing the Hlog
Date Fri, 30 Sep 2011 19:29:45 GMT

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

stack commented on HBASE-4487:

+1 on v7 (IIUC, Ram and Lars close issue is addressed by the call to sync if edits and then
the close).  From the back and forth above, my take away is this patch makes the grouping
fatter but doesn't change current semantics -- we are as 'broke' as we were before this patch.
 I no longer think this an incompatible change.  We should release note the fatter grouping
of increments on commit. 

> The increment operation can release the rowlock before sync-ing the Hlog
> ------------------------------------------------------------------------
>                 Key: HBASE-4487
>                 URL: https://issues.apache.org/jira/browse/HBASE-4487
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>             Fix For: 0.94.0
>         Attachments: 4487-v7.txt, appendNoSync4.txt, appendNoSync5.txt, appendNoSync6.txt
> This allows for better throughput when there are hot rows.I have seen this change make
a single row update improve from 400 increments/sec/server to 4000 increments/sec/server.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message