You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2019/06/03 09:51:01 UTC
[jira] [Updated] (HBASE-21512) Reimplement sync client based on
async client
[ https://issues.apache.org/jira/browse/HBASE-21512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang updated HBASE-21512:
------------------------------
Summary: Reimplement sync client based on async client (was: Introduce an AsyncClusterConnection and replace the usage of ClusterConnection)
> Reimplement sync client based on async client
> ---------------------------------------------
>
> 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)