Hi,
I'm fresh new to heartbeat, and I'm still learning all the
configurations.
I'm using this rule:
<rsc_location id="my_resource:connected" rsc="my_resource">
<rule id="my_resource:connected:rule" score_attribute="pingd" >
<expression id="my_resource:connected:expr:defined"
attribute="pingd" operation="defined"/>
</rule>
</rsc_location>
This is working fine, for the example it was made.
I need something different, because both of my machines (2 nodes) have
the same weight, so both can do the job, since this is only one
fail over cluster.
Knowing this, i enable the option resource stickiness to INFINITY, to
disable the resource group I have created, from migrating again to the
main node.
Example, i start both nodes, my resource it's at node1, I take out
network connectivity from node1, and node2 take care of all the
resources. Working fine, but when node1 its up again, the resource
should not migrate to node1 again, should stay on node2.
My problem with this is, if i have resource_stickiness set to
'INFINITY' and i use this rsc_location rule, that reads the score from
the pingd daemon, if the network connectivity goes down, for node1,
where the resources were running, they not migrate to node2.
If i set resource_stickiness to '0', this works very fine, but, when
node1 comes up again, heartbeat migrates the resources again to node1.
The help i need is, how do i set this behaviour, but disable the
migration after node1 comes up again?
The idea it's to survive and provide always service, if the public
network connectivity it's loss, on any of the nodes, and prevent
migrating resources when not needed.
Thanks.
---------
Igor Neves <[EMAIL PROTECTED]>
3GNTW - Tecnologias de Informação, Lda
sip [EMAIL PROTECTED] jid [EMAIL PROTECTED]
icq 249075444 tlm 00351914503611
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
