QPS is blocked when it reaches the threshold??

[yugj]

环境说明

应用网关：zuul 单机

sentinel 版本：1.6.3

zuul adaptor 版本：1.6.3

数据源Zookeeper

规则数据如下：每秒针对uid限制允许访问数量8

[
  {
    "id" : 5,
    "controlBehavior" : 0,
    "resource" : "sop",
    "intervalUnit" : 0,
    "count" : 8,
    "interval" : 1,
    "gmtCreate" : 1568252327724,
    "gmtModified" : 1568253506932,
    "app" : "mg-zuul-test",
    "ip" : "10.46.235.124",
    "paramItem" : {
      "fieldName" : "uid",
      "parseStrategy" : 2
    },
    "burst" : 0,
    "resourceMode" : 0,
    "grade" : 1,
    "port" : 8721
  }
]

问题描述

观察到单位时间流量通过的是3，拒绝的是1，但是我配置的针对header uid限流的阈值是8，总流量都没有达到特定限流的值，为什么就被拦截了？，如下图

对应时间Metrics.log

1568253804000|2019-09-12 10:03:24|sop|3|1|3|0|106|0|0|3
1568253804000|2019-09-12 10:03:24|__total_inbound_traffic__|3|1|3|0|106|0|0|0

原先有出现类似问题，在另一个issue1002里面

由于这个问题我们一直不敢在生产环境使用sentinel，请教下可能是啥原因

[sentinel-bot]

Hi @yugj, we detect non-English characters in the issue. This comment is an auto translation from @sentinel-bot to help other users to understand this issue.
We encourage you to describe your issue in English which is more friendly to other users.

QPS is blocked when it reaches the threshold??

Environment Description

Application gateway: zuul stand-alone

Sentinel version: 1.6.3

Zuul adaptor version: 1.6.3

Data source Zookeeper

The rule data is as follows: Permission limit per 8 for uid limit

[
  {
    "id" : 5,
    "controlBehavior" : 0,
    "resource" : "sop",
    "intervalUnit" : 0,
    "count" : 8,
    "interval" : 1,
    "gmtCreate" : 1568252327724,
    "gmtModified" : 1568253506932,
    "app" : "mg-zuul-test",
    "ip" : "10.46.235.124",
    "paramItem" : {
      "fieldName" : "uid",
      "parseStrategy" : 2
    },
    "burst" : 0,
    "resourceMode" : 0,
    "grade" : 1,
    "port" : 8721
  }
]

Problem Description

Observed that the unit time flow is 3, and the rejection is 1, but the threshold for the header uid current limit I configured is 8, and the total traffic does not reach the value of the specific current limit. Why is it intercepted? ,As shown below

Corresponding time Metrics.log

1568253804000|2019-09-12 10:03:24|sop|3|1|3|0|106|0|0|3
1568253804000|2019-09-12 10:03:24|__total_inbound_traffic__|3|1|3|0|106|0|0|0

There was a similar problem in the other [issue1002] (#1002)

Because of this problem, we have been afraid to use sentinel in the production environment. Please ask why

[sczyh30]

This might be related to #1039