I have a fairly complicated one-way replication set-up, whereby we have multiple master servers and multiple slaves, all replicating unrelated databases from one to another.
It's set up and works, but not reliably. Pretty much every day I come into work to find one machine is no longer replicating, or there are inconsistencies in the replicated data. In fact, it's gotten so complicated that I had to write a PHP script to monitor each of the 8 masters/slaves to see bin-log numbers and slave status! Does anyone on the list have a decent web-based management tool for MySQL replication? I am also looking for suggestions on the following topics: 1) Binary log management. We often get binlogs in the 1GB range after only a day's transactions. I really need to figure out an easy, painless process to rotate these out without losing updates, which leads to 2)... 2) Re-syncing tables. After a failure of replication, I need to figure out how to easily re-sync the tables in a database. I'd really like to run a batch job nightly to re-sync without screwing up replication. But we're talking 40 tables or so in some cases. 3) Optimizing binlogs in the form of table restriction. I only want to replicate very specific tables on the master, but from what I can tell from the documentation, the "binlog-do-db" command from /etc/my.cnf allows you to only specify a single database - you can't have multiple "binlog-do-db" commands like the other commands. Is there anything I can do? We're running various versions - 3.23.38 through 3.23.43 - under FreeBSD 4.4. --------------------------------------------------------------------- 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
