centos7 memcached+magent+keepalived集群

最新推荐文章于 2021-09-25 15:55:15 发布
最新推荐文章于 2021-09-25 15:55:15 发布
阅读量274 收藏
点赞数
文章标签： memcached 操作系统 运维
原文链接：http://www.cnblogs.com/lurenjia1994/p/9519418.html
版权

 

111,222均部署keepalived,magent,memcached

keepalived 111为主机，222为备机

其中，111上magent以本地memcache为主，222为备用

222上magen以本地memcache为主，111为备用

 

 

安装memcached

安装：yum -y install memcached
查看配置：cat /etc/sysconfig/memcached, 通过ip+下图port可远程连接

　　PORT="11211"
　　USER="memcached"
　　MAXCONN="1024"
　　CACHESIZE="64"
　　OPTIONS=""


启动： systemctl start memcached
停止： systemctl stop memcached
重启： systemctl restart memcached

连接memcached测试

cmd命令窗口：telnet 10.0.0.111 11211
(回车)

ERROR
add aaa 0 0 4
1111
STORED
get aaa
VALUE aaa 0 4
1111
END

安装libevent(略，下次装时补充)

安装magent

mkdir /opt/magent
cd magent
wget https://files.cnblogs.com/files/lurenjia1994/magent.tar.gz
tar xzvf magent.tar.gz
make进行安装

可能错误1：

magent.c: 在函数‘writev_list’中:
magent.c:729:17: 错误：‘SSIZE_MAX’未声明(在此函数内第一次使用)
    if (toSend > SSIZE_MAX ||
                 ^
magent.c:729:17: 附注：每个未声明的标识符在其出现的函数内只报告一次
make: *** [magent.o] 错误 1

解决方法：

vi ketama.h

在头部加入以下代码
#ifndef SSIZE_MAX
#define SSIZE_MAX      32767
#endif

可能错误2：

gcc -Wall -g -O2 -I/usr/local/include -m64 -c -o magent.o magent.c
gcc -Wall -g -O2 -I/usr/local/include -m64 -c -o ketama.o ketama.c
gcc -Wall -g -O2 -I/usr/local/include -m64 -o magent magent.o ketama.o /usr/lib64/libevent.a /usr/lib64/libm.a 
gcc: 错误：/usr/lib64/libevent.a：没有那个文件或目录
gcc: 错误：/usr/lib64/libm.a：没有那个文件或目录
make: *** [magent] 错误 1

解决方法：

ln -s /usr/lib64/libm.so /usr/lib64/libm.a
ln -s /usr/lib64/libevent.so /usr/lib64/libevent.a

检查是否安装成功

[root@localhost magent]# cp magent /usr/bin/
[root@localhost magent]# magent
please provide -s "ip:port" argument

memcached agent v0.6 Build-Date: Aug 22 2018 15:40:29
Usage:
  -h this message
  -u uid
  -g gid
  -p port, default is 11211. (0 to disable tcp support)
  -s ip:port, set memcached server ip and port
  -b ip:port, set backup memcached server ip and port
  -l ip, local bind ip address, default is 0.0.0.0
  -n number, set max connections, default is 4096
  -D don't go to background
  -k use ketama key allocation algorithm
  -f file, unix socket path to listen on. default is off
  -i number, set max keep alive connections for one memcached server, default is 20
  -v verbose

 

启动magent

[root@centos7 magent]# magent -u root -n 51200 -l 10.0.0.111 -p 12000 -s 10.0.0.111:11211 -b 10.0.0.222:11211
[root@centos7 magent]# ps -aux|grep magent
root     32007  0.0  0.0  11948   616 ?        Ss   15:47   0:00 magent -u root -n 51200 -l 10.0.0.111 -p 12000 -s 10.0.0.111:11211 -b 10.0.0.222:11211
root     32466  0.0  0.0 112720   972 pts/1    S+   15:48   0:00 grep --color=auto magent

测试magent

1.连接magent节点

现象：通过magent节点可以取到所有主节点的数据

telnet 10.0.0.111 12000

UNSUPPORTED COMMAND
get aaa 前面在测试memcache连接设置的aaa,这里取值成功
VALUE aaa 0 4
1111
END
set b 0 0 4
1234
STORED
2.连接主节点

现象：可以取到所有magent节点存入的数据

ERROR
get aaa
VALUE aaa 0 4
1111
END
get b
VALUE b 0 4
1234
END
set c 0 0 4
cccc
STORED
3.连接备份节点

现象：可以取到所有magent节点存入的数据

ERROR
get aaa
END
get b #只能取到在magent节点设置的值，其他取不到
VALUE b 0 4
1234
END
get c
END
4.关掉主节点的memcache进程

现象：通过magent节点可以取到所有备份节点的数据

[root@centos7 magent]# systemctl stop memcached
[root@centos7 magent]# ps -aux|grep memcached
root     30827  0.0  0.0 112720   972 pts/1    S+   16:05   0:00 grep --color=auto memcached

cmd连接magent节点
telnet 10.0.0.111 12000

UNSUPPORTED COMMAND
get aaa
END
get b
VALUE b 0 4
1234
END
get c
END
5.再开启主节点memcached

现象：取不到前面设置的所有值，因为重启以后，主节点数据全部清空，虽然备份节点有数据，但是主节点在备份节点不会生效

UNSUPPORTED COMMAND
get a
END
get aaa
END
get b
END
get c
END

安装keepalived(当10.0.0.111上的magent挂掉时，自动切换到10.0.0.222的magent)

yum install keepalived

修改keepalived配置

本文配置为在这个基础上添加的配置，请忽略多余部分keepalive+nginx 热备跟负载均衡

keepalived配置

! Configuration File for keepalived

global_defs {
   notification_email {
     #acassen@firewall.loc
     #failover@firewall.loc
     #sysadmin@firewall.loc
   }
   #notification_email_from Alexandre.Cassen@firewall.loc
   #smtp_server 192.168.200.1
   #smtp_connect_timeout 30
   router_id LVS_DEVEL
   vrrp_skip_check_adv_addr
   #vrrp_strict
   vrrp_garp_interval 0
   vrrp_gna_interval 0
}

vrrp_script chk_nginx {         
    script "/etc/keepalived/chk_nginx.sh"   
    interval 2             
}

vrrp_script chk_magent {         
    script "/etc/keepalived/chk_magent.sh"   
    interval 2             
}

vrrp_instance VI_1 {
    state MASTER
    interface ens192
    virtual_router_id 51
    priority 50
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        10.0.0.233
    }
    notify_master "/usr/bin/python2.7 /etc/keepalived/send.py 1499418300@qq.com 报！111成为主机！ 报！111成为主机！"
    notify_fault "/usr/bin/python2.7 /etc/keepalived/send.py 1499418300@qq.com 报！111已挂！ 10.0.0.111故障！请尽快修复！"
    track_script {
      chk_nginx                 
    }
}

