[
https://issues.apache.org/jira/browse/HBASE-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13136687#comment-13136687
]
dhruba borthakur commented on HBASE-4528:
-----------------------------------------
TestDistibutedLogSplitting fails without this patch too. The other tests pass
in my setup. I am rerunnign test again.
Ted: the TimeRangeTracker seems to me to be a heuristic, it can for sure tell
if the key *does not* belong in the file. The fact that we are not rolling back
timeRangeTracker for a memstoreRollback means that there might be a case where
we will look for this key in this store file although the key does not belong
to this store file, but that should be ok.
> The put operation can release the rowlock before sync-ing the Hlog
> ------------------------------------------------------------------
>
> Key: HBASE-4528
> URL: https://issues.apache.org/jira/browse/HBASE-4528
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.94.0
>
> Attachments: HBASE-4528-Trunk-FINAL.patch, appendNoSync5.txt,
> appendNoSyncPut1.txt, appendNoSyncPut2.txt, appendNoSyncPut3.txt,
> appendNoSyncPut4.txt, appendNoSyncPut5.txt, appendNoSyncPut6.txt,
> appendNoSyncPut7.txt, appendNoSyncPut8.txt
>
>
> This allows for better throughput when there are hot rows. A single row
> update improves from 100 puts/sec/server to 5000 puts/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
