On Thu, May 10, 2001 at 03:51:59PM -0400, Chris Foreman wrote:
>
> I would like to use MySQL for a high-availability application
> (available 24 hours per day, 7 days per week) using replication to
> minimize down times. The volume of transactions will be about one
> million per week. Can anyone share experiences with me about
> high-availability applications with MySQL and use of database
> replication in MySQL?
My experience is roughy this:
The primary (master) is a dual cpu P3-850 with 1GB of RAM and about
100GB of disk space. It's currently running 3.23.29 (as noted in my
sig) and has been up for the last 130 days. It's handled over 800
million queries in that time (roughly 10% of which are update/insert
queries).
We have two slaves which replicate the full set of data (and two
more which get a specific subset), but I've not had to switch to one
yet. The last time the server was down was because I was upgrading
from an earlier release of MySQL, and I can now do that in about 10
seconds with a simple shell script. That keeps me pretty close to
24/7 uptime.
The only times before that, the server was down because of hardware
problems and I hadn't yet fully configured replication--I was still
experimenting with it.
One of these days, I should really prune the binary logs on that
server. They're getting sorta big...
Jeremy
--
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 439-9951
MySQL 3.23.29: up 130 days, processed 804,802,515 queries (71/sec. avg)
---------------------------------------------------------------------
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
