I would like to propose a change to how TS handles unresponsive upstream
destinations. The current logic is
- If there is a round robin, skip elements that are down.
- Attempt to connect.
- If the connect fails, and the upstream is marked down and within the
down server cache time, res
Sounds reasonable to me!
A related aspect for completeness would be to also drop all the existing keep
alive sessions (including the “floor”) to a Server marked down, since session
reuse doesn’t go through the connect logic, and we still have the same problem
of client socket build up when thos
I thought I had, but I can't find it. I did discuss this at the last
summit, but that slide is not very informative..
On Fri, Oct 2, 2020 at 11:05 AM Sudheer Vinukonda
wrote:
> Sounds reasonable to me!
>
> A related aspect for completeness would be to also drop all the existing
> keep alive sess
