Nico Sabbi wrote:
[...]
There are 3 GB of logs that no one needs anymore. Since the master knows that all
the slaves are correctly aligned up to a certain MASTER_LOG_POS, can't
it automatically remove the logs up to that position?
The problem here is that MySQL masters aren't necessarily aware of all their slaves, so it has no way of telling if they're all caught up with the replication.
The best way to solve this problem is to write a Perl script to connect to each slave periodically and check the current log, and then purge all the logs previous to the least-caught-up slave's current log.
-- Alex
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
