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

Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/11 23:33:00 UTC

[jira] [Resolved] (HBASE-2445) Clean up client retry policies

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

Andrew Kyle Purtell resolved HBASE-2445.
----------------------------------------
    Resolution: Incomplete

> Clean up client retry policies
> ------------------------------
>
>                 Key: HBASE-2445
>                 URL: https://issues.apache.org/jira/browse/HBASE-2445
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>            Reporter: Todd Lipcon
>            Priority: Critical
>              Labels: moved_from_0_20_5
>
> Right now almost all retry behavior is governed by a single parameter that determines the number of retries. In a few places, there are also conf for the number of millis to sleep between retries. This isn't quite flexible enough. If we can refactor some of the retry logic into a RetryPolicy class, we could introduce exponential backoff where appropriate, clean up some of the config, etc



--
This message was sent by Atlassian Jira
(v8.20.7#820007)