角色 |
IP |
用途 |
Master A |
10.10.10.33 |
MySQL DB |
Master B |
10.10.10.36 |
|
VIP |
10.10.10.199 |
KeepAlived VIP |
解压安装包到指定目录/opt/usr/:
# tar -zxvf keepalived-1.2.13.tar.gz -C /opt/usr/
# cd /opt/usr/keepalived-1.2.13/
创建安装目录:
# mkdir /opt/usr/keepalived
编译安装
# ./configure --prefix=/opt/usr/keepalived/
# make;make install
configure: error:
!!! OpenSSL is not properly installed on your system. !!!
!!! Can not include OpenSSL headers files. !!!
解决:
yum install -y openssl openssl-devel
默认情况下keepalived启动时会去/etc/keepalived目录下找配置文件
#A主机和B主机都操作
# mkdir /etc/keepalived
#cp安装生成的conf模板到/etc/keepalived
# cp /opt/usr/keepalived/etc/keepalived/keepalived.conf /etc/keepalived/
#Master A配置文件
# vi /etc/keepalived/keepalived.conf
# mkdir -p /usr/local/MySQL/bin/
# vi /usr/local/MySQL/bin/MySQL.sh
注:此脚本是上面配置文件notify_down选项所用到的,keepalived使用notify_down选项来检查real_server的服务状态,当发现real_server服务故障时,便触发此脚本;我们可以看到,脚本就一个命令,通过pkill keepalived强制杀死keepalived进程,从而实现了MySQL故障自动转移。另外,我们不用担心两个MySQL会同时提供数据更新操作,因为每台MySQL上的keepalived的配置里面只有本机MySQL的IP+VIP,而不是两台MySQL的IP+VIP
~]# /opt/us/keepalived/sbin/keepalived –D
# ps -ef|grep keep
#停止MySQL服务
# /etc/init.d/mysql stop
Shutting down MySQL..... [ OK ]
#查看vip,发现VIP已经不存在
# ip a|grep eth0
3: eth1: mtu 1500 qdisc pfifo_fast state UP qlen 1000
inet 192.168.56.101/24 brd 192.168.56.255 scope global eth1
#查看keepalive进程消失
# ps -ef|grep keep
root 29537 4894 0 20:34 pts/2 00:00:00 grep keep
#监控日志
# tail -f /var/log/messages
Dec 3 20:34:08 MySQL1 Keepalived_healthcheckers[29424]: TCP connection to [192.168.56.101]:3306 failed !!!
Dec 3 20:34:08 MySQL1 Keepalived_healthcheckers[29424]: Removing service [192.168.56.101]:3306 from VS [192.168.56.111]:3306
Dec 3 20:34:08 MySQL1 Keepalived_healthcheckers[29424]: Executing [/usr/local/MySQL/bin/MySQL.sh] for service [192.168.56.101]:3306 in VS [192.168.56.111]:3306
Dec 3 20:34:08 MySQL1 Keepalived_healthcheckers[29424]: Lost quorum 1-0=1 > 0 for VS [192.168.56.111]:3306
Dec 3 20:34:08 MySQL1 Keepalived_healthcheckers[29424]: Remote SMTP server [127.0.0.1]:25 connected.
Dec 3 20:34:09 MySQL1 Keepalived[29423]: Stopping Keepalived v1.2.13 (12/03,2014)
Dec 3 20:34:09 MySQL1 Keepalived_vrrp[29425]: VRRP_Instance(MySQL-HA{) sending 0 priority
Dec 3 20:34:09 MySQL1 Keepalived_vrrp[29425]: VRRP_Instance(MySQL-HA{) removing protocol VIPs.
Dec 3 20:34:09 MySQL1 Keepalived_healthcheckers[29424]: Netlink reflector reports IP 192.168.56.111 removed
Dec 3 20:34:09 MySQL1 avahi-daemon[1430]: Server startup complete. Host name is MySQL1-62.local. Local service cookie is 1197773774.
Dec 3 20:34:09 MySQL1 avahi-daemon[1430]: Withdrawing address record for 192.168.56.111 on eth1.
Dec 3 20:34:10 MySQL1 avahi-daemon[1430]: Service "MySQL1-62" (/services/ssh.service) successfully established.
#跟DB1基本一致,但有三个地方不同:优先级为90、无抢占设置、real_server为本机IP
# vi /etc/keepalived/keepalived.conf
# mkdir -p /usr/local/MySQL/bin/
# vi /usr/local/MySQL/bin/MySQL.sh
# /opt/usr/keepalived/sbin/keepalived
# ip a|grep eth0
#停止MySQL服务
# /etc/init.d/mysql stop
Shutting down MySQL..... [ OK ]
#查看vip,发现VIP已经不存在
# ip a|grep eth0
3: eth1: mtu 1500 qdisc pfifo_fast state UP qlen 1000
inet 192.168.56.101/24 brd 192.168.56.255 scope global eth1
#查看keepalive进程消失
# ps -ef|grep keep
root 29537 4894 0 20:34 pts/2 00:00:00 grep keep
#监控日志
# tail -f /var/log/messages
Dec 4 10:35:53 MySQL2 Keepalived_healthcheckers[6733]: TCP connection to [192.168.56.102]:3306 failed !!!
Dec 4 10:35:53 MySQL2 Keepalived_healthcheckers[6733]: Removing service [192.168.56.102]:3306 from VS [192.168.56.111]:3306
Dec 4 10:35:53 MySQL2 Keepalived_healthcheckers[6733]: Executing [/usr/local/MySQL/bin/MySQL.sh] for service [192.168.56.102]:3306 in VS [192.168.56.111]:3306
Dec 4 10:35:53 MySQL2 Keepalived_healthcheckers[6733]: Lost quorum 1-0=1 > 0 for VS [192.168.56.111]:3306
Dec 4 10:35:53 MySQL2 Keepalived_healthcheckers[6733]: Remote SMTP server [127.0.0.1]:25 connected.
Dec 4 10:35:53 MySQL2 Keepalived[6732]: Stopping Keepalived v1.2.13 (11/24,2014)
Dec 4 10:35:53 MySQL2 Keepalived_vrrp[6734]: VRRP_Instance(MySQL-HA{) sending 0 priority
Dec 4 10:35:53 MySQL2 Keepalived_vrrp[6734]: VRRP_Instance(MySQL-HA{) removing protocol VIPs.
Dec 4 10:35:53 MySQL2 Keepalived_healthcheckers[6733]: Netlink reflector reports IP 192.168.56.111 removed
Dec 4 10:35:54 MySQL2 avahi-daemon[1387]: Withdrawing address record for 192.168.56.111 on eth1.
~]# mysql -u root -h 10.10.10.199 -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 2622
Server version: 5.6.21-log MySQL Community Server (GPL)
Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql>
cp /opt/usr/keepalived/etc/rc.d/init.d/keepalived /etc/init.d/
cp /opt/usr/keepalived/etc/sysconfig/keepalived /etc/sysconfig/
cp /opt/usr/keepalived/sbin/keepalived /sbin/
# /etc/init.d/keepalived -h
Usage: /etc/init.d/keepalived {start|stop|reload|restart|condrestart|status}
chkconfig --level 2345 keepalived on
相关推荐
### Keepalived+Nginx 实现高可用Web负载均衡 #### 场景需求 在现代互联网应用中,网站和应用程序需要处理大量的用户请求,并确保即使在服务器出现故障的情况下也能持续提供服务。为了满足这一需求,通常采用高可用...
二、keepalived配置 keepalived的配置文件是/etc/keepalived/keepalived.conf。该文件定义了keepalived的全局设置、VRRP脚本、VRRP实例等信息。在主服务器和从服务器上,keepalived的配置文件都需要进行相应的修改...
Keepalived + Nginx 实现高可用 Web 负载均衡配置文件,具体详情参见博文:http://blog.csdn.net/l1028386804/article/details/72801492
"高可用之Keepalived+Nginx实现...4. 高可用之 Keepalived+Nginx 实现高可用 Web 负载均衡的步骤和配置。 5. VIPIP 主机名、Nginx 端口、默认主从关系等高可用之 Keepalived+Nginx 实现高可用 Web 负载均衡的关键技术。
keepalived安装实现高可用的配置
在这个高可用架构中,我们使用 Keepalived 来实现 Nginx 的高可用,通过 Keepalived,我们可以将多个 Nginx 服务器组成一个高可用集群,使得我们的 web 服务具有高可用性。同时,我们还可以使用 Nginx 的负载均衡...
Keepalived 是一种高可用性解决方案,可以与 Nginx 和 Tomcat 配合使用来实现高可用集群。下面是 Keepalived+Nginx+Tomcat 高可用集群搭建的实战记录。 Keepalived 简介 Keepalived 是一种基于 Linux 的高可用性...
### 分布式架构高可用架构-Keepalived+Nginx实现高可用Web负载均衡 #### 一、场景需求 在互联网应用中,随着用户数量的增长和技术的发展,单一服务器已难以满足日益增长的服务需求。分布式系统架构应运而生于解决...
2. **配置vrrp_instance**:在Keepalived配置文件(通常为`/etc/keepalived/keepalived.conf`)中,定义一个vrrp_instance,指定虚拟IP地址、优先级、密码等信息。 3. **配置检查脚本**:编写一个用于检查Redis服务...
在本文中,我们将详细介绍LVS、KeepAlived和Nginx的安装和配置过程,并提供一个完整的高可用实现方案。 一、LVS安装和配置 LVS可以通过源码安装或yum安装,安装完成后需要配置ipvsadm工具来管理LVS集群。 二、...
此外,这个脚本假设你正在安装Keepalived作为MASTER节点;如果你正在安装BACKUP节点,你需要更改state MASTER为state BACKUP,并相应地调整priority值。 此外,对于生产环境,你可能还需要考虑其他因素,如防火墙...
### 源码安装Nginx与Keepalived实现高可用集群 #### 一、概述 在本篇文章中,我们将详细介绍如何通过源码安装的方式部署Nginx与Keepalived来构建一个高可用(High Availability,简称HA)的Web服务集群。这种方式...
【MySQL高可用负载均衡配置】 在IT领域,确保数据库系统的高可用性和负载均衡是至关重要的,特别是对于大型企业或高流量网站。Keepalived和HAProxy是两个强大的工具,常用于实现这一目标,尤其是针对MySQL数据库。在...
Keepalived 安装配置详解 Keepalived 是一个基于 Linux 平台的高可用性解决方案,可以实现服务器...Keepalived 是一个功能强大且灵活的高可用性解决方案,通过正确的安装和配置,可以实现服务器的负载均衡和高可用性。
本文将详细介绍如何采用Keepalived来实现Redis的双机高可用配置。 Keepalived是一款开源软件,主要用于网络服务的负载均衡和故障检测。它通常与Nginx、HAProxy等配合使用,但在Redis场景下,Keepalived可以用来实现...
5. **配置Keepalived**:在主节点的Keepalived配置中,指定健康检查脚本并设置较高优先级;从节点配置较低优先级,等待故障转移。 6. **启动服务**:启动Redis和Keepalived服务,验证虚拟IP是否正常工作,主从复制...
最后,部署Keepalived,配置VIP,确保在HAProxy节点发生故障时可以进行故障转移,以实现整个系统的高可用性。 在整个架构中,高可用性不仅仅体现在MyCat本身,还体现在负载均衡器HAProxy以及整个高可用集群的配置上...