Proper comment on why changing innodb_log_file_size breaks the system

This commit is contained in:
Jasper N. Brouwer
2017-06-28 21:55:44 +02:00
parent e51a980af1
commit ef67883ab2
2 changed files with 6 additions and 4 deletions

View File

@@ -45,7 +45,7 @@ mysql_thread_concurrency: 2
# InnoDB settings.
mysql_innodb_file_per_table: '1'
mysql_innodb_buffer_pool_size: "{{ (ansible_memtotal_mb * 0.2) | round | int }}M"
mysql_innodb_log_file_size: '64M'
mysql_innodb_log_file_size: '64M' # If this setting changes on a running system, you will break it! http://dev.mysql.com/doc/refman/5.6/en/innodb-data-log-reconfiguration.html
mysql_innodb_log_buffer_size: '8M'
mysql_innodb_flush_log_at_trx_commit: '1'
mysql_innodb_lock_wait_timeout: 50