On 14 Mar 2014, at 1:00 am, Bingham <knee-jerk-react...@hotmail.com> wrote:
> Hello, > > My setup: > I have a 2 node cluster using pacemaker and heartbeat. I have 2 > resources, ocf::heartbeat:IPaddr and lsb:rabbitmq-server. > I have these 2 resources grouped together and they will fail over to > the other node. > > > > question: > 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). 'migrate' has special meaning here. After a failure rabbitmq is moved (stopped on the old node and started on the new one), which is different from a migration. Leaving rabbitmq in an unclean state on node1 would definitely not be a good idea. > > Is it possible to do this in crm? > > 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. > > > Thanks for any help, > Steve > > > _______________________________________________ > 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
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ 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
