mysql - can't resize innodb_log_file_size in my.cnf -



mysql - can't resize innodb_log_file_size in my.cnf -

i have mysql 5.0 sonar database bloated (360gb instead of on average 30gb)

this link said in order prepare need export db, install mysql 5.6, import , export, , should go original size..: sonarqube : how cut down size of measures_data.ibd?

so got virtual machine test, installed centos 5.6 , , mysql 5.6, , started import... unfortunately errors in of imports...

[error] innodb: total blob info length (39220742) greater 10% of redo log file size (3072). please increment innodb_log_file_size.

which brought me many links of innodb_log_file_size one: issue changing innodb_log_file_size

i shut downwards mysql without errors. modify my.cnf

innodb_log_file_size=64m (for illustration purposes although tried much higher values seek 600m 6g etc..)

i deleted ib_logfile0 , ib_logfile1 logs in /var/lib/mysql restarted service , nil changes.. (even though read shouldnt matter in 5.6)

2014-10-09 13:05:09 18205 [note] innodb: completed initialization of buffer pool

2014-10-09 13:05:10 18205 [note] innodb: setting log file ./ib_logfile101 size 48 mb

2014-10-09 13:05:10 18205 [note] innodb: setting log file ./ib_logfile1 size 48 mb

2014-10-09 13:05:10 18205 [note] innodb: renaming log file ./ib_logfile101 ./ib_logfile0

2014-10-09 13:05:10 18205 [warning] innodb: new log files created, lsn=36443469334

i truncated table info after failed import , altered each of them compressed key_block_size 8k. removed "drop table if exists" backup i'm importing maintain tables compressed, didn't work either...

active_rule_changes | innodb | 10 | compressed | 379 | 86 | 32768 >| 0 | 8192 | 0 | 566 | 2014-10-08 18:03:45 | null | >null | utf8_bin | null | row_format=compressed key_block_size=8 | |

i'm not sure do... log doesnt error, , read, should straightforward.

heres my.cnf file info import.

innodb_file_per_table = 1

innodb_file_format = barracuda

innodb_file_format_max = barracuda

innodb_file_format_check = on

ideas appreciated. thanks.

one mutual problem people experience have more 1 line in /etc/my.cnf defining variable. last line defining variable in file wins. search config file line sets log file size 48m.

another possibility set variable definition in wrong group. belongs under [mysqld] grouping in config file.

fwiw, don't need export , import data, unless need shrink ibdata1 tablespace.

you can compact individual .ibd file using optimize table.

mysql sql database innodb

Comments

Popular posts from this blog

c - Compilation of a code: unkown type name string -

java - Bypassing "final local variable defined in an enclosing type" -

json - Hibernate and Jackson (java.lang.IllegalStateException: Cannot call sendError() after the response has been committed) -