16 messages in com.mysql.lists.mysqlRE: MySQL Replication
FromSent OnAttachments
Ian Neubert07 Aug 2003 11:26 
Dathan Vance Pattishall07 Aug 2003 12:53 
Dathan Vance Pattishall07 Aug 2003 12:58 
Ian Neubert07 Aug 2003 12:59 
Dathan Vance Pattishall07 Aug 2003 13:33 
Ian Neubert07 Aug 2003 14:01 
Jeremy Zawodny07 Aug 2003 14:52 
Ian Neubert07 Aug 2003 15:22 
Jeremy Zawodny07 Aug 2003 15:38 
Adam Nelson08 Aug 2003 09:09 
System11 Aug 2003 04:25 
System11 Aug 2003 06:22 
yin11 Aug 2003 06:51 
Jeremy Zawodny11 Aug 2003 12:38 
Ian Neubert11 Aug 2003 13:16 
Michael Conlen11 Aug 2003 18:16 
Subject:RE: MySQL Replication
From:Ian Neubert (ia@TWAcomm.net)
Date:08/07/2003 03:22:36 PM
List:com.mysql.lists.mysql

Good question :)

I got a message from a person off the list that suggested I use network disk mirroring or a NAS/SAN/NFS system to handle that. I'm not sure if the mirroring would be 100% perfect, but the NAS/SAN solution should as either server would be reading and writing to the same physical data.

But, then I have another point of failure. Heh.

I realize that creating the perfect HA system is probably the most difficult thing to do, and doesn't come cheaply either. However, I'm going to think it through and try anyway :)

I've read your presentations on your website and have used that info for my plan here, but its a little difficult to get details from just the slides (as you even mentioned on your site) :)

Do you bother with multi-masters? How do you ensure redundancy on the write/master server?

....................... Ian Neubert Director of IS TWAcomm.com, Inc. http://www.twacomm.com/

-----Original Message----- From: Jeremy Zawodny [mailto:Jer@Zawodny.com] Sent: Thursday, August 07, 2003 2:53 PM To: Ian Neubert Cc: Dathan Vance Pattishall; mys@lists.mysql.com Subject: Re: MySQL Replication

On Thu, Aug 07, 2003 at 01:00:12PM -0700, Ian Neubert wrote:

I was trying to design it so that the slaves wouldn't know they had connected to a different master, as they both masters would have the same IP address that gets failed over based on the Linux Virtual Server software and VRRP (like heartbeat from Linux-HA).

That path is a very, very, very difficult one.

How can you absolutely guarantee that each master's binlog will be indentical in name, size, and content?

If you can't, this scenario really falls apart.

(I've suggested enhancements to MySQL that would fix this but don't know if they're terribly high on the priority list...)

Jeremy

-- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <Jer@Zawodny.com> | http://jeremy.zawodny.com/

MySQL 4.0.13: up 6 days, processed 212,501,412 queries (399/sec. avg)

-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=ia@twacomm.net