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/18 13:57:02 UTC

[jira] [Assigned] (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 reassigned HBASE-21512:
---------------------------------

    Assignee: Duo Zhang

> Reimplement sync client based on async client
> ---------------------------------------------
>
>                 Key: HBASE-21512
>                 URL: https://issues.apache.org/jira/browse/HBASE-21512
>             Project: HBase
>          Issue Type: Umbrella
>          Components: asyncclient, Client
>            Reporter: Duo Zhang
>            Assignee: 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)