Hi Luke,
On Mon, Mar 18, 2019 at 11:14:12AM -0400, Luke Seelenbinder wrote:
(...)
> If I disable HTX, everything flows per normal and the status codes are even
> correctly -1.
>
> I've replicated this on 1.9.4, 1.9.x master, and 2.0-dev master branches. The
> global "this will work" and "this
Hi everyone!
I assume I am misunderstanding something, but I cannot figure out what it is.
We are using haproxy in AWS, in this case as sidecars to applications so they
need not
know about changing backend addresses at all, but can always talk to localhost.
Haproxy listens on localhost and then
Hi Ashwin,
On Mon, Mar 18, 2019 at 10:57:45AM -0700, Ashwin Neerabail wrote:
> Hi Willy,
>
> Thanks for the reply.
>
> My Test setup:
> Client Server1 using local HAProxy 1.9 > 2 Backend servers and
> Client Server2 using local HAProxy 1.8 > same 2 backend servers.
>
> I am measuring latency
Hi Willy,
Thanks for the reply.
My Test setup:
Client Server1 using local HAProxy 1.9 > 2 Backend servers and
Client Server2 using local HAProxy 1.8 > same 2 backend servers.
I am measuring latency from the client server.
So when I run 1000rps test , 50% of them end up on 1.9 and 50% on 1.8.
Hi Willy,
Unfortunately, I spoke too soon in my last email. After hitting send, I went
down the rabbit hole again and uncovered some behaviors I thought we'd rooted
out. Namely, any time I use HTX mode with an H2 fe -> H1 or H2 backend and have
frequent request cancellation as discussed
Hi Willy,
I finally had the opportunity to try out `option abortonclose`.
Initially, it made the problem much worse. Instead of occasionally incorrect
status codes in the logs, I saw requests fail in the following manner:
[18/Mar/2019:12:30:08.040] stadiamaps~ tile/tile1 0/18603/-1/-1/24804
Hi,
I want to know to configure Email server in haproxy 1.8 version when any server
is down.
Regards
Shweta
::DISCLAIMER::
7 matches
Mail list logo
