On Fri, Jan 05, 2018 at 03:52:22PM +0100, Pierre Cheynier wrote: > OK so now that I've applied all of Lukas recos (I kept the -x added ) : > > * I don't see any ALERT log anymore.. Only the WARNs >
I'm still seing a few of them in journalctl. Maybe you don't see those emitted by the workers, there is still room for improvement there. I'm taking notes. > Jan 05 14:47:12 hostname systemd[1]: Reloaded HAProxy Load Balancer. > Jan 05 14:47:12 hostname haproxy[59888]: [WARNING] 004/144712 (59888) : > Former worker 61331 exited with code 0 > Jan 05 14:47:25 hostname haproxy[59888]: [WARNING] 004/144712 (59888) : > Reexecuting Master process > Jan 05 14:47:26 hostname systemd[1]: Reloaded HAProxy Load Balancer. > Jan 05 14:47:26 hostname haproxy[59888]: [WARNING] 004/144726 (59888) : > Former worker 61355 exited with code 0 > > * I still observe the same issue (here doing an ab during a > rolling/upgrade of my test app => consequently triggering N reloads on > HAProxy as long as the app instances are created/destroyed). > > $ ab -n100000 http://test-app.tld/ > (..) > Benchmarking test-app.tld (be patient) > apr_socket_recv: Connection reset by peer (104) > Total of 3031 requests completed > I'm able to reproduce, looks like it happens with the nbthread parameter only, I'll try to find the problem in the code. -- William Lallemand
