[Pacemaker] the behavior of resource-stickiness

[Junko IKEDA]

Hi,

I am running pacemaker 1.0.6 + corosync 1.1.2.
There are two resource and their "resource-stickiness" is "INFINITY".
They have rsc_colocation but there is no rsc_location setting.

(1) start the resources first
# crm_mon -1

============
Last updated: Thu Nov 19 20:35:45 2009
Stack: openais
Current DC: dom1 - partition with quorum
Version: 1.0.6-f709c638237cdff7556cb6ab615f32826c0f8c06
3 Nodes configured, 2 expected votes
2 Resources configured.
============

Online: [ dom9 dom1 dom2 ]

dummy1  (ocf::heartbeat:Dummy): Started dom1
dummy2  (ocf::heartbeat:Dummy): Started dom9


(2) standby one node
# crm_standby -U dom1 -v on

I expected that dummy2 kept running on dom9,
but it moved to another node.

# crm_mon -1
============
Last updated: Thu Nov 19 20:36:27 2009
Stack: openais
Current DC: dom1 - partition with quorum
Version: 1.0.6-f709c638237cdff7556cb6ab615f32826c0f8c06
3 Nodes configured, 2 expected votes
2 Resources configured.
============

Node dom1: standby
Online: [ dom9 dom2 ]

dummy1  (ocf::heartbeat:Dummy): Started dom9
dummy2  (ocf::heartbeat:Dummy): Started dom2


(2) standby "off" one node
# crm_standby -U dom1 -v off

Both dummy1 and dummy2 moved to the other node.
It's strange because these resources' "resource-stickiness" is "INFINITY".
Is there anything wrong in my setting?


# crm_mon -1
============
Last updated: Thu Nov 19 20:36:50 2009
Stack: openais
Current DC: dom1 - partition with quorum
Version: 1.0.6-f709c638237cdff7556cb6ab615f32826c0f8c06
3 Nodes configured, 2 expected votes
2 Resources configured.
============

Online: [ dom9 dom1 dom2 ]

dummy1  (ocf::heartbeat:Dummy): Started dom2
dummy2  (ocf::heartbeat:Dummy): Started dom1




I attached the log.

Thanks,
Junko
-------------- next part --------------
A non-text attachment was scrubbed...
Name: standby.tar.gz
Type: application/x-gzip
Size: 49553 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20091119/c2558231/attachment-0001.bin>