vrrp_instance VI_2 {
    state MASTER
    interface ens192
    virtual_router_id 52
    priority 50
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        10.0.0.234
    }
    track_script {
      chk_magent                 
    }    
}

其中/etc/keepalived目录下的chk_magent.sh

#!/bin/bash
run=`ps -C magent --no-header | wc -l`
if [ $run -eq 0 ]; then
    magent -u root -n 51200 -l 10.0.0.234 -p 12000 -s 10.0.0.111:11211 -b 10.0.0.222:11211
    sleep 3
    if [ `ps -C magent --no-header | wc -l` -eq 0 ]; then
        systemctl stop keepalived
    fi
fi

遇到问题1

绑定不了虚拟vip排查，没有发现虚拟ip 10.0.0.234

只有vrid 51的组播，没有52的组播

[root@centos7 keepalived]# tcpdump -nn -c 20 -i any host 224.0.0.18
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
10:46:43.008689 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:44.009046 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:45.009174 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:46.009534 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:47.009703 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:48.010830 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:49.010960 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:50.012050 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:51.012178 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:52.012727 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:53.012828 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:54.013334 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:55.013481 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:56.013858 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:57.014023 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:58.014457 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:46:59.014604 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:47:00.015002 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:47:01.015815 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
10:47:02.016914 IP 10.0.0.111 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 50, authtype simple, intvl 1s, length 20
20 packets captured
20 packets received by filter
0 packets dropped by kernel
View Code

查看日志：cat /var/log/message

