I was looking for a solution for graceful reload of haproxy. I have a nginx server running which passes requests to Haproxy and at times I reload the Haproxy configuration. But I am observing that at time of reloading all the existing connections are getting cut off and haproxy backend queue shows 0 requests ( got from socket stats of haproxy ) .
Pound is infront of HAProxy for SSL off-load so HAProxy receives plaint text HTTP requests. I have HAProxy (v1.4.8) infront of two web-app servers hosting the same application. Below is my HAProxy config.
Currently, a client hits HAProxy, and can go to any server for their initial "GET /" request for the root of the site.
If I am using haproxy as my only publicly accessible server that's job is to route requests to our backend servers, will all data flow through the haproxy server?
If we have 50 servers and a single haproxy server, and the actual 1 gigabyte port on our front end haproxy server will not suffice.
If this is the case (which I believe it to be), what options do we have?
I believe I read something ab
I have several geographical regions for my service deployment, say Region1, Region2, and Region3. Each region has a failover haproxy instance. Each haproxy is configured with several backend servers that get passed requests to their private IP's.
I use a DNS based load balancing solution to direct each countries traffic to the fastest available region.
I'm just getting started with HAProxy and I was wondering if its possible to modify the request path for an HTTP request.
One of the backend server uses Dropwizard and its assets bundle see here bundle.
I use haproxy to loadbalancer multiple virtual machines (web services). Each virtual machine has multiple IP addresses.
What is best practice to setup this on haproxy? Right now my configuration are each IP of virtual machine have an entry "listen" on haproxy with corresponding two real server.
Can I ask if it can be revise like multiple "listen" and only two backend server.
I have installed Pound (for SSL off-load) and HAproxy on Debian 6 Squeeze.
I'm trying to figure out how to set up my architecture for a socket.io app that will require both https and wss connections. I've found many tutorials on the web suggesting that you use something like stud or stunnel in front of haproxy, which then routes your unencrypted traffic to your app.
For haproxy TCP load balancing, you only need to configure the "real servers" or "backends" behind the VIP (i.e., cluster IP).