alibaba / alibaba/Sentinel

[熔断]参数/下游方熔断需求 | Circuit breaking by slow params

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

Description

## Issue Description

Type: *feature request*

### Describe what happened (or what feature you want)
我们有一个业务场景,有一个应用作为出口应用,一个对外接口会依赖外部数百个下游。
这些下游中的一部分服务不稳定,可能会出现变慢的情况,当个别或者少数下游服务变慢,可能会拖住整个业务线程的线程池。
我们当前使用的熔断模式,是资源级别的,是对一个资源全部熔断,所以当前我们对这个几百个下游依赖在资源层面做了粗粒度划分未几个资源,熔断器开启可以熔断一个资源中数十个下游。

### Describe what you expected to happen
我们希望有类似来源方限流/参数限流的一种熔断方式,暂且叫做参数熔断/下游方熔断,可以根据下游的数量创建等数量的熔断器,当一个下游变慢时,只熔断这个下游的请求,其他下游的请求不受影响,达成一种下游方资源隔离的状态。

我有开发这个特性的打算,所以想探讨下这个需求的通用性。同时,在这之前,在社区请教下是否有可用组合方案能满足上述需求?

Contributor guide

Open the contributing guide

Research direction

Start by reviewing Sentinel’s existing resource-level circuit breaking and source/parameter limiting mechanisms, then compare them with the proposed per-downstream behavior described here. Define the scope and completion criteria for isolating slow downstreams before implementation; this issue names no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.