<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><div><div><br class="Apple-interchange-newline">My problem is that I need to have rabbitmq running on both node1 and node2.</div><div><span style="font-size: 12pt;">I also need the IP to fail over if rabbitmq were to fail on the current node.</span></div><div><br></div><div><span style="font-size: 12pt;">The 2 rabbitmq services are communicating with each other. </span></div><div><span style="font-size: 12pt;">Data is pushed to the clients. </span></div><div><span style="font-size: 12pt;"><br></span></div><div><span style="font-size: 12pt;">Even though the IP may currently live on node1, data may flow through node1 then through node2 (via rabbit) and out to client.</span></div><div><br></div><div><span style="font-size: 12pt;"> Rnode1 -------> client1</span></div></div><div><span style="font-size: 12pt;"> / /|\</span></div><div><span style="font-size: 12pt;">DB---->VIP |</span></div><div><span style="font-size: 12pt;"> \|/</span></div><div> Rnode2 --------> client2</div><div><span style="font-size: 12pt;"><br></span></div><div><span style="font-size: 12pt;"><br></span></div><div><div><br></div><div>Maybe I should not have these resources grouped together since that implies collocation infinity for IP and rabbitmq?</div></div><div><br></div><div><br></div><div>Steve</div><div><span style="font-size: 12pt;"><br></span></div><div><span style="font-size: 12pt;"><br></span></div><div>From: andrew@beekhof.net<br>Date: Tue, 18 Mar 2014 11:44:34 +1100<br>To: pacemaker@oss.clusterlabs.org<br>Subject: Re: [Pacemaker] Don't want to stop lsb resource on migration<br><br><pre> <br>On 14 Mar 2014, at 1:00 am, Bingham <knee-jerk-reaction@hotmail.com> wrote:<br> <br>> Hello,<br>> <br>> My setup:<br>> I have a 2 node cluster using pacemaker and heartbeat. I have 2 resources, ocf::heartbeat:IPaddr and lsb:rabbitmq-server. <br>> I have these 2 resources grouped together and they will fail over to the other node.<br>> <br>> <br>> <br>> question:<br>> When rabbitmq is migrated to node1 from node2 I would like to 'not' have the the </etc/init.d/rabbitmq-server stop> happen on the failed server (node1 in this example).<br> <br>'migrate' has special meaning here.<br>After a failure rabbitmq is moved (stopped on the old node and started on the new one), which is different from a migration.<br> <br>Leaving rabbitmq in an unclean state on node1 would definitely not be a good idea.<br> <br>> <br>> Is it possible to do this in crm? <br>> <br>> I realize that I could hack the initscript's case statement for stop to just "exit 0", but I am hoping there is a way to do this in crm.<br>> <br>> <br>> Thanks for any help,<br>> Steve<br>> <br>> <br>> _______________________________________________<br>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>> <br>> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br> <br></pre><br>_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org</div> </div></body>
</html>