[
https://issues.apache.org/jira/browse/HBASE-21512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717147#comment-16717147
]
Duo Zhang commented on HBASE-21512:
-----------------------------------
And there are also lots of references to the ClusterConnection, so maybe a
better way is to purge as many references to ClusterConnection as possible, and
then also reimplement the ClusterConnection based on AsyncConnection. The
purging of references is useful as we can remove lots of methods in
ClusterConnection, if they are only referenced by the client implementation.
> Introduce an AsyncClusterConnection and replace the usage of ClusterConnection
> ------------------------------------------------------------------------------
>
> Key: HBASE-21512
> URL: https://issues.apache.org/jira/browse/HBASE-21512
> Project: HBase
> Issue Type: Umbrella
> Reporter: Duo Zhang
> Priority: Major
> Fix For: 3.0.0
>
>
> At least for the RSProcedureDispatcher, with CompletableFuture we do not need
> to set a delay and use a thread pool any more, which could reduce the
> resource usage and also the latency.
> Once this is done, I think we can remove the ClusterConnection completely,
> and start to rewrite the old sync client based on the async client, which
> could reduce the code base a lot for our client.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
