MySQL5.7 MM+Keepalive测试验证

最新推荐文章于 2022-04-08 08:13:37 发布
最新推荐文章于 2022-04-08 08:13:37 发布
阅读量566 收藏 3
点赞数
分类专栏： MySQL 文章标签： linux mysql
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/zz_aiytag/article/details/107386698
版权

文章目录

环境

软件版本
centos7.4-1708
mysql5.7.29
keepalived2.0.10
主机名IP
node1192.168.183.102mysql1
node2192.168.183.103mysql2
vip192.168.183.200虚拟IP

MySQL安装

安装过程：
https://blog.csdn.net/zz_aiytag/article/details/89917832

两个节点分别安装，过程一样。
MySQL默认安装在/var/lib/mysql目录下
配置文件为/etc/my.cnf，默认配置如下

[mysqld]
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

设置互为主备

修改配置

node1:

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
symbolic-links=0
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

# 开启mysql binlog功能
log-bin=mysql-bin 
# binlog记录内容的方式
binlog_format=mixed
# 服务的唯一编号(另一个写2)
server-id=1
# 字符集编码
character-set-server=utf8
# 自增长字段从哪个数开始(另一个写2)
auto_increment_offset=1
# 自增长字段每次递增的量
auto_increment_increment=2
# 以下参数根据需要来设置
# logs-slave-updates
# expire_logs_days = 10 默认为0
# max_binlog_size = 100M 默认1G
# sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
# log_bin_trust_function_creators=0 默认为0
[client]
# 字符集编码
default-character-set=utf8

node2与node1保持一致，除和server-id和auto_increment_offset属性。

修改完配置后，两节点均重启mysql服务。

[root@worker opt]# systemctl restart mysqld

互相授权配置

node1做主，node2做从的情况
先在node1上操作：

# 自动创建用户
mysql> grant replication slave,replication client on *.* to 'sync'@'%' identified by 'bigdata';
Query OK, 0 rows affected, 1 warning (0.00 sec)

# 查看node1的master状态
mysql> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000001 |      454 |              |                  |                   |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)

在node2上操作：

mysql> change master to master_host='192.168.183.103',master_user='sync',master_password='bigdata',master_log_file='mysql-bin.000001',master_log_pos=454;
Query OK, 0 rows affected, 2 warnings (0.01 sec)

mysql> start slave;
Query OK, 0 rows affected (0.00 sec)

mysql> show slave status\G;
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.183.103
                  Master_User: sync
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000001
          Read_Master_Log_Pos: 454
               Relay_Log_File: master-relay-bin.000002
                Relay_Log_Pos: 320
        Relay_Master_Log_File: mysql-bin.000001
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes

查看Slave_IO_Running和Slave_SQL_Running状态为Yes说明设置成功。

node2做主，node1做从的情况
先在node2上操作：

mysql> grant replication slave,replication client on *.* to 'sync'@'%' identified by 'bigdata';
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000001 |      462 |              |                  |                   |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)

在node1上操作：

mysql> change master to master_host='192.168.183.102',master_user='sync',master_password='bigdata',master_log_file='mysql-bin.000001',master_log_pos=462;
Query OK, 0 rows affected, 2 warnings (0.00 sec)

mysql> start slave;
Query OK, 0 rows affected (0.01 sec)

mysql> show slave status\G;
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.183.102
                  Master_User: sync
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000001
          Read_Master_Log_Pos: 462
               Relay_Log_File: worker-relay-bin.000002
                Relay_Log_Pos: 320
        Relay_Master_Log_File: mysql-bin.000001
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes

测试

在node1上创建sync01数据库

mysql> create database sync01;
Query OK, 1 row affected (0.01 sec)

在node2上查看数据库

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| sync01             |
| sys                |
+--------------------+
5 rows in set (0.00 sec)

（此处遗留一个问题，就是如果防火墙firewalld关闭的话，两库之间是同步的，如果firewalld不关闭，需要增加策略？）

已解决：
防火墙开启的状态下，需要将mysql服务放行，使用firewall-cmd工具

# 查看firewall-cmd版本
[root@master services]# firewall-cmd --version
0.4.4.4
# 查看已经放行的服务
[root@master services]# firewall-cmd --list-service
ssh dhcpv6-client
# 永久放行
[root@master services]# firewall-cmd --add-service=mysql --permanent
success
# 重新加载使生效，不用重启
[root@master services]# firewall-cmd --reload
success
# 重新查看已放行的服务
[root@master services]# firewall-cmd --list-service
ssh dhcpv6-client mysql

