Shulou(Shulou.com)06/03 Report--

Using haproxy- to realize Seven-layer load balancing

HAProxy Overview:

HAProxy provides high availability, load balancing, agents based on TCP and HTTP applications, and supports virtual hosts. It is a free, fast and reliable solution. According to official data, its maximum limit supports 10G concurrency. HAProxy is especially suitable for heavily loaded web sites, which usually require session persistence or seven-tier processing. HAProxy runs on current hardware and can support tens of thousands of concurrent connections. And its mode of operation makes it easy and secure to integrate into your current architecture, while protecting your web server from being exposed to the network.

It supports network switching from layer 4 to layer 7, that is, covering all TCP protocols. That is, Haproxy even supports load balancing for Mysql.

Similarity: functionally, proxy uses reverse proxy to achieve WEB load balancing. Same as Nginx,ApacheProxy,lighttpd,Cheroke and so on.

The difference: Haproxy is not a Http server. All the products with reverse proxy load balancing mentioned above are all WEB servers. Simply put, they can provide static (html,jpg,gif..) on their own. Or dynamic (php,cgi..) Transfer and processing of files. Haproxy is only, and specifically, an application agent for load balancing. It does not provide http services on its own. But its configuration is simple, it has a very good server health check function and a special system status monitoring page. When the back-end server of its agent fails, HAProxy will automatically remove the server, and then automatically join the server after the fault is restored.

One: experimental topology diagram:

Second: experimental objectives

Practice: using haproxy to realize load balancing Cluster

Three: experimental environment

Xuegod63: 192.168.1.63

Xuegod64: 192.168.1.64

Xuegod62: 192.168.1.62

Four: experimental code

1. Build, compile and install haproxy environment

1) decompress haproxy software package

[root@xuegod63 ~] # tar-zxvf haproxy-1.4.22.tar.gz

[root@xuegod63 haproxy-1.4.22] # cd / root/haproxy-1.4.22

[root@xuegod63 haproxy-1.4.22] # uname-r # View kernel version

2.6.32-220.el6.x86_64

2) installation

[root@xuegod63 haproxy-1.4.22] # make TARGET=linux26 PREFIX=/usr/local/haproxy # specifies the operating system kernel type and installation path. You can also directly modify the values of these two variables in the Makefile configuration file. As follows:

[root@xuegod63 haproxy-1.4.22] # vim Makefile

[root@xuegod63 haproxy-1.4.22] # make install PREFIX=/usr/local/haproxy

# if you do not modify the value of the PREFIX variable in the Makefile configuration file, you must reassign the PREFIX=/usr/local/haproxy assignment here, otherwise when you execute make install directly, make install will directly read the variable value of PREFIX in the Makefile file.

3) use nobody user to run haproxy

[root@xuegod63 haproxy-1.4.22] # id nobody

Uid=99 (nobody) gid=99 (nobody) groups=99 (nobody)

4) set HAproxy configuration file

[root@xuegod63 haproxy-1.4.22] # ls / usr/local/haproxy/

Doc sbin share

Note: no configuration file is generated. Write one manually later.

[root@xuegod63 ~] # mkdir / usr/local/haproxy/etc

[root@xuegod63 ~] # touch / usr/local/haproxy/etc/haproxy.cfg # manually create a configuration file

Note: interpretation of configuration files:

Global # Global, subject to global definition

By default, defaults # defaults to the local configuration under the global premise. If the local configuration is not said, it defaults to the local configuration, and if the local configuration is defined, it defaults to the local configuration.

Frontend # front end, listening address, listening port, how to deal with it

Backend # back-end servers, which define those servers that actually handle business Realserver.

Listen # A scheme of combining frontend and backend

[root@xuegod63 ~] # vim / usr/local/haproxy/etc/haproxy.cfg # writes the following

Global

Log 127.0.0.1 local0

# log 127.0.0.1 local1 notice

# log loghost local0 info

Maxconn 4096

Chroot / usr/local/haproxy

Uid 99 # running user uid

Gid 99 # user group to which it belongs

Daemon # runs haproxy as a later platform

Nbproc 1 # starts an instance of haproxy. # # the number of worker processes (number of CPU) should be set to the same number as the number of CPU cores in actual work. In this way, you can maximize performance.

Pidfile / usr/local/haproxy/run/haproxy.pid # writes all processes to the pid file

# debug # used when debugging errors

# quiet # quiet

Defaults

Log global

