Pacemaker

server1 和 server2 均安装pacemaker 和 corosync

server1 和 server2 作相同配置

[root@server1 ~]# yum install -y pacemaker corosync
[root@server1 ~]# cp /etc/corosync/corosync.conf.example /etc/corosync/corosync.conf
[root@server1 ~]# vim /etc/corosync/corosync.conf34 service {35         name: pacemaker36         ver: 037 }8  yum install -y pacemaker corosync9  cp /etc/corosync/corosync.conf.example /etc/corosync/corosync.conf10  vim /etc/corosync/corosync.conf
# Please read the corosync.conf.5 manual page
compatibility: whitetanktotem {version: 2secauth: offthreads: 0interface {ringnumber: 0bindnetaddr: 172.25.54.0mcastaddr: 226.94.1.54mcastport: 5405ttl: 1}
}logging {fileline: offto_stderr: noto_logfile: yesto_syslog: yeslogfile: /var/log/cluster/corosync.logdebug: offtimestamp: onlogger_subsys {subsys: AMFdebug: off}
}amf {mode: disabled
}
service {name: pacemakerver: 0
}

[root@server1 ~]# yum install -y crmsh-1.2.6-0.rc2.2.1.x86_64.rpm pssh-2.3.1-2.1.x86_64.rpm安装管理工具，链接：crmsh and pssh

[root@server1 ~]# crm      //进入管理界面
crm(live)# configure
crm(live)configure# show    //查看默认配置
node server1
node server2
property $id="cib-bootstrap-options" \dc-version="1.1.10-14.el6-368c726" \cluster-infrastructure="classic openais (with plugin)" \expected-quorum-votes="2"
crm(live)configure# 在另一台服务器上我们也可以实施监控查看
Server2:
[root@server1 ~]# crm_mon   //调出监控
Last updated: Sat Aug  4 15:07:13 2018
Last change: Sat Aug  4 15:00:04 2018 via crmd on server1
Stack: classic openais (with plugin)
Current DC: server1 - partition with quorum
Version: 1.1.10-14.el6-368c726
2 Nodes configured, 2 expected votes
0 Resources configured
//ctrl+c退出监控server1
crm(live)configure# property stonith-enabled=false  //禁掉fence
crm(live)configure# commit   //保存

注意：每次修改完策略都必须保存一下，否则不生效

server2
Last updated: Sat Aug  4 15:09:55 2018
Last change: Sat Aug  4 15:09:27 2018 via cibadmin on server1
Stack: classic openais (with plugin)
Current DC: server1 - partition with quorum
Version: 1.1.10-14.el6-368c726
2 Nodes configured, 2 expected votes
0 Resources configuredOnline: [ server1 server2 ]

[root@server2 rpmbuild]# crm_verify -VL //检查语法

添加VIP

crm(live)configure# primitive vip ocf:heartbeat:IPaddr2 params ip=172.25.54.100 cidr_netmask=24 op monitor interval=1min
crm(live)configure# commit

[root@server1 ~]# /etc/init.d/corosync stop
Signaling Corosync Cluster Engine (corosync) to terminate: [  OK  ]
Waiting for corosync services to unload:..                 [  OK  ]
[root@server1 ~]#

[root@server1 ~]# /etc/init.d/corosync start
Starting Corosync Cluster Engine (corosync):               [  OK  ]
[root@server1 ~]#

[root@server1 ~]# crm
crm(live)# configure
crm(live)configure# show
node server1
node server2
primitive vip ocf:heartbeat:IPaddr2 \params ip="172.25.54.100" cidr_netmask="24" \op monitor interval="1min"
property $id="cib-bootstrap-options" \dc-version="1.1.10-14.el6-368c726" \cluster-infrastructure="classic openais (with plugin)" \expected-quorum-votes="2" \stonith-enabled="false"
crm(live)configure# property no-quorum-policy=ignore  ##设置为ignore做实验，这时即使一个节点挂掉了，另一个节点也会正常工作
crm(live)configure# commit
crm(live)configure# bye
bye
[root@server1 ~]#

[root@server1 ~]# /etc/init.d/corosync stop
Signaling Corosync Cluster Engine (corosync) to terminate: [  OK  ]
Waiting for corosync services to unload:.                  [  OK  ]
[root@server1 ~]#

[root@server1 ~]# /etc/init.d/corosync start
Starting Corosync Cluster Engine (corosync):               [  OK  ]
[root@server1 ~]#

[root@server1 ~]# crm
crm(live)# configure
crm(live)configure# primitive haproxy lsb:haproxy op monitor interval=1min
crm(live)configure# commit
crm(live)configure#

crm(live)configure# group hagroup vip haproxy   //创建集群
crm(live)configure# commit
crm(live)configure#

