Hi,

I was hoping the seamless reload in 1.8 would retain stick tables, but I'm
having no luck. Is it possible?

I'm testing this with:

haproxy: 1.8.8, single master, single thread, nbproc 1
OS: CentOS 7.4.1708
socket: stats socket /var/run/haproxy.sock level admin expose-fd listeners

Systemctl status:
● haproxy.service - HAProxy Load Balancer
   Loaded: loaded (/usr/lib/systemd/system/haproxy.service; enabled; vendor
preset: disabled)
   Active: active (running) since Wed 2018-04-25 19:28:21 CEST; 14h ago
  Process: 3504 ExecReload=/bin/kill -USR2 $MAINPID (code=exited,
status=0/SUCCESS)
  Process: 3503 ExecReload=/usr/sbin/haproxy -f $CONFIG -c -q (code=exited,
status=0/SUCCESS)
  Process: 3318 ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q
(code=exited, status=0/SUCCESS)
 Main PID: 3319 (haproxy)
   CGroup:
/docker/b456dcda6def2ef537ee15d9083799094193d2a314102101a3dfbca66b72de46/system.slice/haproxy.service
           ├─3319 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p
/run/haproxy.pid -sf 3497 -x /var/run/haproxy.sock
           └─3505 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p
/run/haproxy.pid -sf 3497 -x /var/run/haproxy.sock

Apr 25 19:53:29 lb01 haproxy[3319]: [WARNING] 114/195328 (3319) : Former
worker 3320 exited with code 0
Apr 25 19:53:56 lb01 haproxy[3319]: [WARNING] 114/195328 (3319) :
Reexecuting Master process
Apr 25 19:53:56 lb01 systemd[1]: Reloaded HAProxy Load Balancer.
Apr 25 19:53:56 lb01 haproxy[3319]: [WARNING] 114/195356 (3319) : Former
worker 3406 exited with code 0
Apr 25 19:57:24 lb01 haproxy[3319]: [WARNING] 114/195356 (3319) :
Reexecuting Master process
Apr 25 19:57:24 lb01 systemd[1]: Reloaded HAProxy Load Balancer.

haproxy -vv:

HA-Proxy version 1.8.8 2018/04/19
Copyright 2000-2018 Willy Tarreau <[email protected]>

Build options :
  TARGET  = linux2628
  CPU     = generic
  CC      = gcc
  CFLAGS  = -m64 -march=x86-64 -O2 -g -fno-strict-aliasing
-Wdeclaration-after-statement -fwrapv -fno-strict-overflow -Wno-unused-label
  OPTIONS = USE_SLZ=1 USE_REGPARM=1 USE_OPENSSL=1 USE_SYSTEMD=1 USE_PCRE=1

Default settings :
  maxconn = 2000, bufsize = 16384, maxrewrite = 1024, maxpollevents = 200

Built with OpenSSL version : OpenSSL 1.0.2k-fips  26 Jan 2017
Running on OpenSSL version : OpenSSL 1.0.2k-fips  26 Jan 2017
OpenSSL library supports TLS extensions : yes
OpenSSL library supports SNI : yes
OpenSSL library supports : SSLv3 TLSv1.0 TLSv1.1 TLSv1.2
Built with transparent proxy support using: IP_TRANSPARENT IPV6_TRANSPARENT
IP_FREEBIND
Encrypted password support via crypt(3): yes
Built with multi-threading support.
Built with PCRE version : 8.32 2012-11-30
Running on PCRE version : 8.32 2012-11-30
PCRE library supports JIT : no (USE_PCRE_JIT not set)
Built with libslz for stateless compression.
Compression algorithms supported : identity("identity"),
deflate("deflate"), raw-deflate("deflate"), gzip("gzip")
Built with network namespace support.

Available polling systems :
      epoll : pref=300,  test result OK
       poll : pref=200,  test result OK
     select : pref=150,  test result OK
Total: 3 (3 usable), will use epoll.

Available filters :
[SPOE] spoe
[COMP] compression
[TRACE] trace


-- 

Christian Greger
977 65 075/ [email protected]

[image: Twitter] <http://twitter.com/luxi2001> [image: Google Plus]
<http://plus.google.com/u/0/115102736822352604450> [image: Skype]

This e-mail message may contain confidential or legally privileged
information and is intended only for the use of the intended recipient(s).
Any unauthorized disclosure, dissemination, distribution, copying or the
taking of any action in reliance on the information herein is prohibited.
E-mails are not secure and cannot be guaranteed to be error free as they
can be intercepted, amended, or contain viruses. Anyone who communicates
with us by e-mail is deemed to have accepted these risks. Company Name is
not responsible for errors or omissions in this message and denies any
responsibility for any damage arising from the use of e-mail. Any opinion
and other statement contained in this message and any attachment are solely
those of the author and do not necessarily represent those of the company.

Reply via email to