Re: max_binlog_size - too small?
Posted by: Rick James
Date: October 10, 2014 11:04AM

> Does that indicate that the binlog_size is too small

A binlog must not exceed 4GB (or maybe 2GB).
A binlog stops growing as it inserts the record that takes it beyond the limit. Hence, most binlogs will be bigger than the limit stated.
In general, binlog size does not matter.
expires_logs_days does not kick in until a new binlog is being created. Hence, you may see a big jump or decline in disk space usage at that time.

> (as well as the innodb_log_file_size)? Would it help to use a bigger binlog_size?

innodb_log_file_size (for transactions stuff) has nothing to do with the binlog (for replication). I recommend adjusting that setting to make
Uptime / 60 * innodb_log_file_size / Innodb_os_log_written
be about 60. It represents the minutes between rotation of the logs. 10 minutes is OK; 10 hours is OK. 1 minute is bad because it is stopping to clean up things too often. 10 days means the log files are wasting disk space.

> The binlog is rotated every 15 minutes during peak times. Could that be performance penalty?

Rotation is quite cheap.
However, 2GB/hour is huge! What are you doing? Or do you accidentally have the server_ids set to the same value on Master and Slave. (Huge replication traffic is the only symptom or harm I know of for this mistake.)

Also SELECT this, to see the average milliseconds:

Options: ReplyQuote

Written By
October 08, 2014 05:21AM
Re: max_binlog_size - too small?
October 10, 2014 11:04AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.