Two tiered haproxy setup and managing queues and back pressure

We have a setup which requires us to have two haproxy tiers so that first forwards connections to the second. What I want to know is the theory how (and why) I should tune my maxconn, backlog and timeout settings to handle queues overloads and back pressure in situations where my backends are

subscribe

Re: Can I add one new server without stop the haproxy process?

You can't. The socket admin interface allows you to only disable existing servers and then re-enable them, but you can't add a completely new server. However you can reload haproxy so that it minimises and on some platforms eliminates dropping any existing connections. Probably your init script

Re: HAProxy 1.5 incorrectly marks servers as DOWN

modified haproxy binarines in my environment so that I could trace this further. On Mon, Sep 8, 2014 at 11:30 AM, Juho Mäkinen j...@unity3d.com wrote: On Thu, Sep 4, 2014 at 11:35 PM, Pavlos Parissis pavlos.paris...@gmail.com wrote: On 04/09/2014 08:55 πμ, Juho Mäkinen wrote: I'm upgrading

Re: HAProxy 1.5 incorrectly marks servers as DOWN

Thanks Pavlos for your help. Fortunately (and embarrassedly for me) the mistake was not anywhere near haproxy but instead my haproxy configure template system had a bug which mixed up the backend name and ip address. Because of this haproxy showed different names for those servers which were

Re: HAProxy 1.5 incorrectly marks servers as DOWN

On Thu, Sep 4, 2014 at 11:35 PM, Pavlos Parissis pavlos.paris...@gmail.com wrote: On 04/09/2014 08:55 πμ, Juho Mäkinen wrote: I'm upgrading my old 1.4.18 haproxies to 1.5.4 and I have a mysterious problem where haproxy marks some backend servers as being DOWN with a message L4TOUT

Re: Spam to this list?

On Fri, Sep 5, 2014 at 1:17 PM, Lukas Tribus luky...@hotmail.com wrote: Restricting the list to subscribed user (subonlypost) is not a good thing either May I ask why this is not a good thing? I see no valid reason why not subscribed members should be allowed to post. The subscription already

HAProxy 1.5 incorrectly marks servers as DOWN

I'm upgrading my old 1.4.18 haproxies to 1.5.4 and I have a mysterious problem where haproxy marks some backend servers as being DOWN with a message L4TOUT in 2000ms. Some times the message also has a star: * L4TOUT in 2000ms (I didn't find what the star means from the docs). Also the reported