[Pacemaker] After a bug is closed, I was confused with default-resource-stickiness

Adrian Chapela achapela.rexistros at gmail.com
Wed Nov 26 06:56:25 EST 2008


after the bug 
http://developerbugs.linux-foundation.org/show_bug.cgi?id=1852 is 
closed. Now I am confused with the behaviour of default-resource-stickiness.

I want two nodes, one of them as Master (always the same..) but if this 
master fails I need the "Failover Master" remains as master until an 
admin do maintenance on the failed node. For this I have the next 

        <rsc_order id="MySQL-IP_Group" first="MySQL" 
first-action="promote" then="IP_Group" then-action="start"/>
        <rsc_colocation id="IP_Group-with-MySQL" rsc="IP_Group" 
with-rsc="MySQL" with-rsc-role="Master" score="INFINITY"/>
        <rsc_location id="loca_MySQL_node1" rsc="MySQL">
                <rule id="rule_loc_MySQL_node1" role="Master" score="100">
                        <expression id="exp_rule_MySQL_node1" 
attribute="#uname" operation="eq" value="node1"/>
        <rsc_location id="loca_MySQL_node2" rsc="MySQL">
                <rule id="rule_loc_MySQL_node2" role="Master" score="50">
                        <expression id="exp_rule_MySQL_node2" 
attribute="#uname" operation="eq" value="node2"/>
        <rsc_location id="mysql-connectivity" rsc="MySQL">
                <rule id="mysql-pingd-prefer-rule" score="-INFINITY" 
                        <expression id="mysql-pingd-prefer" 
attribute="pingd" operation="lt" value="1000"/>

Another rule is failing for me is the pingd rule but I think it is a 
problem with pingd. I have this messages in error log:
pingd[2936]: 2008/11/26_12:46:31 info: ping_read: Retrying...
pingd[2936]: 2008/11/26_12:46:31 info: ping_read: Retrying...

I have attached status and config xml. I think pingd problem is when I 
unplugged cable or I down the ethernet interface (ifdown eth0). In these 
cases, pingd have an error "ping_read: Retrying..." and it doesn't 
update value but if it can get  hosts pingd update value. For me this is 
a problem because you could have a switch power failure and this network 
card will go down.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: state.xml
Type: text/xml
Size: 20682 bytes
Desc: not available
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20081126/60bd824e/attachment.xml>

More information about the Pacemaker mailing list