[
https://issues.apache.org/jira/browse/HBASE-17114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708248#comment-15708248
]
Anoop Sam John commented on HBASE-17114:
----------------------------------------
bq.Set this property to a higher value than hbase.client.pause...
You want to add some check here and make sure it is not wrongly configured?
When low, ignore and log WARN and go with client pause?
RpcRetryingCallerImpl
-expectedSleep = callable.sleep(pause, tries);
+expectedSleep = callable.sleep(pauseBase, tries + 1);
Why this tries + 1 change?
> Add an option to set special retry pause when encountering
> CallQueueTooBigException
> -----------------------------------------------------------------------------------
>
> Key: HBASE-17114
> URL: https://issues.apache.org/jira/browse/HBASE-17114
> Project: HBase
> Issue Type: Bug
> Reporter: Yu Li
> Assignee: Yu Li
> Attachments: HBASE-17114.patch, HBASE-17114.v2.patch,
> HBASE-17114.v3.patch, HBASE-17114.v3.patch, HBASE-17114.v4.patch
>
>
> As titled, after HBASE-15146 we will throw {{CallQueueTooBigException}}
> instead of dead-wait. This is good for performance for most cases but might
> cause a side-effect that if too many clients connect to the busy RS, that the
> retry requests may come over and over again and RS never got the chance for
> recovering, and the issue will become especially critical when the target
> region is META.
> So here in this JIRA we propose to add a new property in name of
> {{hbase.client.pause.cqtbe}} to make it possible to set a special-longer
> pause for CallQueueTooBigException, and by default it will use the setting of
> {{hbase.client.pause}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
