Hi Maksim,
On Thu, Feb 11, 2021 at 01:20:04PM +0300, ?? ? wrote:
> Thank you very much, Willy!
>
> Turning off abortonclose (it was enabled globally) for this particular
> session really helped :)
Fantastic, one less bug to chase :-)
Cheers,
Willy
Thank you very much, Willy!
Turning off abortonclose (it was enabled globally) for this particular
session really helped :)
--
Best regards,
Maksim
вт, 9 февр. 2021 г. в 17:46, Willy Tarreau :
> Hi guys,
>
> > > I faced a problem dealing with l4 (tcp mode) haproxy-based proxy over
> > > Graphit
Hi guys,
> > I faced a problem dealing with l4 (tcp mode) haproxy-based proxy over
> > Graphite's component receiving metrics from clients and clients who are
> > connecting just to send one or two Graphite-metrics and disconnecting right
> > after.
> >
> > It looks like this
> > 1. Client connect
Hi, Lukas!
I didn’t attach dump of haproxy to backend servers packets because there
were no such packets in this particular case. :( this haproxy installation
is heavy loaded with traffic. So it could be the reason haproxy even didn’t
start connecting to a backend in time. If I add some small dela
Hello,
On Mon, 8 Feb 2021 at 18:14, Максим Куприянов
wrote:
>
> Hi!
>
> I faced a problem dealing with l4 (tcp mode) haproxy-based proxy over
> Graphite's component receiving metrics from clients and clients who are
> connecting just to send one or two Graphite-metrics and disconnecting right
I have to go to sleep :)
for unknown reason I thought that you are out ot ephemeral ports due to
rapid connection reopen (aka ephemeral ports exhaustion).
вт, 9 февр. 2021 г. в 01:04, Максим Куприянов :
> Илья, thanks for your answer!
>
> Sorry, but It seems to me I didn't make it clear: the pro
Илья, thanks for your answer!
Sorry, but It seems to me I didn't make it clear: the problem is the data
received from these fast clients never reaches backends. But it should be
delivered in order to be saved.
Maybe there is some way to delay acknowledging of the data received until
some backend
I think it is "4. Client disconnects (FIN, FIN-ACK)"
if client would send RST instead of FIN, port would have been released
immediately.
https://stackoverflow.com/questions/13049828/fin-vs-rst-in-tcp-connections
RST is much better for short living connections.
пн, 8 февр. 2021 г. в 22:17, Макси
Hi!
I faced a problem dealing with l4 (tcp mode) haproxy-based proxy over
Graphite's component receiving metrics from clients and clients who are
connecting just to send one or two Graphite-metrics and disconnecting right
after.
It looks like this
1. Client connects to haproxy (SYN/SYN-ACK/ACK)
2
9 matches
Mail list logo
