Shulou(Shulou.com)05/31 Report--

This article will explain in detail how to understand the redo log transaction log resizing in MySQL5.7. The content of the article is of high quality, so the editor will share it with you for reference. I hope you will have some understanding of the relevant knowledge after reading this article.

In previous versions of MySQL5.6/5.7, such as MySQL5.5, to modify the ib_logfile (redo log) size, the steps are as follows:

1) execute the set global innodb_fast_shutdown=0 command to write all dirty data to disk

2) execute the mysqladmin shutdown command to shut down the database

3) modify the innodb_log_file_size parameter value in the my.cnf file

4) execute the mv ib_logfile* bak command to move redo log to a different directory

5) execute the mysqld_safe-- defaults-file=/etc/my.cnf-- user=mysql & command, and finally start the MySQL service.

In the MySQL5.6/5.7 version, step 4 above can be ignored.

Note: if innodb_log_files_in_group is set to 3, then innodb_log_file_size*innodb_log_files_in_group cannot exceed 512GB

The higher the setting, the less often checkpoint refreshes dirty pages, which is important for MySQL performance and is usually set to around 4GB.

On how to understand the redo log transaction log resizing in MySQL5.7 to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.