[
https://issues.apache.org/jira/browse/HBASE-19200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245078#comment-16245078
]
Duo Zhang commented on HBASE-19200:
-----------------------------------
I'm not sure whether I fully understand the article, but seems it is not a sync
over async wrapper problem? You can see the comment of the RawAsyncTable class.
The implementation of RawAsyncTable will execute the callback directly in the
threads of the rpc framework, so it is only for experts who want to write high
performance programs. For normal users, if you are not sure whether your
callback will block or no, you should use AsyncTable, where you need to provide
a thread pool to execute your callback.
And for our sync api over async client, the callbacks are all implemented by
our own, it is what we can control. And usually it is only a simple get so I do
no think it will block anything, only the caller's thread itself, but it is
synchronous so blocking is expected, right?
Thanks.
> Let ZooKeeperRegistry depend on ZKAsyncRegistry to get data from zookeeper
> --------------------------------------------------------------------------
>
> Key: HBASE-19200
> URL: https://issues.apache.org/jira/browse/HBASE-19200
> Project: HBase
> Issue Type: Bug
> Components: Client, Zookeeper
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19200-v1.patch, HBASE-19200.patch
>
>
> So that we can move most of the zookeeper related code out of hbase-client
> module.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
