Comments on: Implementing High Availability in MySQL

By: links for 2008-07-25 « Brent Sordyl’s Blog

links for 2008-07-25 « Brent Sordyl’s Blog — Fri, 25 Jul 2008 14:31:20 +0000

[...] Implementing High Availability in MySQL Heartbeat is a piece of software that provides High Availability features such as monitoring the availability of the machines in the cluster, transferring the virtual IPs (tags: mysql ha) [...]

By: anonymous

anonymous — Tue, 17 Jan 2006 12:54:18 +0000

ok thank you for the help…

i already followed the steps in this link:
http://www.karkoma.info/index.php/2004/01/24/implementing-high-availability-in-mysql/

and i was able to replicate from the master(server1)
to slave (server2).
i stopped heartbeat of server1 and the server2 took
over.
i updated the database in server2.
then i started the heartbeat in server1.
when i checked the databases in server1, it is not
updated.

how do i replicate from server2 to server1? in which
case, server2 is now the active server.

is it possible to configure server2 so that it will
automatically act as the master when server1 is down?

and also, where can i see the log messages of
replication? i mean, not the binary log.

i hope you can help… thank you.

chEn

By: anonymous

anonymous — Sat, 23 Apr 2005 06:00:45 +0000

i have 2 questions about your implementation:

why don't you check slave_io_thread state before doing 'stop slave_io_thread'?
why don't you check 'Binlog dump' state before doing 'kill '?

thanks,

By: anonymous

anonymous — Sat, 19 Mar 2005 16:53:00 +0000

There is a small scrpit here that will allow you to do MySQL application level monitoring to cause the failover to occur. This is particuarly useful on systems that have unstable versions of MySQL. due to database design or whatever maybe the result.

exter_c

By: anonymous

anonymous — Fri, 08 Oct 2004 21:10:28 +0000

Hi there

Has anyone ever tried to set up a mysql-cluster using heartbeat and drbd? One could spare the replication between two database servers because whichever is active will use the shared data on the drbd-disk.

Well, I'm gonna try it anyways

florian.

By: anonymous

anonymous — Thu, 19 Aug 2004 18:50:52 +0000

its called two way replication by the mysql people:

BOX1 BOX2
MASTER -> SLAVE
SLAVE

gmillerd.

By: anonymous

anonymous — Thu, 19 Aug 2004 00:37:02 +0000

I have a page now for my development efforts on the aforementioned resource script:

http://www.workboy.com/charles/mysql-heartbeat cb

oddcast.

By: anonymous

anonymous — Tue, 13 Jul 2004 00:34:02 +0000

I am currently working on applying hearbeat with MySQL so that the two MySQLservers in a cluster pass back and forth their master role. I have been following the guidelines at the mysql.com site in the replication FAQ (http://dev.mysql.com/doc/mysql/en/Replication_FAQ.html). I created a resource.d script which is used to promote one of the two servers as the master and then signal the other server to become a slave to that server (there are only two servers in the cluster so it is easy enough to do this). Not ready for production yet, but pretty close.

I was dissapointed to see the number of failed starts to try and build MySQL HA. Hopefully this approach will produce a simple reliable solution.

oddcast.

By: anonymous

anonymous — Sat, 12 Jun 2004 07:37:31 +0000

I don’t really know if a master-master configuration is possible. All references I am aware of talk about having master-slave or master-many_slaves. In MySQL documentation once I read about something called circular replication, where servers act as slave and master at the same time.

By: anonymous

anonymous — Fri, 11 Jun 2004 19:17:52 +0000

Would one solution be to have a master master relationship?? or is that not
really possible - sure i read somewhere in the replication docs that you could
do this.

will.