I'll go for the automatic solution. Thanks for the help. -----Original Message----- From: Andrew Beekhof [mailto:and...@beekhof.net] Sent: Wednesday, February 20, 2013 10:50 AM To: The Pacemaker cluster resource manager Subject: Re: [Pacemaker] Monitor process, migrate only ip resources
On Wed, Feb 20, 2013 at 8:07 PM, Grant Bagdasarian <g...@cm.nl> wrote: > Yes, you are correct. I manually stopped kamailio and messed with its config > script so it would not start again. > The resources were migrated to the secondary node =). Awesome piece of > software! > > So in theory I now have a broken primary server which I should fix. Once > fixed, how will the resources be migrated back to the primary again? Does > heartbeat take care of this or do I need to instruct heartbeat to do stuff? You can either clear the error manually (crmsh has a cleanup command) or set failure-timeout to have the cluster do it automagically after a period of time. > > -----Original Message----- > From: Florian Crouzat [mailto:gen...@floriancrouzat.net] > Sent: Wednesday, February 20, 2013 9:46 AM > To: pacemaker@oss.clusterlabs.org > Subject: Re: [Pacemaker] Monitor process, migrate only ip resources > > Le 20/02/2013 09:07, Grant Bagdasarian a écrit : >> 3)When I only stop the kamailio process on the primary node, the >> process is restarted again. Which is also good, but I thought it >> would migrate everything to the secondary node when the kamailio process >> stopped. >> > > Pacemaker always tries to restart a failed resources on it's original hosting > node. > Only if it fails to do so it will migrate the resource(s) to another node. > >> If there is something wrong on the primary node which causes the >> kamailio process to keep crashing and restarting, it could be a >> hazard for our production environment. >> > > I guess the question is: is failcount incremented when a failed > resource > *is* restarted on the same node and no transition occurs . > > > -- > Cheers, > Florian Crouzat > > _______________________________________________ > 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 > > _______________________________________________ > 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 _______________________________________________ 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 _______________________________________________ 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
