Hi everyone,<br><br>I'm starting to get my memcached cluster setup more operational now. But I'm running into one small problem -- when my memcached resource check fails, the stonith primitive isn't triggered to reset the node. It only happens when it's loaded up enough to cause corosync to fail. When the stonith does fire, it resets the node correctly.<br>
<br>Here's the relevant snippets of my config. fence_virsh is used just for my testing environment of Xen VMs.<br><br>------------------------------------------------------------------------------------------------------------------------<br>
<span style="font-family:courier new,monospace">node mem1</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">node mem2</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">node mem3</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">primitive mem1-xen-host stonith:fence_virsh \</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"> op monitor interval="1s" timeout="5s" \</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> params ipaddr="vmhost1" login="root" action="reboot" identity_file="/root/.ssh/id_dsa" port="mem1" pcmk_host_list="mem1" pcmk_host_check="static-list" pcmk_host_map="" verbose="true" debug="/var/log/vmhost1.log" \</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> meta is-managed="true"</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">primitive memcached ocf:fbs:memcached \</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> meta is-managed="true" \</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"> op monitor interval="1s" timeout="1s"</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">clone mem1-xen-host-clone mem1-xen-host \</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"> meta target-role="Started"</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">clone memcached_clone memcached \</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"> params ordered="false" \</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> meta target-role="Started" migration-threshold="1"</span><br style="font-family:courier new,monospace"><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"># stonith device for mem1 should never run on mem1</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">location st-mem1-not-on-mem1 mem1-xen-host-clone -inf: mem1</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> </span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"># ensure ip-mem1 has a working memcache</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">colocation ip-mem1-on-memcache inf: cluster-ip-mem1 memcached_clone</span><br style="font-family:courier new,monospace"><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"># ensure ip-mem2 does not live on the same node as ip-mem1</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"># UNLESS the other 2 nodes are down. </span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">colocation ip-mem2-not-on-ip-mem1 -10000: cluster-ip-mem2 cluster-ip-mem1</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">-----------------------------------------------------------------------------------------------------------------------------</span><br style="font-family:courier new,monospace">
<br>And here's what the cluster status looks like when the memcached service check is failing, but the node is still up.<br><br>-----------------------------------------------------------------------------------------------------------------------------<br>
<span style="font-family:courier new,monospace">Online: [ mem1 mem2 mem3 ]</span><br style="font-family:courier new,monospace"><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"> cluster-ip-mem2 (ocf::heartbeat:IPaddr2): Started mem2</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> cluster-ip-mem1 (ocf::heartbeat:IPaddr2): Started mem3</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"> Clone Set: memcached_clone [memcached]</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> Started: [ mem2 mem3 ]</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"> Stopped: [ memcached:2 ]</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> Clone Set: mem1-xen-host-clone [mem1-xen-host]</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"> Started: [ mem2 mem3 ]</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> Stopped: [ mem1-xen-host:2 ]</span><br style="font-family:courier new,monospace">-----------------------------------------------------------------------------------------------------------------------------<br>
<br>What configuration directive can I add that would force the stonith event to run when the memcached_clone is stopped?<br><br>Thank you!<br><br>--Cal<br><br><br>