The problem isn't so much with the failover. It's with data integrity. Binlogs control replication. You can place a failover master in between the master and slaves. In the event of a master failure, you eliminate the loss of writes by directing them to the failover. If you lose your failover, the binlogs can be completely different thus pointing the slaves to the master is useless.
The binlog position is the real problem. Since binlogs are stored with their byte position as the indicator instead of a unique value passed on from the master, there's no easy way of finding the position you were just at. Is is possible to write two binlogs? One to the local disk, one to a network device? -J -----Original Message----- From: Daniel Koch [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 11:47 AM To: Jeremy Tinley Cc: [EMAIL PROTECTED] Subject: Re: HA of MySQL On Mon, 2002-10-07 at 10:30, Jeremy Tinley wrote: > Howdy, > > There has been some interest lately in HA of MySQL services both in my > company and on the list. A few of us here sat down on Friday (at 5PM no > less) and started hashing out the details of providing such a service. > Following several possible approaches, we ran into major stumbling > blocks on each path. > You might check with these guys, who have a similar project: http://mysql-ha.sourceforge.net/ --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
