On Thu, Aug 07, 2003 at 03:22:58PM -0700, Ian Neubert wrote:
> 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.

Right.

> 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 :)

Well, what you end up finding is that eliminating all points of
failure it very, very, very difficult (and expensive).  But you can
try to architect things so that they're still affordable and provide
minimal downtime in the event of a failure.

> 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) :)

Yeah.  And there are no upcoming tour dates. :-)

> Do you bother with multi-masters?

Sometimes.  It's up to each group to think about the tradeoffs of
multi-master vs. master/slave with a switch-over plan.

> How do you ensure redundancy on the write/master server?

One thing you can do is have a "backup master" that slaves from the
master but doesn't get other work to do.  If it has hardware as beefy
as the master, then switching isn't *too* painful.  Many of our groups
are using that model today.  But others do not.

If you want to go into a lot more detail off-list, let me know.  We
might be able to arrange something...

Jeremy
-- 
Jeremy D. Zawodny     |  Perl, Web, MySQL, Linux Magazine, Yahoo!
<[EMAIL PROTECTED]>  |  http://jeremy.zawodny.com/

MySQL 4.0.13: up 6 days, processed 213,085,838 queries (398/sec. avg)

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to