Re: Drain L4 host that fronts a L7 cluster

Hi Abhijeet, On Mon, May 22, 2023 at 12:30:52PM -0700, Abhijeet Rastogi wrote: > Hi Willy, > > Thank you for the response. It's great to know that this might be > considered as a feature request in future versions, pending > prioritization though. > > Could you comment on why this isn't already

Re: Drain L4 host that fronts a L7 cluster

Hi Willy, Thank you for the response. It's great to know that this might be considered as a feature request in future versions, pending prioritization though. Could you comment on why this isn't already a feature yet? It is hard to believe that we're the first to come across this draining

Re: Drain L4 host that fronts a L7 cluster

On Fri, May 05, 2023 at 04:18:25PM -0700, Abhijeet Rastogi wrote: > Thanks for the response Tristan. > > For the future reader of this thread, a feature request was created > for this. https://github.com/haproxy/haproxy/issues/2146 I've looked again at the code and am seeing that in modern

Re: Drain L4 host that fronts a L7 cluster

Isn't is a similar request to https://github.com/haproxy/haproxy/issues/969 as I mentioned in the issue https://github.com/haproxy/haproxy/issues/2149 On 06.05.23 01:18, Abhijeet Rastogi wrote: Thanks for the response Tristan. For the future reader of this thread, a feature request was

Re: Drain L4 host that fronts a L7 cluster

Thanks for the response Tristan. For the future reader of this thread, a feature request was created for this. https://github.com/haproxy/haproxy/issues/2146 On Fri, May 5, 2023 at 4:09 PM Tristan wrote: > > > however, our reason to migrate to HAproxy is adding gRPC > > compliance to the

Re: Drain L4 host that fronts a L7 cluster

however, our reason to migrate to HAproxy is adding gRPC compliance to the stack, so H2 support is a must. Thanks for the workarounds, indeed interesting, I'll check them out. From a cursory look at the gRPC spec it seems like you would indeed really need the GOAWAY to get anywhere trigger

Re: Drain L4 host that fronts a L7 cluster

Hi Tristan, Thanks for the *excellent* reply. Indeed, the map based solution can work for H1, however, our reason to migrate to HAproxy is adding gRPC compliance to the stack, so H2 support is a must. Thanks for the workarounds, indeed interesting, I'll check them out. >trigger the GOAWAY H2

Re: Drain L4 host that fronts a L7 cluster

Hi Abhijeet, Problem statement is, how do you drain a node [...] L7 constructs like "Connection: close" or "GOAWAY h2 frames" [...] > * For any map (L4 client IP lookup) based solution, I was unable to find any http-request operation that sets "drain mode". Indeed the managed drain mode is

Drain L4 host that fronts a L7 cluster

Hi HAproxy community, We've the following production setup, clusters of: IPVS (dsr) -> L4 HAproxy (tcp termination) -> L7 Proxy (via pp, L7 done here. Not HAproxy today, but it soon will be) Problem statement is, how do you drain a node in L4 tier gracefully as it has no concept of L7