Hi Valentine,
thank you for looking into this and sharing your thoughts. I'm not sure
if these questions were directed at me:
Valentine Krasnobaeva wrote:
cli_find_server() is used in all CLI command handlers, which manipulates
servers. So, let's discuss this use-case, if there is a willingne
Hello,
As for configuration, yes, as Lukas pointed, "hard-stop-after" is a
right setting, it was designed specifically for such case of long
connections.
If master-worker mode is used, there is also "mworker-max-reloads",
which can help.
https://docs.haproxy.org/3.0/configuration.html#3.1
Hi Jens !
Thanks for detailed explanations !
I've looked a bit, why you have this "Proxy is disabled." message,
when"@!PID shutdown sessions server"is issued.
In simply words, for old worker's backend proxies we set the flag
PR_FL_STOPPED during the reload and it's checked in the handler of
Lukas Tribus wrote:
take a look at the hard-stop-after configuration:
https://docs.haproxy.org/3.0/configuration.html#3.1-hard-stop-after
Thank you for this pointer. Actually, I thought about using
"hard-stop-after", but it does not really do what I would like (shut
down old sessions at con
Hello,
On Tuesday, 19 November 2024, Jens Wahnes wrote:
> Lukas Tribus wrote:
>
>> take a look at the hard-stop-after configuration:
>>
>> https://docs.haproxy.org/3.0/configuration.html#3.1-hard-stop-after
>>
>
> Thank you for this pointer. Actually, I thought about using
> "hard-stop-after", b
Hello,
take a look at the hard-stop-after configuration:
https://docs.haproxy.org/3.0/configuration.html#3.1-hard-stop-after
Lukas
Hi,
on my Haproxy instances in HTTP mode, I have some long-lived websocket
connections. When doing a reload of Haproxy (e.g. because of a config
change), this means that the old process will keep running with the
existing websocket connections. The websocket connections can be lasting
for a l
7 matches
Mail list logo