Keepalive安装

下载Keepalive安装包，就是源码包
https://www.keepalived.org/software/keepalived-2.0.10.tar.gz
下载后上传到节点1和节点2，以节点1为例上传到/opt目录（自定义）并解压

yum源的设置

cd /etc/yum.repos.d/
mv /etc/yum.repos.d/CentOS-Base.repo /etc/yum.repos.d/CentOS-Base.repo.bakup        # 复制原有的源文件
wget -O /etc/yum.repos.d/CentOS-Base.repo http://mirrors.aliyun.com/repo/Centos-7.repo              # 通过wget获取阿里云的源文件
yum clean all                                   # 清除缓存
yum makecache

安装keepalive所需要环境

yum install -y openssl-devel popt-devel  curl gcc  libnl3-devel net-snmp-devel  libnfnetlink-devel

进入安装目录，编译，安装。

cd /opt/keepalived-2.0.10
[root@master keepalived-2.0.10]# ./configure --prefix=/opt/keepalived
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
......
Keepalived configuration
------------------------
Keepalived version       : 2.0.10
Compiler                 : gcc
Preprocessor flags       :  -I/usr/include/libnl3 
Compiler flags           : -Wall -Wunused -Wstrict-prototypes -Wextra -Winit-self -g -D_GNU_SOURCE -fPIE -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -O2  
Linker flags             :  -pie
Extra Lib                :  -lcrypto  -lssl  -lnl-genl-3 -lnl-3 
Use IPVS Framework       : Yes
IPVS use libnl           : Yes
IPVS syncd attributes    : No
IPVS 64 bit stats        : No
HTTP_GET regex support   : No
fwmark socket support    : Yes
Use VRRP Framework       : Yes
Use VRRP VMAC            : Yes
Use VRRP authentication  : Yes
With ip rules/routes     : Yes
Use BFD Framework        : No
SNMP vrrp support        : No
SNMP checker support     : No
SNMP RFCv2 support       : No
SNMP RFCv3 support       : No
DBUS support             : No
SHA1 support             : No
Use Json output          : No
libnl version            : 3
Use IPv4 devconf         : No
Use libiptc              : No
Use libipset             : No
init type                : systemd
Strict config checks     : No
Build genhash            : Yes
Build documentation      : No
# 编译
[root@master keepalived-2.0.10]# make
Making all in lib
make[1]: Entering directory `/opt/keepalived-2.0.10/lib'
make  all-am
make[2]: Entering directory `/opt/keepalived-2.0.10/lib'
  CC       memory.o
  CC       utils.o
utils.c: In function ‘fopen_safe’:
utils.c:792:6: warning: unused variable ‘flags’ [-Wunused-variable]
  int flags = O_NOFOLLOW | O_CREAT | O_CLOEXEC;
      ^
  CC       notify.o
  CC       timer.o
...
make[1]: Leaving directory `/opt/keepalived-2.0.10/genhash'
Making all in bin_install
make[1]: Entering directory `/opt/keepalived-2.0.10/bin_install'
make[1]: Leaving directory `/opt/keepalived-2.0.10/bin_install'
make[1]: Entering directory `/opt/keepalived-2.0.10'
  EDIT     README
