Aaron Stone wrote:
[enable soapbox]
If you *must* have five 9's, then you need to get a *budget* for five 9's.
[set soapbox=off]
Hear, hear.
With a imap mail-system you can maybe afford 99. uptime in a moderately
buzzy company net before the heat starts coming down. But even with
fully internet-connected public dbmail deployments 99.99 (<1 hour
downtime per annum) would seem more than exceptable. I bet even hotmail
has a hard time getting any such rating. Always nice to dream*cough*
envision excellence though.
Aaron
On Thu, 1 May 2003, Michael Shuler wrote:
From what I can tell MySQL can only have one master server that can take
writes but many slave replicating servers that can be used for reads. If I
can only write to one then I would think to optimize performance I would
want to only write to the master and do all my SELECTs to a cluster of slave
replicating servers. Does dbmail support using 2 or more different IPs for
reading vs. writing?
Any suggestions on how to handle a master MySQL server failing and having a
slave automatically taking over as master, or being able to write to any of
the MySQL servers in the cluster? I'm trying to build a 99.999% (or better)
uptime system. Oracle will let you write to any server in the cluster so
you can use a Foundry switch or any layer 4 solution to load balance and
handle failover..their SQL solution is awesome but at about $100K it is way
out of my reach. Any suggestions would be VERY appreciated.
Mike
PS: Before I get told to look at the message archives Yes, I looked at them
but I never actualy saw any specific answers.
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
________________________________________________________________
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlands________________________________http://www.nfg.nl
