Re: failover not working

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

 




You should use Linux H.A. (heartbeat) for failover. the rgmanager very good but not yet. you not must use failover with rgmanager. you can get some problems because of priority and two failover happened some the wrong.

have a nice day..

From: James Wilson <jwilson@xxxxxxxxxxxxxxxxx>
Reply-To: jwilson@xxxxxxxxxxxxxxxxx,linux clustering <linux-cluster@xxxxxxxxxx>
To: Jonathan Brassow <jbrassow@xxxxxxxxxx>
CC: linux clustering <linux-cluster@xxxxxxxxxx>
Subject: Re:  failover not working
Date: Tue, 03 Jul 2007 16:08:11 -0500

I have changed it since I posted this. But I though I needed the 2 failover domains? One for each host so if dolphins fails it failsover to patriots and vice versa. Or do I just need one because of the virtual IP?


               <failoverdomains>
                       <failoverdomain name="dolphins-drbd1" ordered="1">
<failoverdomainnode name="dolphins" priority="1"/> <failoverdomainnode name="patriots" priority="2"/>
                       </failoverdomain>
<failoverdomain name="dolphins-drbd2" ordered="1" restricted="0"> <failoverdomainnode name="dolphins" priority="2"/> <failoverdomainnode name="patriots" priority="1"/>
                       </failoverdomain>
               </failoverdomains>
               <resources>
                       <ip address="192.168.5.4" monitor_link="1"/>
               </resources>
<service autostart="1" domain="dolphins-drbd1" name="dolphins-svc-drbd1" recovery="relocate">
                       <ip ref="192.168.5.4"/>
               </service>
<service autostart="1" domain="dolphins-drbd2" name="dolphins-svc-drbd2" recovery="relocate">
                       <ip ref="192.168.5.4"/>
               </service>
       </rm>
       <fence_xvmd/>
       <fence_xvmd/>


Jonathan Brassow wrote:

On Jul 2, 2007, at 3:10 PM, James Wilson wrote:


       <rm>
               <failoverdomains>
<failoverdomain name="dolphins-drbd1" ordered="1"> <failoverdomainnode name="dolphins" priority="1"/> <failoverdomainnode name="patriots" priority="2"/>
                       </failoverdomain>
<failoverdomain name="dolphins-drbd2" ordered="1" restricted="0"> <failoverdomainnode name="dolphins" priority="2"/> <failoverdomainnode name="patriots" priority="1"/>
                       </failoverdomain>
               </failoverdomains>
               <resources>
                       <ip address="192.168.5.4" monitor_link="1"/>
               </resources>
<service autostart="1" domain="dolphins-drbd1" name="dolphins-svc-drbd1" recovery="relocate">
                       <ip ref="192.168.5.4"/>
               </service>
<service autostart="1" domain="dolphins-drbd2" name="dolphins-svc-drbd2" recovery="relocate">
                       <ip ref="192.168.5.4"/>
               </service>
       </rm>

That section looks funny. You don't need the two 'failoverdomain's; and you don't need the two services. Does rgmanager even startup? Check /var/log/messages for more info.

 brassow


--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

_________________________________________________________________
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507

--
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