本文詳細記錄如何在 CentOS 6.6 環境下,利用 Corosync、Pacemaker、DRBD 以及 MariaDB 構建一套高可用(HA)的 MySQL/MariaDB 資料庫叢集。架構採用雙節點主備模式,透過 DRBD 實現區塊級資料同步,Pacemaker 負責資源編排與故障轉移,Corosync 提供叢集通訊與成員管理。
Corosync 是 OpenAIS 專案衍生出的叢集通訊引擎,提供訊息傳遞、成員管理與仲裁功能。1.x 版本本身不具投票能力,需搭配 CMAN;2.x 引入 votequorum 子系統後原生支援仲裁。本文採用 1.4.7 版,並整合 Pacemaker。
Pacemaker 是叢集資源管理器(CRM),負責監控資源狀態、執行遷移與故障恢復。它透過 Corosync 的訊息層協調節點,確保服務高可用。
DRBD 將本地區塊裝置經網路鏡像到對端節點,類似網路版 RAID 1。資料寫入主節點時同步複製到備節點,確保資料一致性。
| 角色 | 主機名 | IP |
|---|---|---|
| Node1 | Legion100.dwhd.org | 172.16.6.100 |
| Node2 | Legion101.dwhd.org | 172.16.6.101 |
| VIP | — | 172.16.7.200 |
# 兩節點均執行
echo "172.16.6.100 Legion100.dwhd.org Legion100 node1" >> /etc/hosts
echo "172.16.6.101 Legion101.dwhd.org Legion101 node2" >> /etc/hosts
echo "*/5 * * * * /usr/sbin/ntpdate pool.ntp.org >/dev/null 2>&1" >> /var/spool/cron/root
ssh-keygen -t rsa -f ~/.ssh/id_rsa -P ''
ssh-copy-id -i ~/.ssh/id_rsa.pub root@對端主機名
yum install corosync pacemaker python-dateutil python-lxml pssh -y
cd /etc/corosync
cp corosync.conf.example corosync.conf
# 編輯 corosync.conf,關鍵段落:
totem {
version: 2
secauth: on
interface {
ringnumber: 0
bindnetaddr: 172.16.0.0
mcastaddr: 225.172.16.6
mcastport: 5405
ttl: 1
}
}
service {
ver: 0
name: pacemaker
}
corosync-keygen
scp /etc/corosync/{corosync.conf,authkey} node2:/etc/corosync/
wget https://www.dwhd.org/wp-content/uploads/2015/05/crmsh-2.1-1.6.x86_64.rpm
yum install crmsh-2.1-1.6.x86_64.rpm -y
service corosync start
ssh node2 "service corosync start"
# 檢查日誌確認啟動正常
grep "Corosync Cluster Engine" /var/log/cluster/corosync.log
crm status

rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org
rpm -Uvh https://www.elrepo.org/elrepo-release-6-6.el6.elrepo.noarch.rpm
yum install drbd84 kmod-drbd84 -y
chkconfig drbd on
global { usage-count yes; }
common {
handlers {
pri-on-incon-degr "/usr/lib/drbd/notify-pri-on-incon-degr.sh; /usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger; reboot -f";
pri-lost-after-sb "/usr/lib/drbd/notify-pri-lost-after-sb.sh; /usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger; reboot -f";
local-io-error "/usr/lib/drbd/notify-io-error.sh; /usr/lib/drbd/notify-emergency-shutdown.sh; echo o > /proc/sysrq-trigger; halt -f";
}
disk { on-io-error detach; }
net { cram-hmac-alg "sha1"; shared-secret "YzYxMDc1ZGYxYWU4"; }
}
resource mariadb {
on Legion100.dwhd.org {
device /dev/drbd0;
disk /dev/sdb1;
address 172.16.6.100:7789;
meta-disk internal;
}
on Legion101.dwhd.org {
device /dev/drbd0;
disk /dev/sdb1;
address 172.16.6.101:7789;
meta-disk internal;
}
}
將配置檔複製到 Node2:scp global_common.conf mariadb.res node1:/etc/drbd.d/
drbdadm create-md mariadb # 兩節點均執行,輸入 yes 確認
/etc/init.d/drbd start
# Node1 執行
drbdadm -- --overwrite-data-of-peer primary mariadb
# 觀察同步進度
watch -n 1 drbd-overview

# 同步完成後於主節點
mke2fs -t ext4 -L drbdMariaDB /dev/drbd0
mkdir /data
mount /dev/drbd0 /data
groupadd -g 1500 mysql && useradd -g mysql -u 1500 -s /sbin/nologin -M mysql
# 編譯安裝 cmake 3.2.2
# 下載 MariaDB 10.0.19 原始碼並編譯
cmake . -DCMAKE_INSTALL_PREFIX=/usr/local/mysql \
-DMYSQL_DATADIR=/data/mysql \
-DWITH_SSL=system \
-DWITH_INNOBASE_STORAGE_ENGINE=1 \
... (其他參數略)
make -j $(nproc) && make install
echo "export PATH=/usr/local/mysql/bin:\$PATH" > /etc/profile.d/mariadb10.0.19.sh
source /etc/profile.d/mariadb10.0.19.sh
cp support-files/mysql.server /etc/rc.d/init.d/mysqld
cp support-files/my-large.cnf /etc/my.cnf
sed -i '/query_cache_size/a datadir = /data/mysql' /etc/my.cnf
mkdir -p /data/mysql && chown -R mysql.mysql /data/mysql
/usr/local/mysql/scripts/mysql_install_db --user=mysql --datadir=/data/mysql --basedir=/usr/local/mysql
scp /etc/rc.d/init.d/mysqld /etc/my.cnf node2:/etc/
scp /tmp/{cmake-3.2.2.tar.gz,mariadb-10.0.19.tar.gz} node2:/tmp/
分別於兩節點將 DRBD 切換為 Primary,掛載 /data,啟動 MariaDB,確認資料庫內容一致。測試完成後關閉服務、卸載檔案系統、將 DRBD 降為 Secondary,關閉 drbd 服務並設為開機不啟動,交由 Pacemaker 管理。
/etc/init.d/drbd stop
chkconfig drbd off
crm configure
property stonith-enabled=false
property no-quorum-policy=ignore
primitive mysqldrbd ocf:linbit:drbd \
params drbd_resource=mariadb \
op start timeout=240 \
op stop timeout=100 \
op monitor role=Master interval=20 timeout=30 \
op monitor role=Slave interval=30 timeout=30
ms ms_mysqldrbd mysqldrbd \
meta master-max=1 master-node-max=1 clone-max=2 clone-node-max=1 notify=true
primitive mystore ocf:heartbeat:Filesystem \
params device="/dev/drbd0" directory="/data" fstype=ext4 \
op start timeout=60 op stop timeout=60
colocation mystore_with_ms_mysqldrbd inf: mystore ms_mysqldrbd:Master
order mystore_after_ms_mysqldrbd mandatory: ms_mysqldrbd:promote mystore:start
primitive mysqld lsb:mysqld
colocation mysqld_with_mystore inf: mysqld mystore
order mysqld_after_mystore mandatory: mystore mysqld
primitive myvip ocf:heartbeat:IPaddr \
params ip="172.16.7.200" \
op monitor interval=20 timeout=20 on-fail=restart
colocation vip_with_ms_mysqldrbd inf: ms_mysqldrbd:Master myvip
commit
quit
crm status

crm node standby Legion100.dwhd.org
# 觀察資源遷移至 Node2
crm status

# 在當前主節點刪除 VIP
ip addr del 172.16.7.200/16 dev eth0
# Pacemaker 會自動偵測並重新啟動 VIP
測試結果顯示 VIP 能在數秒內自動恢復,證實高可用機制有效運作。
本文完整演示了從基礎環境準備、叢集通訊層建立、區塊級資料同步、資料庫編譯部署到資源編排與故障演練的全流程。該架構適用於對資料一致性與服務連續性要求較高的中小型生產環境。後續可擴展加入 STONITH 設備、多節點仲裁、監控告警等功能,進一步提升叢集健壯性。