You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@iotdb.apache.org by "Yongzao Dan (Jira)" <ji...@apache.org> on 2022/07/04 06:52:00 UTC

[jira] [Assigned] (IOTDB-3720) Unify retry logic of AsyncClientPool in ConfigNode

     [ https://issues.apache.org/jira/browse/IOTDB-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yongzao Dan reassigned IOTDB-3720:
----------------------------------

    Assignee: 任宇华  (was: Yongzao Dan)

> Unify retry logic of AsyncClientPool in ConfigNode
> --------------------------------------------------
>
>                 Key: IOTDB-3720
>                 URL: https://issues.apache.org/jira/browse/IOTDB-3720
>             Project: Apache IoTDB
>          Issue Type: Improvement
>            Reporter: Yongzao Dan
>            Assignee: 任宇华
>            Priority: Minor
>             Fix For: 0.14.0
>
>
> Currently, none of ConfigNode's AsyncClientPool interfaces have retry logic except for createRegions. The createRegions interface uses CountDownLatch and BitSet to construct the retry logic. Although this algorithm can fulfill the requirements, it is difficult to reuse and causes the code inside the interface to be too long. We need a uniform way to elegantly retry RPC requests in AsyncClientPool.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)