MySQL binlog administration

If you look into the key elements of replication, then the very basic element is Binary log or binlog. Over the period of time we have made efforts to improve the management of this quintessential element of replication. To keep up with our raising standards and requirements coming from the global MySQL community we have introduced two new features to help you manage your binary logs more efficiently.

    1. RESET MASTER TO X:
      This was a community patch contributed by Daniël van Eeden (see BUG#77482). The goal was to introduce a new parameter in RESET MASTER command where you can specify the index number you would like to start your binary log from, and the old behavior shall remain the same, which is if no extra option is provided to RESET MASTER start the binary log index from 000001. The range of values X takes is [1, 2^31 – 1], both inclusive.
      Read more about the usage in the documentation.

    2.  binlog_expire_logs_seconds:
      This was a feature request by Simon Mudd (see BUG#71697).
      The goal behind this was to be able to set the retention policies of binary logs to a value smaller than one day so that the storage footprint of binlogs can be lowered and at the same time enable setting the expire period which need not be an integral multiple of days like 1 day 2 hours and 32 minutes. A new global server variable binlog_expire_logs_seconds is introduced in addition to the existing expire_logs_days variable. This new variable as the name suggest accepts the expire time in seconds which fulfill both goals discussed above.

We are improving day by day with more new features being added to the Server code and refinements being done to the existing code. All of this wouldn’t have been possible without the support of our awesome MySQL community, and many thanks for contributing. We value contributions very much, so feel free to submit and watch them become part of a MySQL release. Processing a contribution is not as simple as just merging the proposed patch in. It still requires design and code reviews of the proposed changes. Granted, the life of a contribution is not always straightforward but is always fun. You can read more about the process of contributing to MySQL and the story of one contribution .

A BIG THANK you.

Leave a Reply

Your email address will not be published. Required fields are marked *

Please enter. * Time limit is exhausted. Please reload CAPTCHA.