I have binary logging set up for master / slave replication from MySQL 5.5 to Percona 5.5. It was working fine for over a month, but a couple of days ago (April 12) the server ran out of drive space due to a sudden increase in binary log file growth on the master. It went from a few 100 MB log files per day to a few per minute. The ibdata file hasn’t shown the same rate of growth, holding steady at around 20 GB. I reviewed the error logs on the master and saw that it started producing the error below on April 6th. After some research I changed the innodb_log_file_size config to 256M. Previously it was at the default value. I restarted the server but soon started seeing the same problem of high log file growth rate. At this point I’ve shut down logging (and replication) for fear of running out of drive space again.
At this point I’m not sure how to proceed and am reaching out for suggestions. Googling the problem didn’t yield much. It seems odd that the log files would grow at such a high rate while the ibdata file wouldn’t. The log files were adding the equivalent of the total ibdata file size every hour.
130406 17:56:39 InnoDB: ERROR: the age of the last checkpoint is 9435301, InnoDB: which exceeds the log group capacity 9433498. InnoDB: If you are using big BLOB or TEXT rows, you must set the InnoDB: combined size of log files at least 10 times bigger than the InnoDB: largest such row.