[
https://issues.apache.org/jira/browse/HBASE-11610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096520#comment-14096520
]
Virag Kothari commented on HBASE-11610:
---------------------------------------
bq. Can we share one HConnection instead. We can create a HTable instance when
needed. As long as we share the same HConnection, the performance should be ok.
This is what I did initially. I had one HConnection and was creating htable
instance for each put. But with more HConnections (tried with 5,10 and 15), the
write throughput on meta regionserver increased and it brought the assignment
time down by around 2 mins. The no of HConnection is configurable. By default,
it is set to 1 as for small no of regions that is enough. Also, using
threadlocal so we create only one htable instance for each thread accessing
RegionStateStore.
> Enhance remote meta updates
> ---------------------------
>
> Key: HBASE-11610
> URL: https://issues.apache.org/jira/browse/HBASE-11610
> Project: HBase
> Issue Type: Improvement
> Reporter: Jimmy Xiang
> Assignee: Virag Kothari
> Attachments: HBASE-11610.patch
>
>
> Currently, if the meta region is on a regionserver instead of the master,
> meta update is synchronized on one HTable instance. We should be able to do
> better.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
