[gateway] Share dial failures with current waiters
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 625
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 97
Description
### Description
PR #4078 intentionally keeps connection management simple: a failed dial is not cached, so waiting and subsequent requests retry after the previous attempt finishes.
As a follow-up, evaluate sharing one completed dial failure with requests that were already waiting for that attempt, without caching the failure for future requests. Later requests should still retry immediately after the failed attempt completes.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing PR #4078 and the gateway connection-management path it changed. Trace how waiting requests observe a failed dial, then define completion as sharing that failure only with current waiters while later requests retry immediately without cached failure state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100