> -----Original Message----- > From: Gavin Towey [mailto:gto...@ffn.com] > Sent: Friday, July 17, 2009 2:02 PM > To: Gary Smith; Todd Lyons > Cc: mysql@lists.mysql.com > Subject: RE: Slave log files going nuts... > > The binlogs are closed and reopened every time you do a FLUSH LOGS; > command, or when the server restarts. Is your server crashing > continuously? Take a look at your error log as well. > > Regards, > Gavin Towey
Gavin/Todd, Tracking it down, the timestamp correlates with a mysqldump that I have a crontab for which of course, has flush-logs. /usr/bin/mysqldump --opt --flush-logs --all-databases --result-file=$FILENAME I'm not sure if we want to flush the log files on this machine at this point. It's a tossup since there are multiple slaves hitting this guy replicating only specific tables in some cases. I would guess that we could always restore the entire backup and dump what we want across to a new server before starting the incremental replication, but I'm still working that plan up right now. Anyway, thanks for the pointers to indentify the problem. Gary -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org