[
https://issues.apache.org/jira/browse/HBASE-17008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956632#comment-15956632
]
Duo Zhang commented on HBASE-17008:
-----------------------------------
Yeah, PE tool is also a big problem.
I think for async client the PE tool will be more complicated. For sync client,
if you want to get more concurrency then just increase the thread number, but
for async client, you can get concurrency even if you only have one thread,
because you do not need to wait for the response before sending new request. So
how to design the PE tool is a challenge I think.
Thanks.
> Examples, Doc, and Helper Classes to make AsyncClient go down easy
> ------------------------------------------------------------------
>
> Key: HBASE-17008
> URL: https://issues.apache.org/jira/browse/HBASE-17008
> Project: HBase
> Issue Type: Sub-task
> Components: asyncclient, Client
> Reporter: stack
> Priority: Critical
> Fix For: 2.0.0
>
>
> The parent issue is about delivering a new, async client. The new client
> operates at a pretty low level. There will be questions on how best to use it.
> Some have come up already over in HBASE-16991. In particular, [~Apache9] and
> [~carp84] talk about the tier they have to put on top of hbase because its
> API is not user-friendly.
> This issue is about adding in the examples, docs., and helper classes we need
> to make the new async client more palatable to mortals. See HBASE-16991 for
> instance for an example of how to cache an AsyncConnection that an
> application might make use of.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
