Hello Peter,
Am 09.06.2017 um 10:27 schrieb Peter Kenens: > > I understand that more than 1 HAProxy process can be configured > (nbproc) and via cpu-map and bind-process you can specify to which > cores these processes might bind. > > I also understand that the table with cookies is kept in memory and > memory cannot be shared between the different processes. > > Is there a way how can we scale this to more cores while still having > session stickyness? I would recommend to use nbproc for frontend (SSL) traffic, but to handle the backend in a single process configuration. That way, stickiness, health checks, maxconn limits are not affected by the nbproc configuration. You will have to hairpin the traffic through a unix or abns socket though. You should be able to find some sample configuration in the mailing list archives. cheers, lukas
