Invocation may broke when provider offline
- Dominant language
- Java
- Stars
- 41.6k
- Forks
- 26.4k
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 4
Description
- [ ] I have searched the [issues](https://github.com/apache/dubbo/issues) of this repository and believe that this is not a duplicate.
## Describe the proposal
When the provider is offline, the registry will push the offline notification to the consumer, and the consumer will stop all in-transit calls. This affects the overall request success rate.
Move the destroy actions of invoker into a seperate thread, wait unit all of the request end, then destroy.
Contributor guide
Research direction
Start by tracing how the registry's provider-offline notification reaches the consumer and where invoker destruction stops in-transit calls. Define the lifecycle behavior so existing requests finish before destruction, then verify that offline notifications no longer reduce request success through premature cancellation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100