似乎是因为脚本导致vip2启动失败

Aug 23 11:17:52 centos7 Keepalived_vrrp[8399]: Sending gratuitous ARP on ens192 for 10.0.0.233
Aug 23 11:17:52 centos7 Keepalived_vrrp[8399]: Sending gratuitous ARP on ens192 for 10.0.0.233
Aug 23 11:17:52 centos7 Keepalived_vrrp[8399]: Sending gratuitous ARP on ens192 for 10.0.0.233
Aug 23 11:17:52 centos7 Keepalived_vrrp[8399]: Sending gratuitous ARP on ens192 for 10.0.0.233
Aug 23 11:17:53 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:17:55 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:17:57 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:17:59 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:01 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:03 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:05 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:07 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:09 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:11 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:13 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:15 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:17 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:19 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:21 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:23 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:25 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:27 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:29 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:31 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 11:18:33 centos7 Keepalived_vrrp[8399]: /etc/keepalived/chk_magent.sh exited due to signal 15
View Code

难道他是先运行脚本，再开启vip2?

于是把脚本中的10.0.0.234改成10.0.0.111，再重启keepalived，再查看ip，发现已经有10.0.0.234了

[root@centos7 keepalived]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:0c:29:c8:03:3f brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.111/24 brd 10.0.0.255 scope global noprefixroute ens192
       valid_lft forever preferred_lft forever
    inet 10.0.0.233/32 scope global ens192
       valid_lft forever preferred_lft forever
    inet 10.0.0.234/32 scope global ens192
       valid_lft forever preferred_lft forever
    inet6 fe80::7e90:403b:465:db6c/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:70:99:88 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:70:99:88 brd ff:ff:ff:ff:ff:ff
View Code

于是在vip1中设置两个虚拟ip：10.0.0.233，10.0.0.234，vip2中不设置虚拟ip，检测脚本启动magent时绑定10.0.0.234，经测试10.0.0.111上部署成功

遇到问题2

10.0.0.222启动keepalived时，magent似乎启动失败

排查：

1.关掉10.0.0.111上的keepalived

2.给111上的keepalived.conf跟chk_magent.sh覆盖掉222对应文件

3.启动

systemctl start keepalived

4.检查地址

[root@localhost keepalived]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:0c:29:59:17:90 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.222/24 brd 10.0.0.255 scope global noprefixroute ens192
       valid_lft forever preferred_lft forever
    inet 10.0.0.233/32 scope global ens192
       valid_lft forever preferred_lft forever
    inet 10.0.0.234/32 scope global ens192
       valid_lft forever preferred_lft forever
    inet6 fe80::5e69:554d:d28e:dbb5/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:59:38:b4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:59:38:b4 brd ff:ff:ff:ff:ff:ff
View Code

5.检查magent服务

[root@localhost keepalived]# ps -aux|grep magent
root     23443  0.0  0.0 115296  1476 ?        S    15:21   0:00 /bin/bash /etc/keepalived/chk_magent.sh
root     23457  0.0  0.0 112720   968 pts/0    S+   15:21   0:00 grep --color=auto magent


通过./chk_magent.sh可以正确启动
正确启动应该是这样
[root@localhost keepalived]# ./chk_magent.sh 
[root@localhost keepalived]# ps -aux|grep magent
root     24142  0.0  0.0  11948   612 ?        Ss   15:22   0:00 magent -u root -n 51200 -l 10.0.0.234 -p 12000 -s 10.0.0.111:11211 -b 10.0.0.222:11211
root     24185  0.0  0.0 112720   972 pts/0    S+   15:22   0:00 grep --color=auto magent
View Code

6.检查系统日志

Aug 23 15:22:19 localhost Keepalived_vrrp[22337]: /etc/keepalived/chk_magent.sh exited due to signal 15
Aug 23 15:22:19 localhost setroubleshoot: failed to retrieve rpm info for /usr/bin/magent
Aug 23 15:22:19 localhost setroubleshoot: SELinux is preventing /usr/bin/magent from name_bind access on the tcp_socket port 12000. For complete SELinux messages run: sealert -l 7a3a5f2e-5328-4dd4-88d6-bdefea289425
Aug 23 15:22:19 localhost python: SELinux is preventing /usr/bin/magent from name_bind access on the tcp_socket port 12000.#012#012*****  Plugin bind_ports (92.2 confidence) suggests   ************************#012


