Wow, Many thanks!I implement these configurations, I will keep you
updated!
Best Regards,Domenico
Il giorno mar, 21/04/2020 alle 10.19 +0200, William Lallemand ha
scritto:
> On Tue, Apr 21, 2020 at 10:07:27AM +0200, Domenico Briganti wrote:
> > Thanks William, yes, the reload of haproxy is a feasible way, I
> > hadn'tnoticed.I have just one doubt, since I update the crl every
> > day and Ihave mqtt connections that can stay connected for days, at
> > the end Ican have many haproxy process running, one a day, until
> > all oldconnection (of that day) terminates. I think that with ps
> > and netstatsI can see how many they are and how many old
> > connections each processmanages.However I can afford a complete
> > restart of haproxy once everytwo/three weeks.Regards,Domenico
>
> If you configure the master CLI (haproxy -S binary argument), you
> willbe able to access to the CLI of the previous process and monitor
> theremaining connections. The previous process won't leave until
> theconnections aren't closed.
> You can force a process to leave even if there are still
> someconnections with the directive "hard-stop-after".
> https://cbonte.github.io/haproxy-dconv/2.2/configuration.html#3.1-hard-stop-after
>
> You can also limit the number of workers with the directive"mworker-
> max-reloads".
> https://cbonte.github.io/haproxy-dconv/2.2/configuration.html#3.1-mworker-max-reloads
>
> Regards,
