Support timeout "cut-down" mechanism
Open
area/annotation
kind/feature
- 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)
can‘t change Hystrix to Sentinel because RT options not suitable our project
### Describe what you expected to happen
`@SentinelResource` can support timeout fallback in the future, which resembles `timeoutInMilliseconds` property of `@HystrixCommand`. Or can you give me some alternatives?
Contributor guide
Research direction
Start by reviewing the @SentinelResource timeout-fallback request and comparing it with Hystrix's timeoutInMilliseconds behavior. Clarify the desired timeout semantics and alternatives first; done means the agreed mechanism is implemented and its timeout behavior is covered and documented.
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
- Needs clarification
- Newbie friendliness
- 25/100