[root@server2 ~]# crm configure show
node server1
node server2 \attributes standby="off"
primitive haproxy lsb:haproxy \op monitor interval="1min"
primitive vip ocf:heartbeat:IPaddr2 \params ip="172.25.54.100" cidr_netmask="24" \op monitor interval="1min"
group hagroup vip haproxy
property $id="cib-bootstrap-options" \dc-version="1.1.10-14.el6-368c726" \cluster-infrastructure="classic openais (with plugin)" \expected-quorum-votes="2" \stonith-enabled="false" \no-quorum-policy="ignore"

删除资源时，要到resource层下查看该资源是否在工作，若在工作，停掉资源，再到configure层删除

Fence

server1 和 server2
yum install fence-virt-0.2.3-15.el6.x86_64 -y

[root@server1 ~]# ll /etc/cluster/
total 4
-rw-r--r-- 1 root root 128 Aug  4 16:18 fence_xvm.key
[root@server1 ~]#

[root@server2 ~]# ll /etc/cluster/
total 4
-rw-r--r-- 1 root root 128 Aug  4 16:20 fence_xvm.key
[root@server2 ~]# crm
crm(live)# configure
crm(live)configure# property stonith-enabled=true   //启用fence
crm(live)configure# primitive vmfence stonith:fence_xvm params pcmk_host_map="server1:vm1;server2:vm2" op monitor interval=1min
crm(live)configure# commit
crm(live)configure# bye
bye
[root@server2 ~]#

[root@server1 ~]# [root@server1 ~]# echo c >/proc/sysrq-trigger //内核崩溃

此时server2会自动接替server1的工作，而server1则会后台自动重启
待server1重启成功后，再重启corosync服务

Haproxy + Pacemaker 实现高可用负载均衡（二）相关推荐

Haproxy + Pacemaker 实现高可用负载均衡（一）
pacemaker+corosync+haproxy > 高可用架构由两个核心部分组成,一个是心跳检测,判断服务器是否正常运行:一个是资源转移,用来将公共资源在正常服务器和故障服务器之间搬动.两 ...
haproxy keepalived_详解mycat+haproxy+keepalived搭建高可用负载均衡mysql集群
概述目前业界对数据库性能优化普遍采用集群方式,而oracle集群软硬件投入昂贵,mysql则比较推荐用mycat去搭建数据库集群,下面介绍一下怎么用mycat+haproxy+keepalived搭 ...
haproxy+keepalived实现高可用负载均衡
一,软件介绍 HAProxy提供高可用性.负载均衡以及基于TCP和HTTP应用的代理,支持虚拟主机,它是免费.快速并且可靠的一种解决方案,适用于那些负载特大的web站点,这些站点通常又需要会话保持或七 ...
HAProxy Keepalived L4-L7 高可用负载均衡解决方案
目录文章目录目录 HAProxy 负载均衡器应用特性性能优势会话保持健康检查配置文件负载均衡策略 ACL 规则 Web 监控平台 Keepalived 虚拟路由器核心组件 VRRP ...
高可用集群下的负载均衡（7）：haproxy + keepalived 实现高可用负载均衡
实验环境 server1 和 server2 是调度器,server3 和 server4 是服务器一.调度器中进行配置 haproxy+keepalived server1 与server2 均要 ...
Linux之企业实训篇——haproxy与pacemaker实现高可用负载均衡
注:haproxy与fence的相关配置可以参照一下我之前写的博客 >_< ~~~ 一.简介 Pacemaker是一个集群资源管理器.它利用集群基础构件(OpenAIS,heartbeat ...
基于linux下的 Pacemaker+Haproxy高可用负载均衡架构
corosync + pacemaker + crmsh 高可用集群 corosync提供集群的信息层(messaging layer)的功能,传递心跳信息和集群事务信息,多台机器之间通过组播的方式监 ...
haproxy负载均衡_基于mycat+haproxy+keepalived搭建mysql数据库高可用负载均衡
概述目前业界对数据库性能优化普遍采用集群方式,而oracle集群软硬件投入昂贵,mysql则比较推荐用mycat去搭建数据库集群,下面介绍一下怎么用mycat+haproxy+keepalived搭 ...
RabbitMQ+haproxy+keeplived 高可用负载均衡+镜像集群模式_集成高性能高可用组件 Keepalived_03
服务器IP hostname 节点说明端口管控台地址账号密码 192.168.0.115 mq-01 rabbitmq master 5672 http://192.168.0.115:156 ...

Haproxy + Pacemaker 实现高可用负载均衡（二）

Pacemaker

server1 和 server2 均安装pacemaker 和 corosync

Fence

Haproxy + Pacemaker 实现高可用负载均衡（二）相关推荐

最新文章

热门文章