Hi Dominik,

> The spikes seem to be fixed now
Thanks for the update!

However, we are now observing log messages during shutdown that weren’t
there before:
> 
>  
> 
> May 12, 2023 @ 11:56:24.000       Proxy health_check_http_tcp-scheduler 
> stopped (cumulated conns: FE: 0, BE: 0).
> 
> May 12, 2023 @ 11:56:24.000       Proxy http-in stopped (cumulated conns: FE: 
> 166, BE: 0).
> 
> May 12, 2023 @ 11:56:24.000       Proxy st_http_req_rate stopped (cumulated 
> conns: FE: 0, BE: 0).
> 
> May 12, 2023 @ 11:56:24.000       Proxy https-in stopped (cumulated conns: 
> FE: 29570, BE: 0).
> 
> May 12, 2023 @ 11:56:24.000       Proxy st_tcp_conn_rate stopped (cumulated 
> conns: FE: 0, BE: 0).
> 
> May 12, 2023 @ 11:56:24.000       Proxy http-routers-http2 stopped (cumulated 
> conns: FE: 0, BE: 14768).
> 
> May 12, 2023 @ 11:56:24.000       Proxy stats stopped (cumulated conns: FE: 
> 1, BE: 0).
> 
> May 12, 2023 @ 11:56:24.000       Proxy health_check_http_url stopped 
> (cumulated conns: FE: 1811, BE: 0).
> 
> May 12, 2023 @ 11:56:24.000       Proxy tcp-frontend_scheduler stopped 
> (cumulated conns: FE: 3, BE: 0).
> 
> May 12, 2023 @ 11:56:24.000       Proxy <HTTPCLIENT> stopped (cumulated 
> conns: FE: 0, BE: 0).
> 
> May 12, 2023 @ 11:56:24.000       Proxy tcp-scheduler stopped (cumulated 
> conns: FE: 0, BE: 3).
> 
> May 12, 2023 @ 11:56:24.000       Proxy http-routers-http1 stopped (cumulated 
> conns: FE: 0, BE: 134385).


These messages are totally inoffensive: they're only informative and are
generated each time a proxy is explicitly disabled.

As for why there weren't there before, it is probably due to this commit
which was shipped with 2.7.5:

> commit 48678e483f4f47e2a212a545399009b87503ea2d
> Author: Christopher Faulet <cfau...@haproxy.com>
> Date:   Tue Mar 14 14:33:11 2023 +0100
> 
>     BUG/MEDIUM: proxy: properly stop backends on soft-stop
>     
>     On soft-stop, we must properlu stop backends and not only proxies with at
>     least a listener. This is mandatory in order to stop the health checks. A
>     previous fix was provided to do so (ba29687bc1 "BUG/MEDIUM: proxy: 
> properly
>     stop backends"). However, only stop_proxy() function was fixed. When 
> HAproxy
>     is stopped, this function is no longer used. So the same kind of fix must 
> be
>     done on do_soft_stop_now().
>     
>     This patch partially fixes the issue #1874. It must be backported as far 
> as
>     2.4.

(prior to this commit, some of the proxies were not properly /
explicitly disabled during soft-stop)

Regards,
Aurelien

Reply via email to