What is my innodb_log_file_size goes beyong 2gb

Question

What is my innodb_log_file_size goes beyong 2gb

.

.

.

Answer 1

Hi @GeethaT-2444 ,

Welcome to Microsoft Q&A forum.

As I understand, you want to know if innodb_log_file_size can go beyond 2GB in Azure Database for MySQL.

The value of innodb_log_file_size is the size (in bytes) of each log file in a log group. The combined size of log files (innodb_log_file_size * innodb_log_files_in_group) can't exceed a maximum value that is slightly less than 512 GB.

A bigger log file size is better for performance, but the drawback is that the recovery time after a crash is high. You need to balance recovery time for the rare event of a crash versus maximizing throughput during peak operations. A bigger log file size can also result in longer restart times.

You can configure innodb_log_size to 256 megabytes (MB), 512 MB, 1 GB, or 2 GB for Azure Database for MySQL - Flexible Server. The parameter is static and requires a restart.

Note

If you changed the innodb_log_file_size parameter from the default, check if the value of show global status like 'innodb_buffer_pool_pages_dirty' stays at 0 for 30 seconds to avoid restart delay.

Hope this helps.

Let us know if you have further queries.

Thanks