This could the solution for your second question.

Voipcrazy


auto_failback directive - set failback policy

The auto_failback option determines whether a resource will
automatically fail back to its "primary" node, or remain on whatever
node is serving it until that node fails, or an administrator
intervenes.

The possible values for auto_failback are:

    *

      on - enable automatic failbacks
    *

      off - disable automatic failbacks
    *

      legacy - enable automatic failbacks in systems where all nodes
in the cluster do not yet support the auto_failback option.

Both the auto_failback on and off are backwards compatible with the
old "nice_failback on" setting.

See the FAQ document for information on how to convert from "legacy"
to "on" without a flash cut (i.e., using a RollingUpgrade process)

>From URL:
http://www.linux-ha.org/ha.cf/AutoFailbackDirective


2008/10/3 Dejan Muhamedagic <[EMAIL PROTECTED]>:
> Hi,
>
> On Thu, Oct 02, 2008 at 04:55:03PM -0500, Paras pradhan wrote:
>> Hey all:
>>
>> It seems like my question is related to ha, drbd and xen . Hence posting to
>> all of them at once.
>
> Not sure if that's a good idea.
>
>> I have two nodes setup with xen 3.0.3, drbd82, heartbeat 2 under centos
>> 5.2. As I was testing this cluster for high availibility, I noticed some
>> issues
>>
>>
>> 1)  domA is running under node1. when I manually shutdown node 1, sometimes
>> it is migrated automatically to node2 and sometimes it is restarted in
>> node2. Why is this happening?
>
> How can it be restarted on node2 if it was running on node1?
>
>> 2) domA is running under node1. when I pull off the network cable, domA is
>> restarted in node 2 with no problem. But when the node1 comes back, domA is
>> not migrated to node1 and if i do 'xm list' under node1, I see
>> "migrating-domain". This is complicating everything.
>
> Indeed. Did you take a look at the logs?
>
>> My ha.cf file looks:
>>
>>
>> logfacility local0
>> udpport 694
>> keepalive 1
>> deadtime 5
>> warntime 3
>> initdead 10
>> ucast eth0 10.42.40.198
>> ucast eth0 10.42.40.26
>> auto_failback on
>> watchdog /dev/watchdog
>> debugfile /var/log/ha-debug
>> node ha1.domain.local
>> node ha2.domain.local
>
> Do you run v1/haresources or v2/CIB style configuration?
>
>>
>> Help !
>>
>> Thanks in advance
>> Paras.
>> _______________________________________________
>> Linux-HA mailing list
>> [email protected]
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to