Thank you
I'll try it on ------------------ ???????? ------------------ ??????: "Lukas Tribus"<[email protected]>; ????????: 2019??4??22??(??????) ????4:58 ??????: "Marco Corte"<[email protected]>;"????????"<[email protected]>; ????: "haproxy"<[email protected]>; ????: Re: one health check instead of muli check when using master-worker model Hello, On Mon, 22 Apr 2019 at 10:53, Marco Corte <[email protected]> wrote: > > Hi! > > But may I use only one health check process ,and all the process share > > the result > > of the health check, then there are only one check every 3 sec, how to > > archive this? > > I would try the "track" option: Track only solves multiple health checks when you are using multiple backends in the same process with the same servers. This is not that. > The suggestion in > http://cbonte.github.io/haproxy-dconv/1.9/management.html#7 "...it > appears that the easiest setup often consists in having one first layer > running on multiple processes and in charge for the heavy processing, > passing the traffic to a second layer running in a single process." may > further help in reducing the number of "backend processes" and > consequently the number of checks. Right, meaning multiple layers, which is complicated. This is why thread support was introduced though. Using threads instead of processes fixes this. Achieving the same performance with threads will require some tuning, but at the end you'll end up with a simple and scalable configuration. Lukas
