[Pacemaker] Question about cluster start-up in a 2 node cluster with a node offline.

James FLatten jflatten at iso-ne.com
Fri Feb 10 13:45:23 EST 2012


On 02/09/2012 09:36 AM, Andreas Kurz wrote:
> No, this is not a correct behavior ... but for more ... not enough
> information.
Andreas-

Thanks for looking at this.

Here is the version information:

    pacemaker-libs-1.1.6-3.el6.x86_64
    pacemaker-1.1.6-3.el6.x86_64
    pacemaker-cluster-libs-1.1.6-3.el6.x86_64
    pacemaker-cli-1.1.6-3.el6.x86_64
    drbd-pacemaker-8.4.1-1.el6.x86_64
    corosync-1.4.1-4.el6.x86_64
    corosynclib-1.4.1-4.el6.x86_64

Here is the configuration:

    node nodea \
         attributes standby="off"
    node nodeb \
         attributes standby="off"
    primitive ClusterIP ocf:heartbeat:IPaddr2 \
         params ip="192.168.1.3" cidr_netmask="32" \
         op monitor interval="30s"
    primitive datafs ocf:heartbeat:Filesystem \
         params device="/dev/drbd0" directory="/data" fstype="ext3" \
         meta target-role="Started"
    primitive drbd0 ocf:linbit:drbd \
         params drbd_resource="drbd0" \
         op monitor interval="60s"
    primitive drbd1 ocf:linbit:drbd \
         params drbd_resource="drbd1" \
         op monitor interval="60s"
    primitive httpd ocf:heartbeat:apache \
         params configfile="/etc/httpd/conf/httpd.conf" \
         op monitor interval="1min"
    primitive ipmi-fencing stonith:fence_ipmilan \
         params pcmk_host_list="nodea nodeb" ipaddr="xxx.xxx.xxx.xxx"
    login="xxxxxxx" passwd="xxxxxxx" lanplus="1" timeout="4" auth="md5" \
         op monitor interval="60s"
    primitive patchfs ocf:heartbeat:Filesystem \
         params device="/dev/drbd1" directory="/patch" fstype="ext3" \
         meta target-role="Started"
    group web datafs patchfs ClusterIP httpd
    ms drbd0clone drbd0 \
         meta master-max="1" master-node-max="1" clone-max="2"
    clone-node-max="1" notify="true"
    ms drbd1clone drbd1 \
         meta master-max="1" master-node-max="1" clone-max="2"
    clone-node-max="1" notify="true"
    clone fencing ipmi-fencing
    colocation datafs-with-drbd0 inf: web drbd0clone:Master
    colocation patchfs-with-drbd1 inf: web drbd1clone:Master
    order datafs-after-drbd0 inf: drbd0clone:promote web:start
    order patchfs-after-drbd1 inf: drbd1clone:promote web:start
    property $id="cib-bootstrap-options" \
         dc-version="1.1.6-3.el6-a02c0f19a00c1eb2527ad38f146ebc0834814558" \
         cluster-infrastructure="openais" \
         expected-quorum-votes="2" \
         stonith-enabled="true" \
         no-quorum-policy="ignore" \
         last-lrm-refresh="1328556424"
    rsc_defaults $id="rsc-options" \
         resource-stickiness="100"

Attached is the log file from the time the system started up on the b 
node until the services finished coming online.

Thanks!
Davin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120210/962427ec/attachment-0003.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: corosync.log.problem
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120210/962427ec/attachment-0003.ksh>


More information about the Pacemaker mailing list