Le 08/10/2024 à 18:07, Christopher Faulet a écrit :
Le 08/10/2024 à 16:13, Christopher Faulet a écrit :
Le 08/10/2024 à 11:05, Luke Seelenbinder a écrit :
Hi Christopher,
I was out last week, but we were able to gather a few more pieces of data.
1) We ran some tcpdumps, and nothing odd popped
Le 08/10/2024 à 16:13, Christopher Faulet a écrit :
Le 08/10/2024 à 11:05, Luke Seelenbinder a écrit :
Hi Christopher,
I was out last week, but we were able to gather a few more pieces of data.
1) We ran some tcpdumps, and nothing odd popped up at all. Given our traffic
levels, we were actuall
Le 08/10/2024 à 11:05, Luke Seelenbinder a écrit :
Hi Christopher,
I was out last week, but we were able to gather a few more pieces of data.
1) We ran some tcpdumps, and nothing odd popped up at all. Given our traffic
levels, we were actually surprised how few RST, etc. we had. Any TCP issues
Hi Christopher,
I was out last week, but we were able to gather a few more pieces of data.
1) We ran some tcpdumps, and nothing odd popped up at all. Given our traffic
levels, we were actually surprised how few RST, etc. we had. Any TCP issues
that did occur did *not* coincide with the SD-- log
Le 26/09/2024 à 17:59, Luke Seelenbinder a écrit :
Hi again,
Sorry, it's the opposite direction of that. Varnish is the client in this case
(it sits behind a few other pieces, but that's the relevant for the bug). Full flow:
Client -> HAProxy -> Varnish -> HAProxy -> HAProxy Upstream applicat
Hi again,
Sorry, it's the opposite direction of that. Varnish is the client in this case
(it sits behind a few other pieces, but that's the relevant for the bug). Full
flow:
Client -> HAProxy -> Varnish -> HAProxy -> HAProxy Upstream application.
That make more sense? :)
Best,
Luke
—
Luke Se
Le 26/09/2024 à 17:18, Luke Seelenbinder a écrit :
Hi Christopher,
Thanks for the response.
Sorry, I don't understand, the response was successfully sent to the client
when this happens or not ? It is "just" an issue with the termination state or
there is also an issue with the response itsel
Just a quick update. `-dZ` doesn't seem to have any impact on the number of
`SD--` requests.
—
Luke Seelenbinder
Stadia Maps | Founder & CEO
stadiamaps.com
> On Sep 26, 2024, at 18:18, Luke Seelenbinder
> wrote:
>
> Hi Christopher,
>
> Thanks for the response.
>
>> Sorry, I don't understand
Hi Christopher,
Thanks for the response.
> Sorry, I don't understand, the response was successfully sent to the client
> when this happens or not ? It is "just" an issue with the termination state
> or there is also an issue with the response itself ?
It's also an issue with the response. The
Hi Luke,
Le 26/09/2024 à 12:28, Luke Seelenbinder a écrit :
On upgrading to 3.0.5, we began to see a lot of failed backend requests. They
are successful status codes but fail with connection state `SD--`. On the
upstream side, the request succeeds (the upstream is also HAProxy, its state is
`-
Hi List,
On upgrading to 3.0.5, we began to see a lot of failed backend requests. They
are successful status codes but fail with connection state `SD--`. On the
upstream side, the request succeeds (the upstream is also HAProxy, its state is
``).
The data appears to be fully transferred wit
11 matches
Mail list logo
