alibaba / alibaba/Sentinel

关于熔断规则的问题

Open
#2,603 4 comments 0 reactions 0 assignees View on GitHub
area/circuit-breaking kind/question
Dominant language
Java
Stars
23.1k
Forks
8.1k
PR merge metrics
No merged PRs in 30d

Description

我使用的sentinel是**1.8.1的版本**,
配置了熔断的三种模式(慢调用比例、异常比例、异常数量),
并使用Jmeter进行了测试,但测试结果和预期完全不一致。

比如配置1秒内请求达到5个及以上且全部都超过最大RT则熔断也就是阈值为1,
但实际Jmeter测试一组10个或者更多都触发不了熔断,直到线程组设置到1000才触发。

对于**异常比例**来说也是同样。

**异常数量**则是确实测试5个线程确实会熔断,但好像在一个并发下的不会熔断,而是后续的已经处于熔断状态。也就是说熔断是会有延迟的么。

所以我想知道,为什么是这样的情况,不是很理解

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by reproducing the Sentinel 1.8.1 configurations with JMeter, covering slow-call, exception-ratio, and exception-count modes, then trace the circuit-breaking behavior that determines when the threshold is evaluated. Done means explaining the observed concurrency and delay differences with reproducible results.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.