relay log file maintenance problem

2004-11-29 Thread Bill Thomason

I have a replication server that is running out of disk space because of
old relay binary log files.

Both it and the master server are version 4.0.20.

I have a cron script that maintains a 3 day history of binary log files
on the master server.

Has someone figured out a way to manage the number relay log files so
that someone doesn't have to check a replication server to see if the
filesystem for the MySQL data directory hasn't been filled by old relay
log files that haven't been accessed for some specified time?

Thanks in advance,
-bill 


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



Re: relay log file maintenance problem

2004-11-29 Thread Sasha Pachev
Bill Thomason wrote:
I have a replication server that is running out of disk space because of
old relay binary log files.
Both it and the master server are version 4.0.20.
I have a cron script that maintains a 3 day history of binary log files
on the master server.
Has someone figured out a way to manage the number relay log files so
that someone doesn't have to check a replication server to see if the
filesystem for the MySQL data directory hasn't been filled by old relay
log files that haven't been accessed for some specified time?
Bill:
Doublecheck to make sure your SQL thread is running ( SHOW SLAVE STATUS). Relay 
logs should get deleted as soon as they are processed by the SQL thread. Another 
potential problem - if you do not change the default config, and leave less than 
1 GB for the relay log partition you will have a problem. Either put them on a 
bigger partition, or set max-relay-log-size to a lower value.


--
Sasha Pachev
Create online surveys at http://www.surveyz.com/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]