Thanks a lot Baptiste. I am testing it as we speak.
Yes i am using the socket API. I use this( I just extracted it out of our implementation) https://github.com/althea/haproxy_manager Cheers sreekanth. On Sat, Sep 22, 2012 at 2:19 PM, Baptiste <[email protected]> wrote: > On Sat, Sep 22, 2012 at 10:28 AM, Sreekanth V <[email protected]> wrote: >> Hi >> >> We are considering using the following scheme to do our rolling deploys. >> >> For each server on haproxy. >> >> 1) Disable server out of haproxy >> 2) Deploy to the server >> 3) Enable server into haproxy >> >> The question is how does disable server handle existing connections to >> the server? Would it close them immediately or would it let the >> connections to complete but not accept new connections? >> >> Would setting the weight to 0% be better than disable server? >> >> Thanks >> sreekanth. >> > > Hi, > > Disable means that the server won't be used anymore by the > load-balance algorithm, hence it won't receive any new connections. > Sticked connection are still routed to this server, for a graceful shutdown. > Setting the weight to 0 would have the same effect. > > Note that you can use HAProxy socket to run the disable backend/server > command, it will apply the configuration without reloading haproxy. > > cheers
