[
https://issues.apache.org/jira/browse/HBASE-27798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715939#comment-17715939
]
Ray Mattingly commented on HBASE-27798:
---------------------------------------
The current retry backoff has a few inputs & steps. For example, we use [the
{{pause}} and {{pauseForServerOverloaded}} durations in
{{RpcRetryingCallerImpl}}|https://github.com/apache/hbase/blob/branch-2/hbase-client/src/main/java/org/apache/hadoop/hbase/client/RpcRetryingCallerImpl.java#L59-L60]
to determine a pauseBase millis, and then multiply it by the relevant
{{RETRY_BACKOFF}} item.
I'm wondering how we should incorporate the {{waitInterval}} into this existing
system; I see a few options:
# We could consider waitInterval an addition to the pauseBase
# We could consider waitInterval an addition to the product of pauseBase *
retryBackoff
# We could consider waitInterval, if present, to be a replacement for the
pauseBase
# We could consider waitInterval, if present, to be a replacement for the
produce of pauseBase * retryBackoff
[~bbeaudreault] do you have any thoughts/preference here?
> Client side should back off based on wait interval in RpcThrottlingException
> ----------------------------------------------------------------------------
>
> Key: HBASE-27798
> URL: https://issues.apache.org/jira/browse/HBASE-27798
> Project: HBase
> Issue Type: Improvement
> Reporter: Bryan Beaudreault
> Assignee: Ray Mattingly
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