脚本启动失败了，似乎是防火墙
View Code

7.关掉SELinux

[root@localhost keepalived]# setenforce 0
[root@localhost keepalived]# getenforce
Permissive
View Code

8.重启keepalived

[root@localhost keepalived]# systemctl stop keepalived
[root@localhost keepalived]# pkill magent
[root@localhost keepalived]# ps -aux|grep magent
root     27598  0.0  0.0 112720   972 pts/0    S+   15:32   0:00 grep --color=auto magent
[root@localhost keepalived]# systemctl start keepalived
[root@localhost keepalived]# ps -aux|grep magent
root     27647  0.0  0.0  11948   616 ?        Ss   15:32   0:00 magent -u root -n 51200 -l 10.0.0.234 -p 12000 -s 10.0.0.111:11211 -b 10.0.0.222:11211
root     27699  0.0  0.0 112720   972 pts/0    S+   15:32   0:00 grep --color=auto magent

果然是防火墙！
View Code

9.SELinux放出magent

比较复杂，以后再补
View Code

 

 

 

 

最终配置

 10.0.0.111上的keepalived.conf

! Configuration File for keepalived

global_defs {
   notification_email {
     #acassen@firewall.loc
     #failover@firewall.loc
     #sysadmin@firewall.loc
   }
   #notification_email_from Alexandre.Cassen@firewall.loc
   #smtp_server 192.168.200.1
   #smtp_connect_timeout 30
   router_id LVS_DEVEL
   vrrp_skip_check_adv_addr
   #vrrp_strict
   vrrp_garp_interval 0
   vrrp_gna_interval 0
}

vrrp_script chk_nginx {         
    script "/etc/keepalived/chk_nginx.sh"   
    interval 2             
}

vrrp_script chk_magent {         
    script "/etc/keepalived/chk_magent.sh"   
    interval 2             
}

vrrp_instance VI_1 {
    state MASTER
    interface ens192
    virtual_router_id 51
    priority 50
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        10.0.0.233
        10.0.0.234
    }
    notify_master "/usr/bin/python2.7 /etc/keepalived/send.py 1499418300@qq.com 报！111成为主机！ 报！111成为主机！"
    notify_fault "/usr/bin/python2.7 /etc/keepalived/send.py 1499418300@qq.com 报！111已挂！ 10.0.0.111故障！请尽快修复！"
    track_script {
      chk_nginx                 
    }
}

vrrp_instance VI_2 {
    state MASTER
    interface ens192
    virtual_router_id 52
    priority 50
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        # 10.0.0.234
    }
    track_script {
      chk_magent                 
    }    
}
View Code

10.0.0.111上的chk_magent.sh

#!/bin/bash
run=`ps -C magent --no-header | wc -l`
if [ $run -eq 0 ]; then
    magent -u root -n 51200 -l 10.0.0.234 -p 12000 -s 10.0.0.111:11211 -b 10.0.0.222:11211
    sleep 3
    if [ `ps -C magent --no-header | wc -l` -eq 0 ]; then
        systemctl stop keepalived
    fi
fi
View Code

10.0.0.222上的keepalived.conf

! Configuration File for keepalived

global_defs {
   notification_email {
     #acassen@firewall.loc
     #failover@firewall.loc
     #sysadmin@firewall.loc
   }
   #notification_email_from Alexandre.Cassen@firewall.loc
   #smtp_server 192.168.200.1
   #smtp_connect_timeout 30
   router_id LVS_DEVEL
   vrrp_skip_check_adv_addr
   #vrrp_strict
   vrrp_garp_interval 0
   vrrp_gna_interval 0
}

vrrp_script chk_nginx {         
    script "/etc/keepalived/chk_nginx.sh"   
    interval 2             
}

vrrp_script chk_magent {         
    script "/etc/keepalived/chk_magent.sh"   
    interval 2             
}

