Not a 503, but rather a 504... 503 means no servers were available when HAProxy was processing the request.
cheers On Sat, Jan 12, 2013 at 12:58 AM, Bryan Talbot <[email protected]> wrote: > If by "go down" you mean that the server stops unexpectedly, then haproxy > will NOT retry requests that have already been sent to a backend server. If > that server goes down the client will receive an error (503 or something) > and will have to decide what action to take. > > -Bryan > > > On Fri, Jan 11, 2013 at 3:22 AM, Steven Acreman > <[email protected]> wrote: >> >> Hi Manoj, >> >> 1. It depends how you have everything configured. Haproxy will send >> requests to a working server if one goes down, it can also retry the failed >> ones on the working server. If your app has sessions you then need to ensure >> they are available on the other servers otherwise users will get logged out >> etc. >> >> 2. Yes, just update the haproxy configuration file and reload the service >> (works perfectly for me on RHEL 6.3 anyway). >> >> Thanks, >> >> Steven >> >> On 11 January 2013 11:04, Manoj Joshi <[email protected]> wrote: >>> >>> Hello There, >>> >>> >>> >>> Greetings for the day. >>> >>> >>> >>> I am planning to use haproxy in my live web cluster. I have few queries >>> and concerns below. Kindly help me out in understanding these : >>> >>> >>> >>> 1) How haproxy will act in case a server from web cluster goes down that >>> has already few sessions running. What will happen with those already >>> connected sessions? >>> >>> >>> >>> 2) Can I add a new server to the web cluster on haproxy configuration >>> without impacting its current sessions? >>> >>> >>> >>> >>> >>> Thanks & Regards, >>> >>> Manoj Kumar Joshi >>> >>> SO Support Track Lead >>> >>> Express KCS >>> >>> >>> >>> IM: mkjoshi-ekcs (Skype) >>> >>> E: [email protected] >>> >>> U: www.expresskcs.com >>> >>> >> >> > > >
