mysql启用keepalive_mysql主从之keepalive+MySQL高可用
一 keepalive介绍
1.1 keepalived 是什么
keepalived 是集群管理中保证集群高可用的一个服务软件，用来防止单点故障。
1.2 keepalived 工作原理
keepalived 是以VRRP 协议为实现基础的，VRRP 全称VirtualRouter Redundancy Protocol，即虚拟路由冗余协议。虚拟路由冗余协议，可以认为是实现路由器高可用的协议，即将N 台提供相同功能的路由器组成一个路由器组，这个组里面有一个master 和多个backup，master 上面有一个对外提供服务的vip(该路由器所在局域网内其他机器的默认路由为该vip)，master 会发组播，当backup 收不到vrrp 包时就认为master 宕掉了，这时就需要根据VRRP 的优先级来选举一个backup 当master。这样的话就可以保证路由器的高可用了。
keepalived 主要有三个模块，分别是core、check 和vrrp。
core 模块为keepalived 的核心，负责主进程的启动、维护以及全局配置文件的加载和解析。
check 负责健康检查，包括常见的各种检查方式。
vrrp 模块是来实现VRRP 协议的。
1.3 实验环境
master1:192.168.132.121
master2:192.168.132.122
虚拟IP:192.168.132.120
双主环境
master1
master1
mysql>show slave status\G;*************************** 1. row ***************************Slave_IO_State: Waitingformaster to send event
Master_Host:192.168.132.122Master_User: replication
Master_Port:3306Connect_Retry:60Master_Log_File: master-bin.000003Read_Master_Log_Pos:4975Relay_Log_File: relay-log.000003Relay_Log_Pos:913Relay_Master_Log_File: master-bin.000003Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno:0Last_Error:
Skip_Counter:0Exec_Master_Log_Pos:4975Relay_Log_Space:2618Until_Condition: None
Until_Log_File:
Until_Log_Pos:0Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master:0Master_SSL_Verify_Server_Cert: No
Last_IO_Errno:0Last_IO_Error:
Last_SQL_Errno:0Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id:2Master_UUID: 662134df-a196-11e9-b432-000c2963fd11
Master_Info_File:/data/mysql/master.infoSQL_Delay:0SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Slave has read all relay log; waitingfor moreupdates
Master_Retry_Count:86400Master_Bind:
Last_IO_Error_Timestamp:
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set: 662134df-a196-11e9-b432-000c2963fd11:1-7Executed_Gtid_Set: 63a7f26f-a196-11e9-a2b2-000c2991dd19:1-18,
662134df-a196-11e9-b432-000c2963fd11:1-7Auto_Position:1Replicate_Rewrite_DB:
Channel_Name:
master2
mysql>show slave status\G;*************************** 1. row ***************************Slave_IO_State: Waitingformaster to send event
Master_Host:192.168.132.121Master_User: replication
Master_Port:3306Connect_Retry:60Master_Log_File: master-bin.000008Read_Master_Log_Pos:650Relay_Log_File: relay-log.000008Relay_Log_Pos:865Relay_Master_Log_File: master-bin.000008Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno:0Last_Error:
Skip_Counter:0Exec_Master_Log_Pos:650Relay_Log_Space:2098Until_Condition: None
Until_Log_File:
Until_Log_Pos:0Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master:0Master_SSL_Verify_Server_Cert: No
Last_IO_Errno:0Last_IO_Error:
Last_SQL_Errno:0Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id:1Master_UUID: 63a7f26f-a196-11e9-a2b2-000c2991dd19
Master_Info_File:/data/mysql/master.infoSQL_Delay:0SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Slave has read all relay log; waitingfor moreupdates
Master_Retry_Count:86400Master_Bind:
Last_IO_Error_Timestamp:
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set: 63a7f26f-a196-11e9-a2b2-000c2991dd19:1-18Executed_Gtid_Set: 63a7f26f-a196-11e9-a2b2-000c2991dd19:1-18,
662134df-a196-11e9-b432-000c2963fd11:1-7Auto_Position:1Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:
二 配置keepalive
2.1 开始安装keepalived
[root@master1 ~]# cd /usr/local/src/
[root@master1 src]# wget https://www.keepalived.org/software/keepalived-2.0.17.tar.gz
[root@master1 src]# tar -xf keepalived-2.0.17.tar.gz
[root@master1 src]# cd keepalived-2.0.17
[root@master1 keepalived-2.0.17]# yum install openssl* libnl‐dev* gcc-c++
[root@master1 keepalived-2.0.17]# ./configure --prefix=/usr/local/keepalived
[root@master1 keepalived-2.0.17]# make
[root@master1 keepalived-2.0.17]# make install
[root@master1 keepalived-2.0.17]# cd /usr/local/keepalived/sbin/
[root@master1 sbin]# ll
-rwxr-xr-x. 1 root root 2381368 Jul 9 11:59 keepalived
[root@master1 sbin]# cp keepalived /usr/sbin/
[root@master1 sbin]# ll /usr/sbin/keepalived
-rwxr-xr-x. 1 root root 2381368 Jul 9 12:01 /usr/sbin/keepalived
[root@master1 sbin]# systemctl list-unit-files|grep keepalived
[root@master1 sbin]# systemctl enable keepalived
[root@master1 sbin]# systemctl list-unit-files|grep keepalived
[root@master1 sbin]# mkdir /etc/keepalived
[root@master1 sbin]# cp /usr/local/keepalived/etc/keepalived/keepalived.conf /etc/keepalived/
[root@master1 sbin]# ll /etc/keepalived/
-rw-r--r--. 1 root root 3550 Jul 9 12:06 keepalived.conf
2.2 配置keepailve
root@master1 keepalived-2.0.17]# vim /etc/keepalived/keepalived.conf
! Configuration File forkeepalived
global_defs {
router_id db01
}
vrrp_instance VI_1 {
state BACKUP
interface ens33
virtual_router_id51priority100nopreempt
advert_int1authentication {
auth_type PASS
auth_pass1111}
virtual_ipaddress {192.168.132.120}
}
virtual_server192.168.132.120 3306{
delay_loop6persistence_timeout50protocol TCP
real_server192.168.132.121 3306{
notify_down/etc/keepalived/kill_keepalived.shTCP_CHECK {
connect_timeout3nb_get_retry3connect_port3306delay_before_retry3}
}
}
配置简介
global_defs 区域主要是配置故障发生时的通知对象以及机器标识
notification_email_from Alexandre.Cassen@firewall.loc//通知邮件从哪个地址发出
smtp_server 192.168.200.1 //通知邮件的smtp 地址
smtp_connect_timeout 30 //连接smtp 服务器的超时时间
router_id db01 //标识本节点的字符串， 通常为hostname
vrrp_skip_check_adv_addr
vrrp_strict
vrrp_garp_interval0vrrp_gna_interval0}
vrrp_instance VI_1 {//VRRP 实例state MASTER//MASTER 或BACKUP，为了防止脑裂现象，主备均需要设置为backup 模式，master 模式会抢占VIP
interface eth0 //节点固有IP(非VIP)的网卡，用来发VRRP 包
virtual_router_id 51 //取值在0-255 之间，用来区分多个instance 的VRRP 组播priority 100//优先级，同一个vrrp_instance 的MASTER优先级必须比BACKUP 高nopreempt//非抢占，配合backup,防止切换后，主库服务恢复正常后，IP 漂移过来advert_int 1//MASTER 与BACKUP 负载均衡器之间同步检查的时间间隔，单位为秒。
authentication {
auth_type PASS
auth_pass1111}
virtual_ipaddress {//虚拟ip 地址,可以有多个地址，每个地址占一行，不需要子网掩码
192.168.132.120}
}
virtual_server192.168.200.16 3306{
delay_loop6 //健康检查间隔，单位为秒
persistence_timeout 50 //会话保持时间，就是把用户请求转发给同一个服务器
protocol TCP //转发协议，有TCP 和UDP 两种，一般用TCP
real_server 192.168.132.121 3306 { //真实服务器，包括IP和端口号
notify_down kill_keepalived.shTCP_CHECK { #通过tcpcheck 判断RealServer 的健康状态
connect_timeout3#连接超时时间
nb_get_retry3#重连次数
delay_before_retry3#重连时间间隔
connect_port3306#检测端口
}
}
}
keepalived 服务配置
#设置不抢占模式(DB1 设置即可)
nopreempt
#虚拟路由标识，这个标识是一个数字(1‐255)，在一个VRRP
实例中主备服务器ID 必须一样
virtual_router_id 68
#优先级，数字越大优先级越高，在一个实例中主服务器优
先级要高于备服务器
priority 100 #从服务器99
#设置主备之间同步检查的时间间隔单位秒
advert_int 1
[root@master1 keepalived-2.0.17]# vim /etc/keepalived/kill_keepalived.sh
[root@master1 keepalived-2.0.17]# chmod +x /etc/keepalived/kill_keepalived.sh
#!/bin/bashkill -9 $(cat /var/run/keepalived.pid)
[root@master1 keepalived-2.0.17]# systemctl start keepalived
[root@master1 keepalived-2.0.17]# cat /var/run/keepalived.pid
16287
master2相同做法
配置文件
[root@master2 sbin]# cat /etc/keepalived/keepalived.conf
[root@master2 sbin]# cat /etc/keepalived/keepalived.conf! Configuration File forkeepalived
bal_defs {
router_id db02
}
vrrp_instance VI_1 {
state BACKUP
interface ens33
virtual_router_id51priority90nopreempt
advert_int1authentication {
auth_type PASS
auth_pass1111}
virtual_ipaddress {192.168.132.120}
}
virtual_server192.168.132.120 3306{
delay_loop6persistence_timeout50protocol TCP
real_server192.168.132.122 3306{
notify_down/etc/keepalived/kill_keepalived.shTCP_CHECK {
connect_timeout3nb_get_retry3connect_port3306delay_before_retry3}
}
}
2.3 检查状态
[root@master2 ~]# systemctl status keepalived
[root@master2 ~]# ps -ef|grep keepalived
[root@master1 ~]# ip addr
1: lo: mtu 65536 qdisc noqueue state UNKNOWN qlen 1link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet127.0.0.1/8scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128scope host
valid_lft forever preferred_lft forever2: ens33: mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 00:0c:29:91:dd:19brd ff:ff:ff:ff:ff:ff
inet192.168.132.121/24 brd 192.168.132.255scope global ens33
valid_lft forever preferred_lft forever
inet192.168.132.120/32scope global ens33 #虚拟IP地址
valid_lft forever preferred_lft forever
inet6 fe80::b469:7426:8024:a47c/64scope link
valid_lft forever preferred_lft forever3: ens34: mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 00:0c:29:91:dd:23brd ff:ff:ff:ff:ff:ff
inet192.168.43.85/24 brd 192.168.43.255scope global dynamic ens34
valid_lft 2810sec preferred_lft 2810sec
inet192.168.254.121/24 brd 192.168.254.255scope global ens34
valid_lft forever preferred_lft forever
inet6 fe80::4d8:1809:407a:5c0a/64scope link
valid_lft forever preferred_lft forever
master2查看
1: lo: mtu 65536 qdisc noqueue state UNKNOWN qlen 1link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet127.0.0.1/8scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128scope host
valid_lft forever preferred_lft forever2: ens33: mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 00:0c:29:63:fd:11brd ff:ff:ff:ff:ff:ff
inet192.168.132.122/24 brd 192.168.132.255scope global ens33
valid_lft forever preferred_lft forever
inet6 fe80::5d18:db0b:8907:de34/64scope link
valid_lft forever preferred_lft forever3: ens34: mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 00:0c:29:63:fd:1b brd ff:ff:ff:ff:ff:ff
inet192.168.254.122/24 brd 192.168.254.255scope global ens34
valid_lft forever preferred_lft forever
inet6 fe80::c3d5:5055:468a:94f8/64scope link
valid_lft forever preferred_lft forever
三 验证
授权后尝试使用192.168.132.20这个IP连接数据库
mysql> grant all on *.* to root@192.168.132.123 identified by '1234567';mysql>flush privileges;
[root@slave ~]# mysql -ureplication -h192.168.132.120 -p1234567
mysql>show databases;+--------------------+
| Database |
+--------------------+
| information_schema |
| master1 |
| master2 |
| mysql |
| performance_schema |
| sys |
+--------------------+
关闭192.168.132.121的mysqld
[root@master1 ~]# systemctl stop mysqld
[root@master1 ~]# ip addr
1: lo: mtu 65536 qdisc noqueue state UNKNOWN qlen 1link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet127.0.0.1/8scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128scope host
valid_lft forever preferred_lft forever2: ens33: mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 00:0c:29:91:dd:19brd ff:ff:ff:ff:ff:ff
inet192.168.132.121/24 brd 192.168.132.255scope global ens33
valid_lft forever preferred_lft forever
inet6 fe80::b469:7426:8024:a47c/64scope link
valid_lft forever preferred_lft forever3: ens34: mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 00:0c:29:91:dd:23brd ff:ff:ff:ff:ff:ff
inet192.168.43.85/24 brd 192.168.43.255scope global dynamic ens34
valid_lft 3348sec preferred_lft 3348sec
inet192.168.254.121/24 brd 192.168.254.255scope global ens34
valid_lft forever preferred_lft forever
inet6 fe80::4d8:1809:407a:5c0a/64scope link
valid_lft forever preferred_lft forever
查看master2
[root@master2 ~]# ip addr
1: lo: mtu 65536 qdisc noqueue state UNKNOWN qlen 1link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet127.0.0.1/8scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128scope host
valid_lft forever preferred_lft forever2: ens33: mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 00:0c:29:63:fd:11brd ff:ff:ff:ff:ff:ff
inet192.168.132.122/24 brd 192.168.132.255scope global ens33
valid_lft forever preferred_lft forever
inet192.168.132.120/32scope global ens33 #虚拟IP已经转移过来
valid_lft forever preferred_lft forever
inet6 fe80::5d18:db0b:8907:de34/64scope link
valid_lft forever preferred_lft forever3: ens34: mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 00:0c:29:63:fd:1b brd ff:ff:ff:ff:ff:ff
inet192.168.254.122/24 brd 192.168.254.255scope global ens34
valid_lft forever preferred_lft forever
inet6 fe80::c3d5:5055:468a:94f8/64scope link
valid_lft forever preferred_lft forever
使用slave连接
[root@slave ~]# mysql -uroot -h192.168.132.120 -p1234567mysql>show databases;+--------------------+
| Database |
+--------------------+
| information_schema |
| master1 |
| master2 |
| mysql |
| performance_schema |
| sys |
+--------------------+
依然可以访问,双主的高可用配置完成
在master1开启MySQL和keepalive后,虚拟IP并不会抢占回来,是因为设置的是非抢占模式,防止虚拟IP跳动影响性能
mysql启用keepalive_mysql主从之keepalive+MySQL高可用相关推荐
- mysql keepalive_mysql主从之keepalive+MySQL高可用
一 keepalive介绍 1.1 keepalived 是什么 keepalived 是集群管理中保证集群高可用的一个服务软件,用来防止单点故障. 1.2 keepalived 工作原理 keepa ...
- MySQL - 高可用性：少宕机即高可用？
MySQL - 高可用性:少宕机即高可用? 原文:MySQL - 高可用性:少宕机即高可用? 我们之前了解了复制.扩展性,接下来就让我们来了解可用性.归根到底,高可用性就意味着 "更少的宕机 ...
- MySQL HA（High Availability） 数据库高可用工具Orchestrator安装
目录 1.下载安装包 2.安装 backend MySQL server 3.在MySQL实例上授权 4.启动orchestrator 服务 5.参考 本文主要介绍如何在本地安装 MySQL HA(H ...
- linux 双mysql_MySQL双主互备+Keepalived高可用架构实现案例
一.环境介绍 1.1.规划 序号 类别 版本 主机名 IP 端口 备注 1 OS CentOS release 6.9 (Final) (minimal) my1 172.16.210.180 830 ...
- mysql从 lvs_mysql主从之LVS+keepalived+双主MySQL 负载均衡
LVS(Linux Virtual Server)即Linux 虚拟服务器,是一个的开源负载均衡项目,目前LVS 已经被集成到Linux 内核模块中.LVS 是四层负载均衡,也就是说建立在OSI 模型 ...
- mysql主主复制+keepalived 打造高可用mysql集群
为了响应公司需求,打造出更安全的mysql集群,能够实现mysql故障后切换,研究了几天终于有了成果,一起分享一下. 首先介绍一下这套集群方案实现的功能 1.mysql服务器故障后自动转移,修好后自动 ...
- linux mysql 自动加斜杠_【实战演练】Linux操作系统19-Mysql主主复制加Keepalived高可用...
理论部分,在之前的文章已经说明过了,详见: 繁星亮与鲍包包:[理论研究]业务系统高可用及负载均衡zhuanlan.zhihu.com 上一篇已经讲述对2台Mysql服务器做主主复制,实现Mysql数 ...
- mysql 主备及时_MySQL高可用（二）主备延时如何解决？
从上篇文章我们知道主备同步是依赖于 binlog,主库负责生产 binlog,备库负责消费 binlog,从而实现主备同步. 今天我们来学习一下主备同步里的一个重点的问题:主备延时. 主备延时,简单来 ...
- mysql 双主 脑裂_MySQL高可用方案——双主
MySQL高可用方案--双主 发布时间:2020-03-01 20:45:48 来源:51CTO 阅读:253 作者:warrent MySQL的高可用方案有很多种,双主.MHA.MMM等等,这里只是 ...
最新文章
- 2021年春季学期-信号与系统-第十一次作业参考答案-第七小题
- AI安全初探——利用深度学习检测DNS隐蔽通道
- python哪一版好用-最好的 Python IDE,你们推荐使用哪一个？
- 沙漠之旅（二维dp）
- C++11遍历map
- qt接收服务器信息中文乱码,在qt提取lineedit中的中文字符串，通过tcp通信时，服务器接收乱码的情况，解决办法...
- linux如何安装ut880驱动下载,UT-8801 UT - 下载 - 搜珍网
- sql获取某列出现频次最多的值_业务硬核SQL集锦
- 数据类型转换规则C语言
- 硬盘显示容量和实际容量不符合_买移动固态硬盘纠结大半天？花2分钟看完这篇，购买时不再被坑...
- 使用鸿蒙系统的家电厂商,除了华为外！谁还会用鸿蒙系统？米OV们不可能：这些巨头才会用...
- 软件体系结构风格介绍
- 常用字典代码推荐标准
- 计算机网络第一章概述
- 什么是抽象类？什么是抽象方法？
- 微软沈向洋，百度李彦宏、王海峰，阿里王坚均候选中国工程院院士
- 开源正弦波20kHz信号发生器电路分析
- 浅谈TEDS智能传感器
- hdu【1290】献给杭电五十周年校庆的礼物
- 坑！人民币符号￥为什么有时候一根横线，有时候两根横线？
热门文章
- Linux一些软件的安装
- koa2 mysql_koa2+vue+mysql 全栈开发记录
- python实例解析_python中super的用法实例解析
- activiti 工作流_JAVA-工作流引擎-activiti-Tasks介绍
- PHP表格整个往右,css - 使用table表格无端的整体向右偏移一段距离
- ide 两个模块的jdk版本不一样_Java平台模块系统（3）- JDK工具
- java可以继承私有的,关于java：继承中的私有方法
- python 排列组合速度_Python实现的简单排列组合算法示例
- 分析udp数据报_开发需知！！！TCP和UDP的特点和区别
- c语言学习-输入一个十进制数，输出其对应的八进制数据