Re: problem with sort of caching of use_backend with socket.io and apache

2012-11-29 Thread david rene comba lareu
Hi, many thanks, your link was exactly what i needed ! :D Regards, Shadow. 2012/11/29 Baptiste bed...@gmail.com: Hi David, For more information about HAProxy and websockets, please have a look at: http://blog.exceliance.fr/2012/11/07/websockets-load-balancing-with-haproxy/ It may give you

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread Baptiste
Hi, This is not HAProxy's role, this is the tool you use to ensure high availability to do that. I could see a way where HAProxy can report one interface failing, maybe this could help you to detect if you're in a split brain situation. cheers On Thu, Nov 29, 2012 at 11:51 AM, Hermes Flying

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread Robert Snyder
Hi, We use Keepalived http://www.keepalived.org/index.html to manage the Virtual IP address management between our two physical HAproxy servers. It maintains heartbeat between the servers, and in the event of failure passes ensures that the VIPs are migrated and the service is brought up. Also

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread Hermes Flying
Hi Robert, But with keep alive you can only detect that the 2 nodes can not contact each other (network failure). How do you know if the other node/process actually crashed so that the secondary can become the primary? From: Robert Snyder r...@psu.edu To:

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread Robert Snyder
David, Exactly. Robert On Nov 29, 2012, at 1 :57 PM, David Coulson da...@davidcoulson.net wrote: You can do that, but haproxy doesn't have anything to do with the failover process, other than you run an instance of haproxy on one server, and another instance on your backup system. As I

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread David Coulson
Again, you are mixing everything up. HAProxy has it's own configuration - It defines what nodes your port 80 traffic (or whatever) is routed to. Haproxy does periodic health checks of these backend services to make sure they are available for requests. If you have multiple haproxy instances

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread Hermes Flying
Something like the following:    HAProxy1 Tomcat1  |    +/\ |   + |+---Tomcat2 +    /+\     + + HAProxy2+++   HAProxy1 is in the same machine as Tomcat1 HAproxy2 is in the same machine as

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread David Coulson
Both haproxy instances have the same config, with the tomcat instances with the same weight, etc. Run something like keepalived or pacemaker to manage a VIP between the two boxes. That's it. Not sure about keepalived, but pacemaker can make sure haproxy is running, then either restart it or

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread Hermes Flying
I see now! One last question since you are using Pacemaker. Do you recommend it for splitbrain so that I look into that direction? I mean when you say that pacemaker restart HAProxy, does it detect network failures as well? Or only SW crashes?  I assume pacemaker will be aware of both HAProxy1

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread Owen MArinas
we have exactly that setup with heartbeat, and 2 floating IPs. Working in production for 3 years now Owen On 29/11/2012 3:26 PM, David Coulson wrote: On 11/29/12 3:11 PM, Hermes Flying wrote: I see now! One last question since you are using Pacemaker. Do you recommend it for splitbrain so

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread Hermes Flying
Hi Owen,  How does the heartbeat this help for splitbrain? With heartbeat the nodes know that it can't talk to each other. They don't know if the other is down. If there is a different communication path between the nodes and the incoming requests, both can become primary assuming the other is

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread David Coulson
Again, you need to talk to the pacemaker people for actual clustering information. The ping was so a node could detect it lost upstream connectivity, and move the VIP, otherwise the VIP may continue to run on a system which does not have access to your network. This has nothing at all to do

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread Hermes Flying
Thank you for your help. I take it that you are find Pacemaker reliable in your experience? Should I look into it? From: David Coulson da...@davidcoulson.net To: Hermes Flying flyingher...@yahoo.com Cc: Baptiste bed...@gmail.com; haproxy@formilux.org

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread David Coulson
In general, yes, Pacemaker is reliable. If your config is wrong, you may still have an outage in the event of a failure. That said, if you are a business and need support, you probably want to use whatever clustering software ships with the distribution you use. I belive SuSE uses pacemaker,

Re: HAproxy and detect split-brain (network failures)

2012-11-29 Thread Hermes Flying
Great help! Thank you for your time! Much appreciated! From: David Coulson da...@davidcoulson.net To: Hermes Flying flyingher...@yahoo.com Cc: Baptiste bed...@gmail.com; haproxy@formilux.org haproxy@formilux.org Sent: Thursday, November 29, 2012 11:13 PM

RE: stunnel + haproxy + ssl + ddns + multiple domains

2012-11-29 Thread Rob Cluett
Thank you Baptiste. I am implementing this now. The procedure I was looking at had me making it more complicated than it needed to be. -Original Message- From: Baptiste [mailto:bed...@gmail.com] Sent: Thursday, November 29, 2012 2:29 AM To: Rob Cluett Cc: haproxy@formilux.org Subject: Re: