Proper comment on why changing innodb_log_file_size breaks the system
parent
e51a980af1
commit
ef67883ab2
|
@ -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
|
||||
|
|
|
@ -63,11 +63,13 @@ thread_concurrency = {{ mysql_thread_concurrency }}
|
|||
# InnoDB settings.
|
||||
innodb_file_per_table = {{ mysql_innodb_file_per_table }}
|
||||
innodb_buffer_pool_size = {{ mysql_innodb_buffer_pool_size }}
|
||||
{# It craches after install (mysql 5.5)... TODO: FIX -> http://dev.mysql.com/doc/refman/5.6/en/innodb-data-log-reconfiguration.html #}
|
||||
#innodb_log_file_size = {{ mysql_innodb_log_file_size }}
|
||||
#innodb_log_buffer_size = {{ mysql_innodb_log_buffer_size }}
|
||||
innodb_log_buffer_size = {{ mysql_innodb_log_buffer_size }}
|
||||
innodb_flush_log_at_trx_commit = {{ mysql_innodb_flush_log_at_trx_commit }}
|
||||
innodb_lock_wait_timeout = {{ mysql_innodb_lock_wait_timeout }}
|
||||
{# If this setting changes on a running system, you will break it! #}
|
||||
{# See how tho change it here: http://dev.mysql.com/doc/refman/5.6/en/innodb-data-log-reconfiguration.html #}
|
||||
{# TODO FIX -> Maybe detect a change and fail, just to be safe? #}
|
||||
innodb_log_file_size = {{ mysql_innodb_log_file_size }}
|
||||
|
||||
[mysqldump]
|
||||
quick
|
||||
|
|
Loading…
Reference in New Issue