[
https://issues.apache.org/jira/browse/HBASE-11610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102008#comment-14102008
]
Nicolas Liochon commented on HBASE-11610:
-----------------------------------------
The perf improvement is great.
I'm not a big fan of the ThreadLocal<HTableInterface> threadLocalHTable. It's
often difficult to maintain and test.
If I understand well the issue if that the put is synchronous, and all the
threads are queueing?
Should we use something like
HConnection#processBatchCallback(List<? extends Row> list,
final TableName tableName,
ExecutorService pool,
Object[] results,
Batch.Callback<R> callback) throws IOException, InterruptedException;
instead of using HTable? HConnection is thread safe, so there is no sync needed.
(ok it's deprecated, but if it saves this kind of hack may be we need to review
our point of view).
> Enhance remote meta updates
> ---------------------------
>
> Key: HBASE-11610
> URL: https://issues.apache.org/jira/browse/HBASE-11610
> Project: HBase
> Issue Type: Sub-task
> 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)