vrrp_instance VI_1 {
    state BACKUP
    interface ens192
    virtual_router_id 51
    priority 30
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        10.0.0.233
        10.0.0.234
    }
    notify_master "/usr/bin/python2.7 /etc/keepalived/send.py 1499418300@qq.com 报！222成为主机！ 报！222成为主机！"
    notify_fault "/usr/bin/python2.7 /etc/keepalived/send.py 1499418300@qq.com 报！222已挂！ 10.0.0.222故障！请尽快修复！"
    track_script {
      chk_nginx                 
    }    
}

vrrp_instance VI_2 {
    state BACKUP
    interface ens192
    virtual_router_id 52
    priority 30
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        # 10.0.0.234
    }
    track_script {
      chk_magent                 
    }    
}
View Code

10.0.0.222上的chk_magent.sh

#!/bin/bash
run=`ps -C magent --no-header | wc -l`
if [ $run -eq 0 ]; then
    magent -u root -n 51200 -l 10.0.0.234 -p 12000 -s 10.0.0.222:11211 -b 10.0.0.111:11211
    sleep 3
    if [ `ps -C magent --no-header | wc -l` -eq 0 ]; then
        systemctl stop keepalived
    fi
fi
View Code

 

 

 

参考文档

memcached+magent+keepalived实现高可用群集

Memcached之代理服务magent(8)

转载于:https://www.cnblogs.com/lurenjia1994/p/9519418.html

