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-3718) Unify retry logic of SyncClientPool in ConfigNode

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

Yongzao Dan reassigned IOTDB-3718:
----------------------------------

    Assignee: 任宇华  (was: Yongzao Dan)

> Unify retry logic of SyncClientPool in ConfigNode
> -------------------------------------------------
>
>                 Key: IOTDB-3718
>                 URL: https://issues.apache.org/jira/browse/IOTDB-3718
>             Project: Apache IoTDB
>          Issue Type: Improvement
>            Reporter: Yongzao Dan
>            Assignee: 任宇华
>            Priority: Minor
>             Fix For: 0.14.0
>
>
> Currently, almost all interfaces in ConfigNode's SyncClientPool use a combination of a for loop and a try-catch statement to perform their own retry logic. We need a unified approach to gracefully retry RPC requests in SyncClientPool.



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