Output direction of the log 127.0.0.1 local3 # log file. The resulting log level is local3. Local1-7 in the system, defined by the user

Mode http # working mode. The category processed adopts http mode by default, and can be configured as tcp for layer 4 message forwarding.

Option httplog # log category, recording http logs

Option httpclose # actively closes the http channel after each request. Haproxy does not support keep-alive, which can simulate the implementation of this mode.

Option dontlognull # does not record empty connections, resulting in logs

Option forwardfor # if the backend server needs to obtain the parameters that the client real ip needs to configure, you can obtain the client ip from Http Header

Option redispatch # forcibly direct to another healthy server when the server corresponding to serverid is down

If retries 2 # 2 connection fails, the server is considered unavailable, mainly through the following check check.

Maxconn 2000 # maximum connections

Balance roundrobin # load balancing algorithm

Stats uri / haproxy-stats # the access address of the haproxy monitoring page # can be accessed through http://localhost:80/haproxy-stats

Contimeout 5000 # connection timeout. In ms milliseconds

Clitimeout 50000 # client connection timeout

Srvtimeout 50000 # server-side connection timeout

Port and hostname on which listen localhost 0.0.0.0 is running

Mode http

Option httpchk GET / index.html # Health Test. # Note that when testing in practice, you should download a page for testing, so this page should be a small page instead of using the first page. Here is to check the page every other second.

Server S1 192.168.1.62 server 80 weight 3 check # backend host IP & tradeoff

Server S2 192.168.1.64 check 80 weight 3 check # backend host IP & tradeoff

# server S3 192.168.148.110 weight 3 check # backend host IP & tradeoff

5) start and stop services

[root@xuegod63 haproxy] # mkdir run

(1) start haproxy

[root@xuegod63 etc] # / usr/local/haproxy/sbin/haproxy-f / usr/local/haproxy/etc/haproxy.cfg

View status:

[root@xuegod63 etc] # ps-axu | grep haproxy

Warning: bad syntax, perhaps a bogus'-'? See / usr/share/doc/procps-3.2.8/FAQ

Nobody 3871 0.0 0.0 12228 1036? Ss 21:53 0:00 / usr/local/haproxy/sbin/haproxy-f / usr/local/haproxy/etc/haproxy.cfg

Root 3879 0.0 103300 852 pts/0 S + 21:53 0:00 grep haproxy

[root@xuegod63 etc] # netstat-antup | grep 80

Tcp 0 0 0.0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0 of the LISTEN 3871/haproxy.

(2) restart haproxy

[root@xuegod63 etc] # / usr/local/haproxy/sbin/haproxy-f / usr/local/haproxy/etc/haproxy.cfg-st `cat / usr/local/haproxy/run/ haproxy.pid`

Check the meaning of the-st parameter:

[root@xuegod63] # / usr/local/haproxy/sbin/haproxy-h

-sf/-st [pid (haproxy current process ID)] * finishes/terminates old pids. Must be last arguments. # complete / terminates (trm.ntreast) terminates the old PID. This parameter must be the last parameter.

(3) stop

[root@xuegod63 etc] # killall haproxy

6) enable log collection of udp 514 in rsyslog.conf

[root@xuegod63 ~] # vim / etc/rsyslog.conf # opens the comment with the following two lines, and does not open the receipt of the log.

# Provides UDP syslog reception

$ModLoad imudp.so

$UDPServerRun 514

As shown in the figure:

58 local7.* / var/log/boot.log # add the following two lines of entries below

Local3.* / var/log/haproxy.log

Local0.* / var/log/haproxy.log

7) restart the rsyslog service

[root@xuegod63 ~] # / etc/init.d/rsyslog restart

2. Configure the backend server: xuegod62

1) configure the web server:

[root@xuegod62 html] # yum install httpd php-y

2) generate test files:

Root@xuegod62 html] # echo 192.168.1.62 > / var/www/html/index.html

3) start the apache server:

[root@xuegod62 html] # service httpd restart

3. Configure the backend server: xuegod64

1) configure the web server:

[root@xuegod64 html] # yum install httpd php-y:

2) generate test files:

Echo 192.168.1.64 > / var/www/html/index.html

3) restart the apache server

[root@xuegod64 html] # service httpd restart

4. Test:

1) View the monitoring page of HAproxy

Http://192.168.1.63/haproxy-stats

2: test: reverse proxy and load balancing

Http://192.168.1.63/

Http://192.168.1.63/

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.