weixin_30753873
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Centos 7搭建memcached
Butterfly0011的博客
03-14 215
由于memcached依赖于libevent，因此需要安装libevent。由于linux系统可能默认已经安装libevent，执行命令： rpm -qa|grep libevent 查看系统是否带有该安装软件，如果有执行命令: 安装libevent命令 tar -zxvf libevent-2.0.21-stable.tar.gz cd libevent-2.0.21-stable ./...
centos7 安装memcached以及扩展
lijiang的博客
09-09 1154
安装memcached yum install memcached 启动 memcached /usr/bin/memcached -d -m 64M -u root -l 192.168.1.118 -p 11211 -c 256 -P /tmp/memcached.pid 查看进程 ps  -aux |grep memcached 使用memcached yu
部署Memcached+magent+keepalived高可用集群
weixin_33843409的博客
07-25 117
Memcached+magent+keepalived高可用集群 magent是一款开源的代理服务软件，我们可以通过他来实现缓存数据的同步，当然这里说的同步不是说memcached之间就能互相通讯了， 而magent可以同时连接多个memcached节点， 通过magent绑定的VIP从客户端登录memcached写入数据，其他节点的memcached数据也会同步。  案例环境 主机...
使用Magent搭建Memcached分布式集群
独醉的博客
04-24 400
搭建memcached分布式集群安装Memcached安装libevent库安装 MemcachedMemcached 运行安装Magent下载Magent安装Magent代理Memcache 安装Memcached 安装libevent库 yum install libevent libevent-devel 安装 Memcached yum install memcached Memc...
memcached+magent的集群部署详细过程
weixin_30399871的博客
06-29 143
问题描述 Memcached在实现分布集群部署时，Memcached服务端的之间是没有通讯的，服务端是伪分布式，实现分布式是由客户端实现的，客户端实现了分布式算法把数据保存到不同的Memcached服务端。 memcached对容错不做处理的，也就是说当Memcached服务端挂掉或者Memcached重启复活后是无数据的，这对高并发的大型系统是没办法接受的。我们在集群的情况下，要做到负载...
CentOS7 nginx+keepalived 离线安装包
12-04
本文将详细介绍如何在CentOS7系统上，离线环境下安装nginx和keepalived，以实现主从热备负载均衡反向代理功能。 首先，我们关注的两个主要组件是`nginx`和`keepalived`。`nginx`是一款高性能的HTTP和反向代理服务器...
mysql+mycat+keepalived+haproxy集群(生产环境实测).doc
08-10
总结来说，这个集群环境通过MySQL提供数据库服务，Mycat进行数据分片和负载均衡，Keepalived确保主从切换的高可用性，而HAProxy则进一步增强了对外服务的负载均衡能力。这样的组合可以有效提升系统的稳定性和处理...
centos7.5 LVS +keepalived安装包.zip
09-27
在IT行业中，LVS（Linux Virtual Server）和Keepalived是构建高可用性集群的关键组件。这个名为"centos7.5 LVS +keepalived安装包.zip"的压缩文件显然是为CentOS 7.5操作系统设计的，用于在完全离线的环境中安装和...
centos6.5 LVS +keepalived安装包.zip
09-27
在IT行业中，Linux虚拟服务器（LVS）与Keepalived是构建高可用性集群的关键组件。本教程将针对CentOS 6.5操作系统，详细解释如何离线安装LVS和Keepalived，以及如何利用提供的压缩包进行安装。 首先，LVS（Linux ...
centos7搭建LVS+keepalived.txt
08-08
centos7搭建LVS+keepalived
nginx_check.sh
04-30
lvs+keepalived+nginx整合时，所需要的配置文件及其对应的心跳脚本
教你用Magent实现Memcached集群
weixin_43226231的博客
05-09 374
Magent 是一款开源的 Memcached 代理服务器软件，使用它可以搭建高可用性的集群应用的 Memcached 服务 ，备份 Memcached 数据 尽管 Memcached 服务挂掉，前端也能获取到数据，客户端先连到 Magent 代理服务器 ，然后Magent 代理服务器 在可以连接多台 Memcached 服务器，然后可以进行数据的保存和备份数据。这样数据就不会丢失，保存了数据完整性。 安装Magent 1）下载安装 cd /usr/local mkdir magent wget
本地yum源搭建及failed to retrieve解决
weixin_33774615的博客
07-12 2032
第1章 yum是什么YUM（Yellow dog Updater Modified）为多个Linux发行版的软件包管理器，例如Redhat RHEL,CentOS&Fedoro。YUM主要用于自动安装、升级rpm软件包，它能自动查找并解决rpm包之间的依赖关系。YUM自动下载rpm包并安装。类似某软件的一键安装。1.1 yum源是什么？要成功的使用YUM工具安装更新软...
keepalived 常见问题及解决方法
热门推荐
lixingdefengzi的专栏
06-29 1万+
1、虚拟 ip 没有生成。 /var/log/message 日志 Jun 29 10:43:11 cloud-config2 Keepalived_vrrp[2442]: ip address associated with VRID not present in received packet : 172.21.15.64 Jun 29 10:43:11 cloud-config2 Ke
项目管理——Nginx
LiLi的博客
09-25 835
Nginx 简介 什么是反向代理 安装 Nginx Nginx 的使用
keepalived 错误提示（VRID not present）
weixin_33739646的博客
11-20 741
keepalived ip address associated with VRID not present in received packet原因5913May1615:26:04ha02Keepalived_vrrp:ipaddressassociatedwithVRIDnotpresentinreceivedpacket:192.16...
CentOS 7.x安装部署Memcached服务器的详细方法
Luke
05-24 642
操作系统：CentOS 7.x 64位实现目的：安装部署Memcached服务器一、防火墙设置CentOS 7.x默认使用的是firewall作为防火墙，这里改为iptables防火墙。1、关闭firewall：systemctl stop firewalld.service #停止firewallsystemctl disable firewalld.service #禁止firewall开机启...
keepalived+nginx遇到的几个问题
harryxxxxx的博客
07-18 5991
nginx masterIP 192.168.119.120 nginx backupIP 192.168.119.121 VIP 192.168.119.130 MASTER ! Configuration File for keepalived global_defs { router_id LVS1 ...
Keepalived实现LVS（DR模式）+自动后端健康检测
lvshaorong的博客
07-27 6685
上一篇博客《Keepalived实现NAT+LVS+后端健康检测》简单介绍了NAT模式的LVS搭建步骤，下面介绍一下使用更普遍、网络结构更简单的DR模式搭建方法。 不同与NAT模式，DR模式不需要跨两个网段，负载均衡服务器和真实Web服务器还有客户端都可以放在同一个网段里，对网络的复杂性要求降低，而且有一个好处是负载量会提高，因为数据流量不需要通过负载均衡器进行路由，使负载均衡器不会产生瓶颈。但...
Centos7搭建lvs+keepalived+nginx+tomcat集群实战
"本文档描述了如何在CentOS 7环境下构建一个基于lvs+keepalived+nginx+tomcat的高可用性集群。实验环境包括多台服务器，每台服务器有不同的角色，如Tomcat应用服务器、Nginx反向代理服务器、LVS调度器以及后端的...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值