Hi Alex,
On Sat, Dec 25, 2021 at 11:59:20PM +0100, Aleksandar Lazic wrote:
>
> Hi.
>
> as the message tell us that we should report this to the developers I do so
> :-)
>
>
> ```
> Dec 24 01:10:31 lb1 haproxy[20008]: A bogus STREAM [0x559faa07b4f0] is
> spinning at 204371 calls per second
> and refuses to die, aborting now!
> Please report this error to developers
> [strm=0x559faa07b4f0,12390e src=::ffff:79.183.184.235 fe=https-in be=be_api
> dst=api_main2
> txn=0x559faab233e0,44000 txn.req=MSG_DONE,d txn.rsp=MSG_RPBEFORE,0
> rqf=48c4e068 rqa=40000
> rpf=a000a860 rpa=0 sif=CLO,2c8002 sib=CLO,1280112 af=(nil),0
> csf=0x559faa07ba10,1059a0
> ab=(nil),0 csb=0x559faad7dcf0,1a0
>
> cof=0x7f224212e5d0,80003300:H2(0x559faa7d7b00)/SSL(0x7f22424fc7a0)/tcpv6(2162)
> cob=0x7f2240f79fe0,8982300:H1(0x559faa0ab840)/SSL(0x7f2263517770)/tcpv4(1490)
> filters={0x559faa29c520="cache store filter"}]
(...)
Interesting, thank you. I'm not aware of this one, it seems that the cache
filter is ignoring the fact that everything's closed on both sides, as if
a client abort happened at the same instant as a close from the server,
while the response was being analysed by the filter. I'm not aware of any
particular bug related to this, but I know that Christopher recently fixed
certain issues related to shutdowns and this one might have escaped. We'll
have to discuss this next week.
Thanks,
Willy
