Web Servers Load balancing with HAProxy

-

HAProxy is a free, very fast and reliable solution offering high availability,load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for very high traffic web sites and powers quite a number of the world’s most visited ones. See more at http://haproxy.org

This tuturial, I use hostname and ip as follows:
10.11.218.250 (haproxy)
10.11.218.251 (srv-web01)
10.11.218.252 (srv-web02)

Installing HAProxy server
#yum install haproxy [RedHat Systems]
#apt-get install haproxy [Debian Systems]

Configuring HAProxy Server
Opening the main HAProxy configuration file ‘/etc/haproxy/haproxy.cfg’ and editing the following content:


#----------------------------------------------------------------

# Global settings
global


# need to:

# to have these messages end up in /var/log/haproxy.log you will
 #


# by adding the '-r' option to the SYSLOGD_OPTIONS in

# 1) configure syslog to accept network log events. This is done
 # /etc/sysconfig/syslog
 #


# /etc/sysconfig/syslog

# 2) configure local2 events to go to the /var/log/haproxy.log
 # file. A line like the following can be added to
 #
 # local2.* /var/log/haproxy.log
 #


# turn on stats unix socket

log 127.0.0.1 local2
    chroot /var/lib/haproxy
    pidfile /var/run/haproxy.pid
    maxconn 4000
    user haproxy
    group haproxy
    daemon


log                     global

stats socket /var/lib/haproxy/stats
#---------------------------------------------------------------
# Defaults settings
defaults
    mode                    http


option                  redispatch

option                  httplog
    option                  dontlognull
    option http-server-close
    option forwardfor       except 127.0.0.0/8
    retries                 3


timeout check           20

timeout http-request    20
    timeout queue           86400
    timeout connect         86400
    timeout client          86400
    timeout server          86400
    timeout http-keep-alive 30


frontend lb_in

maxconn                 50000
#----------------------------------------------------------------
#main frontend which proxys to the backends




bind *:80


default_backend lb_http



backend lb_http



balance roundrobin

mode http


server srv-web01 10.11.218.251:80 check

server srv-web02 10.11.218.252:80 check



#-------------------------- THE END -----------------------------

Restarting and verify HAProxy Load Balancer

Comments

Post a Comment

Popular posts from this blog

Redirect all unencrypted traffic to HTTPS in Apache

-
To redirect all HTTP traffic to HTTPS administrators are encouraged to issue a permanent redirect using the 301 status code. When using Apache this can be achieved by a setting such as the following in the Apache VirtualHosts config: <VirtualHost *:80> ServerName example.com Redirect permanent / https://example.com/ </VirtualHost>
Read more

Using nginx as http load balancer

-
Image
Load balancing across multiple application instances is a commonly used technique for optimizing resource utilization, maximizing throughput, reducing latency, and ensuring fault-tolerant configurations. Nginx is a very efficient HTTP load balancer to distribute traffic to several application servers and to improve performance, scalability and reliability of web applications. Nginx Load balancing methods The following load balancing mechanisms (or methods) are supported in nginx: round-robin least-connected ip-hash See detail at http://nginx.org/en/docs/http/load_balancing.html Initialization Nginx Load Banlancing In this tutorial I use any hostname and ip addresses as follows: srv-lb01 (10.11.218.250) (Nginx load balancer) srv-web01 (10.11.218.251) ( Web server) srv-web02 (10.11.218.252) ( Web server) srv-web03 (10.11.218.253) ( Web server) Note: pointing nginx.vn to 10.11.218.250 (Replace nginx.vn with your real site name) Default load balancing c
Read more