apache/dubbo
Voir sur GitHub[Bug] Is there any graceful way to prevent running out of http2 stream id in Dubbo3.x
Open
#14 098 ouverte le 17 avr. 2024
help wantedtype/proposal
Métriques du dépôt
- Stars
- (41 524 stars)
- Métriques de merge PR
- (Merge moyen 7j 14h) (20 PRs mergées en 30 j)
Description
Pre-check
- I am sure that all the content I provide is in English.
Search before asking
- I had searched in the issues and found no similar issues.
Apache Dubbo Component
Java SDK (apache/dubbo)
Dubbo Version
Dubbo 3.x
Steps to reproduce this issue
Based on the discussion in #13731, I think it is an improper way to make a reconnection triggered by GoAwayFrame(stream id exhausted) cause there will be 100% request failure before the new connection being active and it is unacceptable for production scenario. To make sure the connection is consistently available, is it possible to make a new connection before the stream id is about to be exhausted?
What you expected to happen
- Make a new connection before the stream id is about to be exhausted.
Anything else
No response
Are you willing to submit a pull request to fix on your own?
- Yes I am willing to submit a pull request on my own!
Code of Conduct
- I agree to follow this project's Code of Conduct