make[1]: Leaving directory `/opt/keepalived-2.0.10'

############################################### 安装
[root@master keepalived-2.0.10]# make install
Making install in lib
make[1]: Entering directory `/opt/keepalived-2.0.10/lib'
make  install-am
make[2]: Entering directory `/opt/keepalived-2.0.10/lib'
make[3]: Entering directory `/opt/keepalived-2.0.10/lib'
make[2]: Nothing to be done for `install-exec-am'.
 /usr/bin/mkdir -p '/opt/keepalived/share/doc/keepalived'
 /usr/bin/install -c -m 644 README '/opt/keepalived/share/doc/keepalived'
make[2]: Leaving directory `/opt/keepalived-2.0.10'
make[1]: Leaving directory `/opt/keepalived-2.0.10

安装后目录如下

[root@master keepalived-2.0.10]# cd /opt/keepalived
[root@master keepalived]# ll
total 0
drwxr-xr-x. 2 root root 21 Jul 17 14:48 bin
drwxr-xr-x. 4 root root 41 Jul 17 14:48 etc
drwxr-xr-x. 2 root root 24 Jul 17 14:48 sbin
drwxr-xr-x. 5 root root 40 Jul 17 14:48 share

node2节点的安装方法一致

Keepalive配置

前期配置

# 可执行文件直接执行
[root@master keepalived]# cp /opt/keepalived/sbin/keepalived /usr/sbin/
# 加入开机启动
[root@master keepalived]# cp /opt/keepalived-2.0.10/keepalived/etc/init.d/keepalived /etc/init.d/
# 加入配置 网卡？  
[root@master keepalived]# cp /opt/keepalived/etc/sysconfig/keepalived /etc/sysconfig/
# 创建keepalive配置文件夹并拷贝配置文件
[root@master keepalived]# mkdir -p /etc/keepalived
[root@master keepalived]# cp /opt/keepalived/etc/keepalived/keepalived.conf /etc/keepalived/
# 开机启动文件增加可执行权限
[root@master keepalived]# chmod +x /etc/init.d/keepalived

编辑Keepalived关闭脚本

[root@master keepalived]# touch /var/lib/mysql/killkeepalived.sh

#!/bin/sh  
systemctl stop keepalived

# 保存退出后给脚本增加执行权限
[root@master mysql]# cd /var/lib/mysql
[root@master mysql]# chmod +x killkeepalived.sh

以上操作node1和node2一样，脚本内容也一样

编辑keepalived.conf文件，先编辑node1节点的

[root@master mysql]# cd /etc/keepalived/
[root@master keepalived]# vim keepalived.conf

内容如下：

! Configuration File for keepalived

global_defs {
   router_id MySQL-HA
}

vrrp_instance VI_1 {
    state BACKUP
    interface eth0
    virtual_router_id 51
    priority 100
    advert_int 1
    nopreempt
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        192.168.183.200
    }
}

virtual_server 192.168.183.200 3306 {
    delay_loop 6
#    lb_algo wrr
#    lb_kind DR
    persistence_timeout 50
    protocol TCP
    nat_mask 255.255.255.0

    real_server 192.168.183.102 3306 {
        weight 3
        notify_down /var/lib/mysql/killkeepalived.sh
        TCP_CHECK {
            connect_timeout 10
            nb_get_retry 3
            delay_before_retry 3
            connect_port 3306
        }
    }
}

再编辑node2节点的，内容如下

! Configuration File for keepalived

global_defs {
   router_id MySQL-HA
}

vrrp_instance VI_1 {
    state BACKUP
    interface eth0
    virtual_router_id 51
    priority 80
    advert_int 1
    nopreempt
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        192.168.183.200
    }
}

virtual_server 192.168.183.200 3306 {
    delay_loop 6
#    lb_algo wrr
#    lb_kind DR
    persistence_timeout 50
    protocol TCP
    nat_mask 255.255.255.0

    real_server 192.168.183.103 3306 {
        weight 3
        notify_down /var/lib/mysql/killkeepalived.sh
        TCP_CHECK {
            connect_timeout 10
            nb_get_retry 3
            delay_before_retry 3
            connect_port 3306
        }
    }
}

两份文件只有priority参数和real_server参考不一样，别的都一样。
这里判断MySQL服务是否正常是通过TCP_CHECK，没有通过脚本判断。

Keepalived启动

两节点启动keepalived服务并查看，启动指令如下：

[root@master keepalived]# systemctl start keepalived
[root@master keepalived]# systemctl status keepalived
● keepalived.service - LVS and VRRP High Availability Monitor
   Loaded: loaded (/usr/lib/systemd/system/keepalived.service; disabled; vendor preset: disabled)
   Active: active (running) since Sat 2020-07-18 15:45:14 CST; 18min ago
  Process: 10644 ExecStart=/opt/keepalived/sbin/keepalived $KEEPALIVED_OPTIONS (code=exited, status=0/SUCCESS)
 Main PID: 10645 (keepalived)
   CGroup: /system.slice/keepalived.service
           ├─10645 /opt/keepalived/sbin/keepalived -D
           ├─10646 /opt/keepalived/sbin/keepalived -D
           └─10647 /opt/keepalived/sbin/keepalived -D

Jul 18 15:46:16 master.learn.bigdata Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:16 master.learn.bigdata Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:16 master.learn.bigdata Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:16 master.learn.bigdata Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:21 master.learn.bigdata Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:21 master.learn.bigdata Keepalived_vrrp[10647]: (VI_1) Sending/queueing gratuitous ARPs on eth0 for 192.168.183.200
Jul 18 15:46:21 master.learn.bigdata Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:21 master.learn.bigdata Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:21 master.learn.bigdata Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:21 master.learn.bigdata Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200

查看node1是否有虚拟IP

[root@master keepalived]# ip a
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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:88:a5:35 brd ff:ff:ff:ff:ff:ff
    inet 192.168.183.102/24 brd 192.168.183.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 192.168.183.200/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe88:a535/64 scope link 
       valid_lft forever preferred_lft forever

设置Keepalived开机启动

[root@worker mysql]# systemctl enable keepalived
Created symlink from /etc/systemd/system/multi-user.target.wants/keepalived.service to /usr/lib/systemd/system/keepalived.service.

验证节点漂移

两个节点同时打开查看日志/var/log/message

[root@master keepalived]# tail -1000f /var/log/messages
Jul 18 15:45:20 master Keepalived_healthcheckers[10646]: TCP connection to [192.168.183.102]:tcp:3306 success.
Jul 18 15:46:15 master Keepalived_vrrp[10647]: (VI_1) Backup received priority 0 advertisement
Jul 18 15:46:16 master Keepalived_vrrp[10647]: (VI_1) Receive advertisement timeout
Jul 18 15:46:16 master Keepalived_vrrp[10647]: (VI_1) Entering MASTER STATE
Jul 18 15:46:16 master Keepalived_vrrp[10647]: (VI_1) setting VIPs.
Jul 18 15:46:16 master Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:16 master Keepalived_vrrp[10647]: (VI_1) Sending/queueing gratuitous ARPs on eth0 for 192.168.183.200
Jul 18 15:46:16 master Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:16 master Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:16 master Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:16 master Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:21 master Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:21 master Keepalived_vrrp[10647]: (VI_1) Sending/queueing gratuitous ARPs on eth0 for 192.168.183.200
Jul 18 15:46:21 master Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:21 master Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:21 master Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 15:46:21 master Keepalived_vrrp[10647]: Sending gratuitous ARP on eth0 for 192.168.183.200
Jul 18 16:01:01 master systemd: Started Session 8 of user root.
Jul 18 16:01:01 master systemd: Starting Session 8 of user root.
Jul 18 16:06:45 master systemd: Reloading.

在节点1上关闭mysql服务，再次查看两节点虚拟IP和日志信息。
不再絮述。

脑裂现象

在另一个环境中，两个节点开启keepalived服务，使用ip a指令查看IP时，竟然都出现虚拟IP
节点一：

[root@master services]# ip a
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: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 34:48:ed:f3:76:a4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.45/24 brd 192.168.3.255 scope global noprefixroute em1
       valid_lft forever preferred_lft forever
    inet 192.168.3.43/32 scope global em1
       valid_lft forever preferred_lft forever
    inet6 fe80::b55e:98fd:5b2c:30c3/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

节点二：

[root@slave keepalived]# vim keepalived.conf 
[root@slave keepalived]# ip a
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: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 34:48:ed:f3:61:38 brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.46/24 brd 192.168.3.255 scope global noprefixroute em1
       valid_lft forever preferred_lft forever
    inet 192.168.3.43/32 scope global em1
       valid_lft forever preferred_lft forever
    inet6 fe80::f764:b214:bfa1:da7d/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

查看节点一的日志

Aug  1 17:31:27 localhost Keepalived_vrrp[200826]: (VI_1) Receive advertisement timeout
Aug  1 17:31:27 localhost Keepalived_vrrp[200826]: (VI_1) Entering MASTER STATE
Aug  1 17:31:27 localhost Keepalived_vrrp[200826]: (VI_1) setting VIPs.
Aug  1 17:31:27 localhost Keepalived_vrrp[200826]: Sending gratuitous ARP on em1 for 192.168.3.43

节点二的，就是说两个节点都说自己是master

Aug  1 17:33:00 localhost Keepalived_vrrp[97161]: VRRP sockpool: [ifindex(2), family(IPv4), proto(112), unicast(0), fd(10,11)]
Aug  1 17:33:04 localhost Keepalived_vrrp[97161]: (VI_1) Receive advertisement timeout
Aug  1 17:33:04 localhost Keepalived_vrrp[97161]: (VI_1) Entering MASTER STATE
Aug  1 17:33:04 localhost Keepalived_vrrp[97161]: (VI_1) setting VIPs.
Aug  1 17:33:04 localhost Keepalived_vrrp[97161]: Sending gratuitous ARP on em1 for 192.168.3.43

解决方案：
此问题应该是防火墙将vrrp广播给过滤掉了，导致backup接受不到master的广播，然后自己去争抢了vip，因此可以将防火墙关闭，也可以通过增加策略来解决，两个节点都执行

# 指令中em1根据自己的情况更改
[root@master services]# firewall-cmd --direct --permanent --add-rule ipv4 filter INPUT 0 --in-interface em1 --destination 224.0.0.18 --protocol vrrp -j ACCEPT
success
[root@master services]# firewall-cmd --reload
success

再次观察两个节点的ip a，发现神奇的好了。

再看我把你吃掉
关注
  • 0
    点赞
  • 踩
  • 3
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Mysql集群之mysql双主双活+keepalived实现高可用_mysql+keepalived搭建教程
a360284634的博客
11-24 1万+
史上最全mysql+keepalived教程。 本文介绍在linux服务下安装mysql并实现mysql主从配置，双主双活+keepalive实现mysql高可用的详细部署流程
mysql地址漂移_keepalived应用：漂移IP的实现
weixin_42365334的博客
02-01 826
state BACKUP：在keepalived中2种模式，分别是master->backup模式和backup->backup模式。这两种模式有很大区别。在master->backup模式下，一旦主库宕机，虚拟ip会自动漂移到从库，当主库修复后，keepalived启动后，还会把虚拟ip抢占过来，即使设置了非抢占模式(nopreempt)抢占ip的动作也会发生。在backup-...
keepalived安装配置使用
zhaikaiyun的博客
03-12 1410
keepalived服务介绍 keepalived是集群管理中保证集群高可用的一个服务软件，主要是防止单点故障问题。keepalived起初是专为LVS设计的，专门用来监控LVS集群系统中各个服务节点的状态，后来又加入了VRRP的功能，因此除了配合LVS的服务外，还可以作为其他服务（nginx\haproxy）的高可用软件。Keepalived提供了两个主要功能： 1)健康检查LVS系统，检查L...
keepalive配置mysql自动故障转移
热门推荐
雅冰石的专栏
02-29 1万+
本文先配置了一个双master环境，互为主从，然后通过Keepalive配置了一个虚拟IP，客户端通过虚拟IP连接master1,当master1宕机，自动切换到master2。一次只能连接其中一个master进行读写，所以是active-passive模式。 一 Mysql主主复制搭建 1.1 实验环境 两台机器事先都已经装好了mysql单实例。 二者的端...
keepalive+nginx实现负载均衡高可用（已验证）
u012433915的专栏
04-08 6281
keepalived实现nginx高可用(HA) 　一、在两台nginx机器上安装keepalived yum install keepalived -y （这种方式安装更靠谱，编译安装容易出错，亲测） 1. 在主节点上配置keepalived vim /etc/keepalived/keepalived.conf global_defs { notification_email { 3813472...
mysql+lvs+keepalive+mha高可用
07-19
5. **测试与监控**：进行故障模拟测试，确保在主服务器故障时，服务能够自动切换且数据一致性不受影响。同时，持续监控系统的运行状态。 通过这个架构，企业可以构建一个高度可靠的MySQL服务环境，降低因单一硬件...
Keepalive+mysql主主同步.pdf
09-04
"Keepalive+mysql主主同步" Keepalive+mysql主主同步是指在高可用性环境中，使用Keepalive和MySQL主主同步技术来实现数据库的高可用性和负载均衡。下面是相关的知识点： 一、Keepalive简介 Keepalive是一个高可用...
nginx1.9.7+keepalive1.3.2
04-26
标题 "nginx1.9.7+keepalive1.3.2" 暗示我们要讨论的是一个特定版本的 Nginx 服务器软件，与 Keepalive 模块的结合使用。Nginx 是一款广泛使用的高性能 web 服务器和反向代理服务器，而 Keepalive 模块则是增强其...
centos7-lvs+keepalive部署
12-19
centos7-lvs+keepalive部署.
keepalive+lvs+mysql部署
06-04
keepalive+lvs+mysql部署,mysql主备配置 ！
MySQL MHA KEEPALIVE最佳部署指南
01-19
MySQL MHA KEEPALIVE最佳部署指南
centos-mini环境下安装配置keepalived v2.0.6
qq_42794720的博客
08-17 1068
1.自行到http://www.keepalived.org/下载对应的keepalived版本 2.安装必要的库
mysql 5.7 mmm_Centos7:Mysql 5.7 安装
weixin_32047493的博客
01-30 112
yum安装是最简便和稳定的安装方式，centos7默认安装的是mariadb，需要先卸载mariadb，先查看是否安装mariadbrpm -qa | grep mariadb如果找到，则拷贝结果，使用下面命令删除，如删除mariadb-libs-5.5.35-3.el7.x86_64rpm -e --nodeps mariadb-libs-5.5.35-3.el7.x86_641.卸载 先停掉...
MySQL高可用之MMM介绍
weixin_47019016的博客
03-10 1891
高可用之MMM一、MMM简介二、部署实施 一、MMM简介 MMM即Multi-Master Replication Manager for MySQL:mysql多主复制管理器,基于perl实现,关于mysql主主复制 配置的监控、故障转移和管理的一套可伸缩的脚本套件（在任何时候只有一个节点可以被写入），MMM也能 对从服务器进行读负载均衡，所以可以用它来在一组用于复制的服务器启动虚拟ip，除此之外，它还有实现数 据备份、节点之间重新同步功能的脚本。MySQL本身没有提供replication failov
keepalive安装配置
大树叶 技术专栏
04-07 5024
环境准备  系统需要的 LINUX 版本为：2.6.9‐5.ELsmp   需要的keepalived 版本为：1.1.20  ?  检查 LINUX版本 [root@test01 etc]# uname -r 2.6.9-5.ELsmp ?   检查 keepalived 版本 [root@test01 keepalived]# pwd /root/disk/keep
MySQL5.7+keepalive+增强型半同步搭建文档
weixin_34272308的博客
10-27 211
MySQL5.7+keepalive+增强型半同步搭建文档 转载于:https://blog.51cto.com/625052787/1976713...
mysql启用keepalive_mysql5.7+keepalive1.3.5
weixin_36125719的博客
12-28 349
keepalived部署方案一、基本思路两台mysql互为主从关系， 通过keepalived配置虚拟IP，实现当其中一台mysql 挂机后，应用能自动切换到另外一台，从而保证系统的高可用。二、系统环境vip：192.168.7.170master1：192.168.7.171master2：192.168.7.172一、配置mysql主主同步修改master1的mysql配置文件/etc/my....
nginx+tomcat的keepalive验证、bio/nio连接比较
看看写写，记录所学，权当笔记の
12-27 3074
最近刚好有时间找了台机器压测了一下，验证一下自己的一些想法。 很多时候我们会发现实际情况并不如我们所了解，一方面是实际情况并非完美，会受到许多环境的影响，所以结果有时与我们所学理论会相悖，更有甚者，有时在网上了解的理论本身或过时，或并不正确，所以在有机会、抑或有条件的情况，可是实验一下自己所学，这也可加深理解。 1. nginx+tomcat keepalive验证
CentOS7.4上mysql5.7双主keepalived实现高可用
kadwf123的专栏
09-02 763
目录 1、环境规划... 1 2、准备rpm包... 1 3、安装mysql 2 4、检查安装... 2 5、配置文件... 2 6、启动mysql 5 7、mysql root用户密码... 5 8、mysql日志... 5 9、详细参见... 5 10、创建mysql复制账户... 6 11、搭建双主... 6 12、下载keepalived源码包... 7 13、安...
nginx+keepalive+tomcat+redis+mysql+inotify+rsync+elk如何部署搭建需要几台服务器
最新发布
06-06
第一台服务器可以部署nginx、keepalive、redis、inotify和rsync服务。nginx作为反向代理服务器，通过keepalive与tomcat服务器通信，并且使用redis作为缓存服务。inotify用于监控文件系统变化，rsync用于文件同步。 ...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值