You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Chao Shi (JIRA)" <ji...@apache.org> on 2014/01/10 09:15:13 UTC
[jira] [Resolved] (HBASE-10305) Batch update performance drops as
the number of regions grows
[ https://issues.apache.org/jira/browse/HBASE-10305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chao Shi resolved HBASE-10305.
------------------------------
Resolution: Not A Problem
We're running 0.94.10. ASYNC_WAL does work for me. Thanks Lars. Close this issue.
> Batch update performance drops as the number of regions grows
> -------------------------------------------------------------
>
> Key: HBASE-10305
> URL: https://issues.apache.org/jira/browse/HBASE-10305
> Project: HBase
> Issue Type: Bug
> Components: Performance
> Reporter: Chao Shi
>
> In our use case, we use a small number (~5) of proxy programs that read from a queue and batch update to HBase. Our program is multi-threaded and HBase client will batch mutations to each RS.
> We found we're getting lower TPS when there are more regions. I think the reason is RS syncs HLog for each region. Suppose there is a single region, the batch update will only touch one region and therefore syncs HLog once. And suppose there are 10 regions per server, in RS#multi() it have to process update for each individual region and sync HLog 10 times.
> Please note that in our scenario, batched mutations usually are independent with each other and need to touch a various number of regions.
> We are using the 0.94 series, but I think the trunk should have the same problem after a quick look into the code.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)