作者:夜間獨行的浪子
鏈接:https://www.cnblogs.com/wxzhe/p/11459777.html
兩種模式:
第一種:數(shù)據(jù)庫宕機觸發(fā)VIP漂移的高可用使用淤井。
第二種:haproxy宕機出發(fā)VIP漂移的高可用榨咐。
這兩種模式的底層數(shù)據(jù)庫均為雙主模式或者MGR的多主模式笆制,mariadb的galera模式,percona的pxc模式;也就是底層的數(shù)據(jù)庫每一個都可寫荔茬。
在雙主的模式下霞揉,如果添加了haproxy這一層,那么就可以實現(xiàn)了數(shù)據(jù)庫讀寫的負載均衡翎苫,VIP隨著haproxy的狀態(tài)而漂移权埠,即上面提到的第一種情況。
如果沒有加入haproxy這一層煎谍,那么就只實現(xiàn)了雙主模式數(shù)據(jù)庫的高可用攘蔽,即一個數(shù)據(jù)庫宕機,則VIP漂移呐粘,VIP隨著數(shù)據(jù)庫的狀態(tài)而漂移满俗,即上面提到的第二種情況。
下面分別來說明這兩種情況的使用作岖。
雙主模式的數(shù)據(jù)庫:10.9.8.201和10.9.8.223
VIP地址:10.9.8.120
【因服務(wù)器資源限制唆垃,因此只使用此兩臺服務(wù)器】
數(shù)據(jù)庫宕機觸發(fā)VIP漂移
已經(jīng)配置好的雙主模式數(shù)據(jù)庫。然后在兩個服務(wù)器上分別下載keepalive軟件痘儡,直接yum安裝即可辕万。
keepalived的配置文件有很長,原因是里面有l(wèi)vs的配置,這里只需要部分配置即可渐尿,如下:
[root@test1 keepalived]# vim /etc/keepalived/keepalived.conf
! Configuration File for keepalived
global_defs {
router_id LVS_DB2
}
vrrp_script check_haproxy {
script "/etc/keepalived/check_mysql.sh"
interval 3
weight -5
}
vrrp_instance VI_1 {
state MASTER
interface ens33
virtual_router_id 51
priority 100
advert_int 1
authentication {
auth_type PASS
auth_pass 1111
}
virtual_ipaddress {
10.9.8.120 dev ens33
}
track_script {
check_haproxy
}
}
檢測腳本內(nèi)容如下:腳本內(nèi)容很簡單醉途,就是檢查mysql進程是否存在,若是不存在砖茸,則停止當前的keepalive隘擎,讓其VIP進行漂移×购唬【要給檢測腳本加上可執(zhí)行的權(quán)限】
#!/bin/bash
if [ $(ps -C mysqld --no-header | wc -l) -eq 0 ]; then
service keepalived stop
fi
上面就是master的配置货葬,做為backup的keepalived的配置和上面基本一樣,只需要更改router_id劲够,state震桶,priority三個值即可。state值的說明再沧,主和備keepalived的state的值均可以設(shè)置為BACKUP尼夺,這樣的話,先啟動的服務(wù)器即為主炒瘸,當發(fā)生VIP漂移后淤堵,原來的主啟動后VIP不會再發(fā)生漂移,可以減少網(wǎng)絡(luò)抖動的影響顷扩。
state值的說明拐邪,主和備keepalived的state的值均可以設(shè)置為BACKUP,這樣的話隘截,先啟動的服務(wù)器即為主扎阶,當發(fā)生VIP漂移后,原來的主啟動后VIP不會再發(fā)生漂移婶芭,可以減少網(wǎng)絡(luò)抖動的影響东臀。
測試:
[root@test1 keepalived]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:0c:29:01:9c:98 brd ff:ff:ff:ff:ff:ff
inet 10.9.8.201/22 brd 10.9.11.255 scope global ens33
valid_lft forever preferred_lft forever
inet 10.9.8.120/32 scope global ens33
valid_lft forever preferred_lft forever
inet6 fe80::744a:3948:cdf2:1976/64 scope link
valid_lft forever preferred_lft forever
[root@test1 keepalived]# ps uax |grep mysql
root 60710 0.0 0.0 11764 1632 pts/0 S 15:21 0:00 /bin/sh /usr/local/mysql/bin/mysqld_safe --datadir=/data/mysql/data --pid-file=/data/mysql/data/test1.pid
mysql 62092 0.0 16.5 2190032 309408 pts/0 Sl 15:21 0:01 /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/data/mysql/data --plugin-dir=/usr/local/mysql/lib/plugin --user=mysql --log-error=/data/mysql/log/error.log --open-files-limit=65535 --pid-file=/data/mysql/data/test1.pid --socket=/data/mysql/run/mysql.sock --port=3306
root 63704 0.0 0.0 112648 960 pts/0 R+ 16:00 0:00 grep --color=auto mysql
[root@test1 keepalived]#
主上面的VIP存在以及mysql服務(wù)存在。停掉主上面的mysql服務(wù)犀农,查看VIP是否漂移惰赋。【主上的VIP已經(jīng)不存在】
[root@test1 keepalived]# service mysqld stop
Shutting down MySQL........... SUCCESS!
[root@test1 keepalived]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:0c:29:01:9c:98 brd ff:ff:ff:ff:ff:ff
inet 10.9.8.201/22 brd 10.9.11.255 scope global ens33
valid_lft forever preferred_lft forever
inet6 fe80::744a:3948:cdf2:1976/64 scope link
valid_lft forever preferred_lft forever
[root@test1 keepalived]# ps aux |grep mysql
root 63933 0.0 0.0 112648 956 pts/0 R+ 16:01 0:00 grep --color=auto mysql
[root@test1 keepalived]#
在back上面查看VIP是否存在:【可以看到VIP已經(jīng)漂移到BACKUP上面】
[root@monitor keepalived]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:0c:29:7c:ae:10 brd ff:ff:ff:ff:ff:ff
inet 10.9.8.223/22 brd 10.9.11.255 scope global ens33
valid_lft forever preferred_lft forever
inet 10.9.8.120/32 scope global ens33
valid_lft forever preferred_lft forever
inet6 fe80::d4e4:4f75:1be6:2134/64 scope link
valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
link/ether 02:42:25:78:a0:39 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
[root@monitor keepalived]#
上面的實例中VIP隨著數(shù)據(jù)庫的狀態(tài)而漂移呵哨。
在這個架構(gòu)下赁濒,其實就是在上面mysql+keepalived的架構(gòu)中插入一層,使用haproxy做負載均衡孟害。
在兩臺機器上分別安裝haproxy拒炎,直接yum安裝即可,haproxy的配置很簡單挨务,就是做一個負載均衡击你。
配置很簡單玉组,haproxy的兩個服務(wù)器都是用同樣的配置」【需要說明球切,因為后面訪問的是mysql,因此需要使用四層負載均衡绒障,mode需要選擇tcp】
#---------------------------------------------------------------------
# Example configuration for a possible web application. See the
# full configuration options online.
#
# http://haproxy.1wt.eu/download/1.4/doc/configuration.txt
#
#---------------------------------------------------------------------
#---------------------------------------------------------------------
# Global settings
#---------------------------------------------------------------------
global
# to have these messages end up in /var/log/haproxy.log you will
# need to:
#
# 1) configure syslog to accept network log events. This is done
# by adding the '-r' option to the SYSLOGD_OPTIONS in
# /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
# /etc/sysconfig/syslog
#
# local2.* /var/log/haproxy.log
#
log 127.0.0.1 local2
chroot /var/lib/haproxy
pidfile /var/run/haproxy.pid
maxconn 4000
user haproxy
group haproxy
daemon
# turn on stats unix socket
stats socket /var/lib/haproxy/stats
#---------------------------------------------------------------------
# common defaults that all the 'listen' and 'backend' sections will
# use if not designated in their block
#---------------------------------------------------------------------
defaults
mode http
log global
option httplog
option dontlognull
option http-server-close
option forwardfor except 127.0.0.0/8
option redispatch
retries 3
timeout http-request 10s
timeout queue 1m
timeout connect 10s
timeout client 1m
timeout server 1m
timeout http-keep-alive 10s
timeout check 10s
maxconn 3000
#---------------------------------------------------------------------
# main frontend which proxys to the backends
#---------------------------------------------------------------------
frontend mysql
mode tcp
bind *:6039
default_backend back_mysql
#---------------------------------------------------------------------
# static backend for serving up images, stylesheets and such
#---------------------------------------------------------------------
backend back_mysql
mode tcp
balance roundrobin
server db1 10.9.8.201:3306 check
server db2 10.9.8.223:3306 check
然后修改keepalived的檢測腳本,上面的模式檢查的是mysql的狀態(tài)捍歪,這一次檢查的是haproxy的狀態(tài)户辱。
! Configuration File for keepalived
global_defs {
router_id LVS_DB2
}
vrrp_script check_haproxy {
script "/etc/keepalived/check_haproxy_status.sh"
interval 3
weight -5
}
vrrp_instance VI_1 {
state BACKUP
interface ens33
virtual_router_id 51
priority 9
advert_int 1
authentication {
auth_type PASS
auth_pass 1111
}
virtual_ipaddress {
10.9.8.120 dev ens33
}
track_script {
check_haproxy
}
}
腳本內(nèi)容如下:
#!/bin/bash
if [ $(ps -C haproxy --no-header | wc -l) -eq 0 ];then
sudo service keepalived stop
fi
修改完之后重啟keepalive即可。
加入了haproxy需要說明的是糙臼,在連接數(shù)據(jù)庫的時候需要使用VIP+haproxy_PORT庐镐,上面我們配置haproxy監(jiān)聽了6039端口,那么連接的時候就是用VIP+6039端口变逃。