You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "Sean Li (JIRA)" <ji...@apache.org> on 2018/06/07 03:36:00 UTC
[jira] [Updated] (SCB-651) QPS rate limit bug
[ https://issues.apache.org/jira/browse/SCB-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Li updated SCB-651:
------------------------
Description:
When setting _servicecomb.flowcontrol.Provider.qps.limit.[ServiceName]_, the actual number of requests allowed per second is always 1 less than the limit value.
For example, if I set _flowcontrol.Provider.qps.limit._
_business-service-consumer_ as 1, I'll get no successful request at the very beginning, although I would expect 1 successful request instead of none. Similarly, if I set _flowcontrol.Provider.qps.limit._
_business-service-consumer_ as 2, I'll get 1 successful request instead of 2.
However, if I pause before sending requests, for example add _Thread.sleep(100)_ before invoking the first request, the number of requests allowed per second will be correct this time. (i.e. 1 successful request when limit value is 1, 2 successful requests when limit value is 2, etc.)
was:When setting servicecomb.flowcontrol.Provider.qps.limit.[ServiceName], the actual number of requests allowed per second is always 1 less than the limit value.
> QPS rate limit bug
> ------------------
>
> Key: SCB-651
> URL: https://issues.apache.org/jira/browse/SCB-651
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
> Affects Versions: java-chassis-1.0.0-m1
> Reporter: Sean Li
> Priority: Major
>
> When setting _servicecomb.flowcontrol.Provider.qps.limit.[ServiceName]_, the actual number of requests allowed per second is always 1 less than the limit value.
>
> For example, if I set _flowcontrol.Provider.qps.limit._
> _business-service-consumer_ as 1, I'll get no successful request at the very beginning, although I would expect 1 successful request instead of none. Similarly, if I set _flowcontrol.Provider.qps.limit._
> _business-service-consumer_ as 2, I'll get 1 successful request instead of 2.
>
> However, if I pause before sending requests, for example add _Thread.sleep(100)_ before invoking the first request, the number of requests allowed per second will be correct this time. (i.e. 1 successful request when limit value is 1, 2 successful requests when limit value is 2, etc.)
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)