You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Yu Li (JIRA)" <ji...@apache.org> on 2016/11/16 16:36:58 UTC

[jira] [Comment Edited] (HBASE-17114) Add an option to set special retry pause when encountering CallQueueTooBigException

    [ https://issues.apache.org/jira/browse/HBASE-17114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15670891#comment-15670891 ] 

Yu Li edited comment on HBASE-17114 at 11/16/16 4:36 PM:
---------------------------------------------------------

As it's already late night on my site, will upload the patch tomorrow.

[~eclark] [~mantonov] and [~ghelmling] especially looking forward to your thoughts on this idea gentlemen. Thanks.

And others' thoughts are also welcome (Smile).


was (Author: carp84):
As it's already late night on my site, will upload the patch tomorrow.

[~eclark] [~mantonov] and [~ghelmling] especially looking forward to your thoughts on this idea gentlemen. Thanks.

> 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
>
> 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 supply some special retry pause for CQTBE in name of {{hbase.client.pause.special}}, and by default it will be 500ms (5 times of {{hbase.client.pause}} default value)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)