On Mon, Apr 09, 2007 at 11:45:12AM -0400, Benjamin Lawetz wrote: > I'm upgrading my existing mysql replication to new servers and moving up > from heartbeat 1.x to 2.x > I've got the basics up and running and was reading up on the monitoring > feature. I'm a little confused so I just wanted to run this by you guys to > make sure I understood correctly: > > I have 2 mysql servers > Mysql1 192.168.1.4 > Mysql2 192.168.1.5 > I have a heartbeat that controls 2 virtual Ips: 192.168.1.6 (which has a > preffered node of mysql1) and 192.168.1.7 (which has a preffered node of > mysql2) > > I don't want hearbeat to control starting and stopping of mysql (these > services should always be running and are controlled by the OS).
That's what heartbeat can do for you as well. I can't imagine a reason to run them outside of the cluster if you want them HA. > But I do want heartbeat to monitor mysql and failover if the monitoring > fails. What would failover consist of then? > The way I understand how to configure this is that I have to add the mysql > ressource to my configuration but disable (or make them return that > everything proceeded correctly) the "start" and "stop" commands on the mysql > script so that start and stop does nothing but monitor functions correctly. > > Is this correct? > > Thanks in advance for your help > > -- > Benjamin > TéliPhone inc. > > > -------------- > N'envoyé pas de courriel à l'adresse qui suit, sinon vous serez > automatiquement mis sur notre liste noire. > [EMAIL PROTECTED] > Do not send an email to the email above or you will automatically be > blacklisted. > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems -- Dejan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
