On Wed, Mar 31, 2021 at 09:55:15AM -0700, Nathan Konopinski wrote:
> Thanks Willy, that is what I'm seeing, capture attached. Clients only send
> GETs, no POSTs. What are possible workarounds? Is there a way to ignore the
> client close and keep the connection open longer?
It's not what happens he
Hi Nathan,
On Tue, Mar 30, 2021 at 09:21:30AM -0700, Nathan Konopinski wrote:
> Sometimes clients (clients are only http 1.1 and use connection: close) are
> reporting a body length of ~4000 is less than the content length of ~14000.
> The issue does not appear when using nginx as an LB and I've v
Hi,
HAProxy 2.2.12 was released on 2021/03/31. It added 29 new commits
after version 2.2.11. This makes 2.2.12 catch up with the fixes that went
into 2.3.9:
- One issue was a regression of the rate counters causing those
spanning over a period (like in stick-tables) to increase forever
On Wed, Mar 31, 2021 at 02:29:40PM +0200, Vincent Bernat wrote:
> ? 31 mars 2021 12:46 +02, Willy Tarreau:
>
> > On the kernel Greg solved all this by issuing all versions very
> > frequently: as long as you produce updates faster than users are
> > willing to deploy them, they can choose what to
Hi,
HAProxy 1.7.14 was released on 2021/03/31. It added 7 new commits after
version 1.7.13, all of which are minor fixes. The main one addresses a
build regression when libmusl is used. The other ones are:
- fix for the too lax hdr_ip() parsing
- for the IPv6 fallback of a failed silent-drop a
❦ 31 mars 2021 12:46 +02, Willy Tarreau:
> On the kernel Greg solved all this by issuing all versions very
> frequently: as long as you produce updates faster than users are
> willing to deploy them, they can choose what to do. It just requires
> a bandwidth that we don't have :-/ Some weeks seve
Hello,
Just giving my feedback on part of the story:
On 31 Mar 12:46, Willy Tarreau wrote:
> On the kernel Greg solved all this by issuing all versions very
> frequently: as long as you produce updates faster than users are
> willing to deploy them, they can choose what to do. It just requires
>
I've forgot to mention that the backtrace is from 2.2.11 built from
http://git.haproxy.org/?p=haproxy-2.2.git;a=commit;h=601704962bc9d82b3b1cc97d90d2763db0ae4479
śr., 31 mar 2021 o 13:28 Maciej Zdeb napisał(a):
> Hi,
>
> Well it's a bit better situation than earlier because only one thread is
>
Hi,
Well it's a bit better situation than earlier because only one thread is
looping forever and the rest is working properly. I've tried to verify
where exactly the thread looped but doing "n" in gdb fixed the problem :(
After quitting gdb session all threads were idle. Before I started gdb it
lo
Hi Vincent!
On Wed, Mar 31, 2021 at 12:11:32PM +0200, Vincent Bernat wrote:
> It's a bit annoying that fixes reach a LTS version before the non-LTS
> one. The upgrade scenario is one annoyance, but if there is a
> regression, you also impact far more users.
I know, this is also why I'm quite a bi
❦ 31 mars 2021 10:35 +02, Willy Tarreau:
>> Thanks Willy for the quick update. That's a good example to avoid
>> pushing stable versions at the same time, so we have opportunities to
>> find those regressions.
>
> I know and we're trying to separate them but it considerably increases the
> requir
On Wed, Mar 31, 2021 at 10:17:35AM +0200, William Dauchy wrote:
> On Tue, Mar 30, 2021 at 6:59 PM Willy Tarreau wrote:
> > HAProxy 2.3.9 was released on 2021/03/30. It added 5 new commits
> > after version 2.3.8.
> >
> > This essentially fixes the rate counters issue that popped up in 2.3.8
> > af
On Tue, Mar 30, 2021 at 6:59 PM Willy Tarreau wrote:
> HAProxy 2.3.9 was released on 2021/03/30. It added 5 new commits
> after version 2.3.8.
>
> This essentially fixes the rate counters issue that popped up in 2.3.8
> after the previous fix for the rate counters already.
>
> What happened is tha
13 matches
Mail list logo
