Or look at how old your one binlog is, and how big it is. Do a little arithmetic to see the avg bytes per day; set max_binlog_size to that.
Expire-logs probably only deletes old binlogs, and does not split any binlogs. So what you have now will not really do anything until you have 2 binlogs, and the older one is > 7 days old. That may not happen for months. Even with the FLUSH you asked about, the expire may not kick in until 14 or more days. > -----Original Message----- > From: Nitin Mehta [mailto:ntn...@yahoo.com] > Sent: Thursday, May 03, 2012 4:20 AM > To: mysql@lists.mysql.com > Subject: Re: master BIN-LOG maintenace > > Hi Charles, > > I guess your application doesn't generate too much of binary logs. The > parameter "expire-logs-days" kicks in at the flush but does not > necessarily require a manual "flush logs" command. You can reduce the > value of "max_binlog_size" to make sure that at least one new file is > created daily and this will force mysql to check and delete old bin- > logs. The default (and maximum) value for this variable is 1G. If I'm > not wrong, it is a dynamic variable, which means you can try different > values without a restart of the database until you find a suitable one. > > Hope that helps! > > Regards, > > > ________________________________ > From: "Brown, Charles" <cbr...@bmi.com> > To: Nitin Mehta <ntn...@yahoo.com> > Cc: "mysql@lists.mysql.com" <mysql@lists.mysql.com> > Sent: Thursday, May 3, 2012 4:24 PM > Subject: master BIN-LOG maintenace > > Hi Gurus, > > I would like to set BIN-LOG maintenance procedure for my master. The > master is on a windows platform. I’m all for make it simple and clean > therefore I’ve been leaning toward the automatic BIN-LOG removal > “expire-logs-days=7”. The problem is for this option to work, it should > be preceded by a “BIN-LOG FLUSH” command. Okay, where do I go from here > in order to make this work. Please help me. > > Thanks > > > ******************************************** > This message is intended only for the use of the Addressee and may > contain information that is PRIVILEGED and CONFIDENTIAL. > > If you are not the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. > > If you have received this communication in error, please erase all > copies of the message and its attachments and notify us immediately. > > Thank you. > ******************************************** -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
