> On Jun 29, 2018, at Jun 29, 12:50 PM, Leela Kalidindi (lkalidin)
> wrote:
>
> Not for Remote desktop protocol, it is for haproxy backend server with option
> persist as in
> "HAPROXY_0_BACKEND_HEAD": "\nbackend {backend}\n balance {balance}\n mode
> http\n option httplog\n option
Not for Remote desktop protocol, it is for haproxy backend server with option
persist as in
"HAPROXY_0_BACKEND_HEAD": "\nbackend {backend}\n balance {balance}\n mode
http\n option httplog\n option forwardfor\n option http-keep-alive\n option
persist\n http-reuse aggressive\n maxconn 16\n",
> On Jun 29, 2018, at Jun 29, 12:42 PM, Leela Kalidindi (lkalidin)
> wrote:
>
> Bryan,
>
> One another follow-up question - what does persist do? Thanks!
>
https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#persist
Bryan,
One another follow-up question - what does persist do? Thanks!
-Leela
From: Bryan Talbot
Date: Friday, June 29, 2018 at 12:40 PM
To: "Leela Kalidindi (lkalidin)"
Cc: HAproxy Mailing Lists
Subject: Re: Reuse backend connections
On Jun 29, 2018, at Jun 29, 12:38 PM, Leela
> On Jun 29, 2018, at Jun 29, 12:38 PM, Leela Kalidindi (lkalidin)
> wrote:
>
> Hi Bryan,
>
> Thanks a lot for the prompt response.
>
> Is there a such kind of thing to leave the backend connections open forever
> that can serve any client request?
>
No, not to my knowledge.
-Bryan
Hi Bryan,
Thanks a lot for the prompt response.
Is there a such kind of thing to leave the backend connections open forever
that can serve any client request?
-Leela
From: Bryan Talbot
Date: Friday, June 29, 2018 at 12:30 PM
To: "Leela Kalidindi (lkalidin)"
Cc: HAproxy Mailing Lists
> On Jun 29, 2018, at Jun 29, 5:11 AM, Leela Kalidindi (lkalidin)
> wrote:
>
> Hi,
>
> How can I enforce haproxy to reuse limited backend connections regardless of
> number of client connections? Basically I do not want to recreate backend
> connection for every front end client.
>
>
This patch changes the sending side of proxy protocol to convert IP
addresses to IPv4 when possible (and converts them IPv6 otherwise).
Previously the code failed to properly provide information under
certain circumstances:
1. haproxy is being accessed using IPv4, http-request set-src sets
a
On Fri, 29 Jun 2018 at 11:19, Milan Petruželka wrote:
> I've added more debug into h2s_close to see not only h2s state and flags
> but also h2c state and flags. My only way to reproduce the bug is to let
> Haproxy run until some of its FD falls into CLOSE_WAIT. After I catch some,
> I'll report
> Le 29 juin 2018 à 14:26, Mildis a écrit :
>
>>
>> Le 29 juin 2018 à 04:51, Willy Tarreau a écrit :
>>
>> Hi,
>>
>> On Thu, Jun 28, 2018 at 11:48:24AM +0200, m...@mildis.org wrote:
>>>
>>> Hi,
>>>
>>> When applying hex transform to an IPv6 in unique-id-format, the result is
>>> an
> Le 29 juin 2018 à 04:51, Willy Tarreau a écrit :
>
> Hi,
>
> On Thu, Jun 28, 2018 at 11:48:24AM +0200, m...@mildis.org wrote:
>>
>> Hi,
>>
>> When applying hex transform to an IPv6 in unique-id-format, the result is an
>> string full of zeros. unique-id-format %{+X}o\
>>
Hi,
How can I enforce haproxy to reuse limited backend connections regardless of
number of client connections? Basically I do not want to recreate backend
connection for every front end client.
"HAPROXY_0_BACKEND_HEAD": "\nbackend {backend}\n balance {balance}\n mode
http\n option
Hi Lukas,
On 06/27/2018 04:48 AM, Willy Tarreau wrote:
> On Wed, Jun 27, 2018 at 01:44:08AM +0200, Lukas Tribus wrote:
>> Hey guys,
>>
>>
>> FYI after lots of discussions with openssl folks:
>>
>> https://github.com/openssl/openssl/issues/5330
>> https://github.com/openssl/openssl/pull/6388
>>
Hi Willy,
I'm back at work after 2 weeks on the beach in Dalmatia. I've patched my
Haproxy 1.8.11 with all three patches discussed here in last two weeks. It
didn't help. Then tried to run Haproxy with debug enabled. The last logs
from FD hanging in CLOSE_WAIT looks like this:
Hi,
converters are just simple C functions, (or could be Lua code as well), and
are quite trivial to write.
Instead of creating a converter that reverse the order of chars in a
string, I would rather patch current "word" converter to support negative
integers.
IE: -2 would means you extract the
Hi Adwait,
So, you have a "timeout check" set to 5s as well.
Are your servers UP and RUNNING ?
If not, then timeout check would trigger before interval, and HAProxy would
retry a health check (up to 'fall' parameter).
(timeout connect might also trigger a retry if a S/A is not received by
16 matches
Mail list logo