On Wed, Dec 8, 2010 at 6:13 PM, Bryan Talbot <btal...@aeriagames.com> wrote: > See the architecture doc section 4.3 > http://haproxy.1wt.eu/download/1.3/doc/architecture.txt > -Bryan > When a new haproxy pid is started after it sends a SIGTTOU to the prior running haproxy pid, what is the state of the backends? If one backend was in a down state due to failed health checks, will it be marked up by the new process until it fails the configured number of checks?
> On Wed, Dec 8, 2010 at 12:51 PM, Joshua N Pritikin <jos...@paloalto.com> > wrote: >> >> I found: >> >> >> http://serverfault.com/questions/165883/is-there-a-way-to-add-more-backend-server-to-haproxy-without-restarting-haproxy >> http://sysbible.org/2008/07/26/haproxy-hot-reconfiguration/ >> >> However, these options are last documented in version 1.2: >> >> http://haproxy.1wt.eu/download/1.2/doc/haproxy-en.txt >> >> A brief search did not uncover any similar documentation in newer >> versions: >> >> http://haproxy.1wt.eu/download/1.3/doc/configuration.txt >> http://haproxy.1wt.eu/download/1.4/doc/configuration.txt >> >> What is the current approved way to do hot reconfiguration? >> > >
