takeover, fencing & failback

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

I'm working on a two node cluster (RHEL 5.2 + RHCS) with one
XEN virtual machine per node:

node1 => VM1
node2 => VM2

When node1 takes over VM2 via the command:

clusvcadm -M vm:VM2 -m node1

node2 gets fenced after takeover is done, which is probably expected behaviour.

As node2 comes up again it fetches his VM2 back (nofailback="0", but also
fences node1 (ipmilan) where VM1 is still running an therefore interrupted and 
restartet on node2.
When node1 comes up the same game in the other direction begins.
Is there a way to avoid this fence loop?

In other words: can a service be migrated from node1 to node2 without other
services that run on node1 being interrupted?

thanks & regards
Gerhard

<?xml version="1.0"?>
<cluster alias="fusi01" config_version="41" name="fusi01">
        <fence_daemon post_fail_delay="3" post_join_delay="30"/>
        <clusternodes>
                <clusternode name="node1" nodeid="1" votes="1">
                        <fence>
                                <method name="1">
                                        <device lanplus="1" name="OLS011-m"/>
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="node2" nodeid="2" votes="1">
                        <fence>
                                <method name="1">
                                        <device lanplus="1" name="OLS012-m"/>
                                </method>
                        </fence>
                </clusternode>
        </clusternodes>
        <quorumd device="/dev/mapper/HDS-00F9p2" votes="1"/>
        <cman expected_votes="3" two_node="0"/>
        <fencedevices>
                <fencedevice agent="fence_ipmilan" auth="password" ipaddr="ols011-m" login="root" name="OLS011-m" passwd="xxx"/>
                <fencedevice agent="fence_ipmilan" auth="password" ipaddr="ols012-m" login="root" name="OLS012-m" passwd="xxx"/>
        </fencedevices>
        <rm>
                <failoverdomains>
                        <failoverdomain name="fusi01_hvm_dom" nofailback="0" ordered="1" restricted="1">
                                <failoverdomainnode name="node1" priority="1"/>
                                <failoverdomainnode name="node2" priority="2"/>
                        </failoverdomain>
                        <failoverdomain name="fusi01_pvm_dom" nofailback="0" ordered="1" restricted="1">
                                <failoverdomainnode name="node1" priority="2"/>
                                <failoverdomainnode name="node2" priority="1"/>
                        </failoverdomain>
                </failoverdomains>
                <resources/>
                <vm autostart="1" domain="fusi01_pvm_dom" exclusive="0" migrate="live" name="VM1" path="/fusi01pvm" recovery="restart"/>
                <vm autostart="1" domain="fusi01_hvm_dom" exclusive="0" migrate="live" name="VM2" path="/fusi01hvm" recovery="restart"/>
        </rm>
</cluster>
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux