服务降级RT策略,可否实现设置一个响应时间,接口响应时间大于设置的值马上就快速熔断,而不是计算平均值再进行熔断处理
- Dominant language
- Java
- Stars
- 23.1k
- Forks
- 8.1k
- PR merge metrics
- No merged PRs in 30d
Description
## Issue Description
服务降级RT策略,可否实现设置一个响应时间,接口响应时间大于设置的值马上就快速熔断,而不是计算平均值再进行熔断处理
### Describe what happened (or what feature you want)
通过设置一个响应时间,接口的响应时间大于该值服务马上就快速熔断,而不是计算平均值再进行熔断处理
### Describe what you expected to happen
### How to reproduce it (as minimally and precisely as possible)
### Tell us your environment
no
### Anything else we need to know?
no
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the existing service-degradation RT strategy and its circuit-breaking behavior, then clarify the configuration and acceptance criteria before changing it. Done means the requested response-time threshold behavior is implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100