Bobcares

MySQL set binlog_expire_logs_seconds | Guide

by | Nov 22, 2023

Learn how to set binlog_expire_logs_seconds in MySQL. Our MySQL Support team is here to help you with your questions and concerns.

MySQL set binlog_expire_logs_seconds | Guide

Managing MySQL binary logs is a key part of database administration, enabling data recovery, replication, etc.

MySQL set binlog_expire_logs_seconds | Guide

Today, we are going to take a walk through setting up up and optimizing MySQL binary logs, including configuring settings, granting privileges, and automating log purging.

  1. First, we have to update the MySQL configuration to enable binary logs. To do this, head to the MySQL config file and make sure these settings are under the [mysqld] section:

    [mysqld]
    server_id = 1
    log_bin = /var/log/mysql/mysql-bin.log
    max_binlog_size = 100M
    binlog_format = mixed

    Furthermore, we have to add the following for MySQL 8+:

    binlog_expire_logs_seconds = 864000

    And add this for MySQL 5:

    expire_log_days = 10

  2. Now, it is time to use the new feature ‘binlog_expire_logs_seconds’ by setting the expiration time. This feature is useful for setting expiration periods that aren’t integral multiples of days.
  3. Then, create a MySQL user with replication capabilities. We can do this by running this command:

    mysql> GRANT REPLICATION SLAVE ON *.* TO 'mysqluser'@'%';

  4. Then, it is time to restart the MySQL server to apply the changes:

    sudo service mysql restart

Furthermore, we can change ‘expire_logs_days’ without restarting the server with these steps:

  1. Check the current setting in MySQL:

    mysql> show variables like 'expire_logs_days';

  2. Then, change the global setting:

    mysql> set global expire_logs_days=1;

  3. After that, update the my.cnf file to make the setting permanent:

    sudo vim /etc/my.cnf
    expire_logs_days = 1

  4. Finally, flush the logs for the changes to take effect:

    mysql> flush binary logs;

Additionally, we can automatically purge MySQL binary logs based on time by adding the ‘binlog_expire_logs_seconds’ variable to our configuration file:

binlog_expire_logs_seconds = 259200

Let us know in the comments if you need further help with configuring MySQL Binary Logs.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to set binlog_expire_logs_seconds in MySQL.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

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

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF