mycat+haproxy服務與高可用（3）

1.服務器

192.168.9.34 haproxy --->haproxy
192.168.9.37 haproxy-keeplived --->haproxy
192.168.9.35 service1 --->nginx
192.168.9.36 service2 --->nginx+tomcat

2.進行web進行haproxy負載均衡

#---------------------------------------------------------------------
# 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

#---------------------------------------------------------------------
# listen page
#---------------------------------------------------------------------
listen stats
    mode http
    bind 0.0.0.0:1080
    stats enable
    stats hide-version
    stats uri     /listen-page
    stats realm   welcome login\ listen-page
    stats auth    admin:000000
    stats admin if TRUE

#---------------------------------------------------------------------
# main frontend which proxys to the backends
#---------------------------------------------------------------------
frontend  main *:80                      #haproxy的監聽端口
    acl url_static       path_beg       -i /static /images /javascript /stylesheets
    acl url_static       path_end       -i .jpg .gif .png .css .js

    use_backend static          if url_static
    default_backend             app

#---------------------------------------------------------------------
# static backend for serving up images, stylesheets and such
#---------------------------------------------------------------------
backend static
    balance     roundrobin
    option httpchk GET /index.html
    server      static1 192.168.9.35:80 check port 80 inter 5s rise 2 fall 3

#---------------------------------------------------------------------
# round robin balancing between the various backends
#---------------------------------------------------------------------
backend app
    balance     roundrobin
    server      app1 192.168.9.35 check port 80 inter 5s rise 2 fall 3
    server      app2 192.168.9.36 check port 80 inter 5s rise 2 fall 3

3.其他應用的後端健康檢查與負載均衡
3.1摘錄

3.2摘錄

3.3摘錄


4.haproxy的keepalived高可用
4.1安裝keeplived

[root@haproxy ~]# yum -y install keepalived

4.2修改keeplived 的配置文件，配置自己需要的配置
4.2.1修改主從的配置文件

[root@haproxy ~]# vim /etc/keepalived/keepalived.conf 

! Configuration File for keepalived
global_defs {
   router_id master                              #此處唯一
}
vrrp_script checkhaproxy {
        script "/usr/local/bin/chk_haproxy.bash"
        weight -20
        interval 3
}
vrrp_instance VI_1 {
    state MASTER                             #此處爲MASTER或BACKUP
    interface ens33
    virtual_router_id 51                      #此處爲虛擬組，要相同表示一個組
    priority 100                                   #此處爲優先級，MASTR要大
    advert_int 1                                  #廣播時間間隔
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    track_script {
            checkhaproxy
    }
    virtual_ipaddress {
        192.168.9.202/24
    }
}

[root@haproxy-keeplived ~]# vim /etc/keepalived/keepalived.conf 

! Configuration File for keepalived
global_defs {
   router_id slave
}
vrrp_script checkhaproxy {
        script "/usr/local/bin/chk_haproxy.bash"
        weight -20
        interval 3
}
vrrp_instance VI_1 {
    state BACKUP
    interface ens33
    virtual_router_id 51
    priority 90
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    track_script {
        checkhaproxy
    }
    virtual_ipaddress {
        192.168.9.202/24
    }
}

track_script 中調用 checkhaproxy

checkhaproxy 的意思是：

每3秒種執行一次 /usr/local/keepalived/script/chk_haproxy.bash 腳本 如果反饋結果是 0，就保持原優先級 priority ，如果是 1 ，就將優先級降低 20，也就是檢查到 haproxy 狀態異常後，就降級，以便讓另一臺服務器的keepalived進程可以搶到IP

爲了避免網絡的不穩定還可以加入 fall N (代表連續N次檢查失敗纔算異常) 和 rise N (代表連續N次檢查成功就算正常)

---

Tip: keepalived 相互之間的通訊要使用到組播，如果沒打開，會出現幾個實例同時搶佔着IP的情況，打開方式是在iptables中加入 -A INPUT -d 224.0.0.18 -j ACCEPT，然後重載iptables配置（這個ip可以更改）

---

如果同一個局域網內存在多組Keepalived服務器對，就會造成IP多播地址衝突問題，導致接管錯亂，不同組的Keepalived都會使用默認的224.0.0.18作爲多播地址。此時的解決辦法是，在同組的Keepalived服務器所有的配置文件裏指定獨一無二的多播地址，配置如下：

global_defs {
router_id LVS_19
vrrp_mcast_group4 224.0.0.19 #這個就是指定多播地址的配置
}

       ＃組播組用於IPv4 VRRP通告
       ＃（默認值：224.0.0.18）
       vrrp_mcast_group4 224.0.0.18

       #Multicast Group用於IPv6 VRRP通告
       ＃（默認值：ff02 :: 12）
       vrrp_mcast_group6 ff02 :: 12

4.2.2檢查狀態腳本
[root@haproxy ~]# vim /usr/local/bin/chk_haproxy.bash

#!/bin/bash
count=`ps aux | grep -v grep | grep haproxy.cfg | wc -l`
if [ $count -gt 0 ]; then
    exit 0
else
    pkill keepalived
    exit 1
fi

增加執行權限
[root@haproxy ~]# chmod +x /usr/local/bin/chk_haproxy.bash

5.裂腦檢查腳本
[root@lb02 scripts]# cat check_split_brain.sh

#!/bin/bash
lb01_vip=192.168.0.240
lb01_ip=192.168.0.221
while true
do
ping -c 2 -W 3 $lb01_ip &>/dev/null
if [ $? -eq 0 -a `ip a | grep "$lb01_vip" | wc -l` -eq 1 ];then
echo "ha is split brain.warning."
else
echo "ha is OK"
fi
sleep 5
done

可以將此腳本整合到Nagios或Zabbix監控服務裏，進行監控報警。

6: 配置日誌

keepalived 默認將日誌輸出到系統日誌/var/log/messages中，因爲系統日誌很多，查詢問題時相對麻煩。
我們可以將 keepalived 的日誌單獨拿出來，這需要修改日誌輸出路徑。

修改 Keepalived 配置

[root@haproxy ~]# vim /etc/sysconfig/keepalived
更改如下：

即把 KEEPALIVED_OPTIONS=”-D” 修改爲KEEPALIVED_OPTIONS=”-D -d -S 0”，其中 -S 指定 syslog 的 facility

修改日誌rsyslog.con配置
[root@haproxy ~]# vim /etc/rsyslog.conf

mofa模仿上面添加
local0.* /var/log/keepalived.log

---

重啓日誌記錄服務
[root@haproxy ~]# systemctl restart rsyslog
重啓 keepalived
[root@haproxy ~]# systemctl restart keepalived

此時，可以從 /var/log/keepalived.log 查看日誌了。