Disabling Binary Logging (binlog) in MySQL 8 (Cloud IDE)

Overview

Binary logging (binlog) in MySQL enables replication and data recovery. If you do not require these features, disable binlog to improve performance and reduce disk usage. This article provides step-by-step instructions on how to disable binlog in MySQL 8 within the Cloud IDE.

Purging existing binary logs

If binlog is enabled, existing log files can consume significant disk space. You must manually purge these files.

To purge existing binlogs:

• To confirm that binlog is active and to identify the log files, run:

  copy

  drush sqlq "SHOW VARIABLES LIKE 'log_bin';"
  drush sqlq "SHOW BINARY LOGS;"

  The system displays log_bin ON.

• To purge all binlog files created before a specific file, such as binlog.000076, run: 

  copy

  drush sqlq "PURGE BINARY LOGS TO 'binlog.000076';"

This command removes all logs listed before the specified filename.

Disabling Binlog in Cloud IDE

To disable binlog in Cloud IDE:

• Edit the MySQL configuration file.

  copy

  /home/ide/configs/mysql/settings.cnf

• Locate the [mysqld] section in the file and add the following line to disable binlog:

  copy

  skip-log-bin

  For example:

  copy

  [mysqld]
  skip-log-bin

• Save your changes and close the configuration file.

• Restart the MySQL service to apply the changes. Run the following command:

  copy

  acli ide:service-restart mysql

• Run the following command to verify that binlog is disabled:

  copy

  drush sqlq "SHOW VARIABLES LIKE 'log_bin';"

  The following output is displayed:

  copy

  +---------------+-------+
  | Variable_name | Value |
  +---------------+-------+
  | log_bin       | OFF   |
  +---------------+-------+