首先,我不是Linux专家,我一直在跟随教程,并一直在谷歌的帮助下,这工作到现在为止罚款,但目前我坚持一个问题。
我正在使用CentOS 6.5和DRBD 8.4.4版。
我有两个运行起搏器的节点,到目前为止一切正常,我build立了DRBD,我可以手动将一个节点设置为主节点,并安装DRBD资源,这样也可以工作。
现在我创build了一个起搏器资源来控制DRBD,但是它并没有促使两个节点中的任何一个节点掌握这个节点,这也阻止了它的安装。
个人电脑状态如下所示:
Cluster name: hydroC Last updated: Wed Jun 25 14:19:49 2014 Last change: Wed Jun 25 14:02:25 2014 via crm_resource on hynode1 Stack: cman Current DC: hynode1 - partition with quorum Version: 1.1.10-14.el6_5.3-368c726 2 Nodes configured 4 Resources configured Online: [ hynode1 hynode2 ] Full list of resources: ClusterIP (ocf::heartbeat:IPaddr2): Started hynode1 Master/Slave Set: MSdrbdDATA [drbdDATA] Slaves: [ hynode1 hynode2 ] ShareDATA (ocf::heartbeat:Filesystem): Stopped
ShareData保持停止,因为没有主人
我最初遵循这个教程:
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Clusters_from_Scratch/_configure_the_cluster_for_drbd.html
这是起搏器configuration的外观:
Cluster Name: hydroC Corosync Nodes: Pacemaker Nodes: hynode1 hynode2 Resources: Resource: ClusterIP (class=ocf provider=heartbeat type=IPaddr2) Attributes: ip=10.0.0.100 cidr_netmask=32 Operations: monitor interval=30s (ClusterIP-monitor-interval-30s) Master: MSdrbdDATA Meta Attrs: master-max=1 master-node-max=1 clone-max=2 clone-node-max=1 notify =true Resource: drbdDATA (class=ocf provider=linbit type=drbd) Attributes: drbd_resource=r0 Operations: monitor interval=60s (drbdDATA-monitor-interval-60s) Resource: ShareDATA (class=ocf provider=heartbeat type=Filesystem) Attributes: device=/dev/drbd3 directory=/share/data fstype=ext4 Operations: monitor interval=60s (ShareDATA-monitor-interval-60s) Stonith Devices: Fencing Levels: Location Constraints: Ordering Constraints: promote MSdrbdDATA then start ShareDATA (Mandatory) (id:order-MSdrbdDATA-Share DATA-mandatory) Colocation Constraints: ShareDATA with MSdrbdDATA (INFINITY) (with-rsc-role:Master) (id:colocation-Sha reDATA-MSdrbdDATA-INFINITY) Cluster Properties: cluster-infrastructure: cman dc-version: 1.1.10-14.el6_5.3-368c726 no-quorum-policy: ignore stonith-enabled: false
我已经尝试了不同的东西,如设置位置约束或使用不同的资源设置…我从另一个教程:
Master: MSdrbdDATA Meta Attrs: master-max=1 master-node-max=1 clone-max=2 notify=true target-role =Master is-managed=true clone-node-max=1 Resource: drbdDATA (class=ocf provider=linbit type=drbd) Attributes: drbd_resource=r0 drbdconf=/etc/drbd.conf Meta Attrs: migration-threshold=2 Operations: monitor interval=60s role=Slave timeout=30s (drbdDATA-monitor-int erval-60s-role-Slave) monitor interval=59s role=Master timeout=30s (drbdDATA-monitor-in terval-59s-role-Master) start interval=0 timeout=240s (drbdDATA-start-interval-0) stop interval=0 timeout=240s (drbdDATA-stop-interval-0)
但结果保持不变,没有任何节点被升级为主节点。
我会很感激任何帮助指导我的解决scheme,在此先感谢。
确保您的DRBD设备是健康的。 如果你# cat /proc/drbd看看它的状态,你看到下面的内容: cs:Connected , ro:Secondary/Secondary ,最重要的是ds:UpToDate/UpToDate ?
如果没有UpToDate数据,DRBD的资源代理将不会升级设备。 如果您刚刚创build了设备的元数据,并且尚未将单个节点强制为主angular色,则会看到您的磁盘状态为: ds:Inconsistent/Inconsistent 。 您需要运行以下命令来告诉DRBD哪个节点应该成为群集的SyncSource : # drbdadm primary r0 --force
在正常情况下,这是唯一一次你不得不迫使DRBD进入小学的时候。 所以之后忘了--force标志)