[Pacemaker] crm_mon shows wrong value of migration-threshold.

Satomi Taniguchi taniguchis at intellilink.co.jp
Mon Aug 4 04:41:50 CEST 2008


Hi,

I found that the value of migration-threshold which crm_mon shows is odd
with the latest Pacemaker-dev(b5a66eb9c9c0).
It shows default-migration-threshold's value, not the value of
each resource's migration-threshold.
(Please see the attached files.)

Maybe, this is because the timing that common_apply_stickiness() is
called has changed.
Is it a right way to solve it to return the function to
unpack_lrm_resources()?

Regards,
Satomi Taniguchi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cib.xml
Type: text/xml
Size: 6761 bytes
Desc: not available
Url : http://list.clusterlabs.org/pipermail/pacemaker/attachments/20080804/8cad849d/cib.bin
-------------- next part --------------


============
Last updated: Mon Aug  4 09:55:51 2008
Current DC: rh5u2node2 (2fdcdb68-89cb-43e0-a93f-137bebdc5edc)
1 Nodes configured.
3 Resources configured.
============

Node: rh5u2node2 (2fdcdb68-89cb-43e0-a93f-137bebdc5edc): online

Resource Group: grpPostgreSQLDB
    prmIpPostgreSQLDB	(ocf::heartbeat:IPaddr):	Started rh5u2node2
    prmApPostgreSQLDB	(ocf::heartbeat:pgsql):	Started rh5u2node2
stonith-1	(stonith:external/ssh):	Started rh5u2node2

Operations:
* Node rh5u2node2: 
   stonith-1: migration-threshold=3
    + start: rc=0 (ok)
   prmApPostgreSQLDB: migration-threshold=3
    + start: rc=0 (ok)
    + monitor: interval=10000ms rc=0 (ok)
   prmIpPostgreSQLDB: migration-threshold=3
    + start: rc=0 (ok)
    + monitor: interval=10000ms rc=0 (ok)
Cleaning up CIB connection: 1


More information about the Pacemaker mailing list