Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase the redo log size using innodb_log_file_size #2

Closed
lmakarov opened this issue Nov 9, 2017 · 9 comments
Closed

Increase the redo log size using innodb_log_file_size #2

lmakarov opened this issue Nov 9, 2017 · 9 comments
Assignees

Comments

@lmakarov
Copy link
Member

lmakarov commented Nov 9, 2017

I was getting the following error when trying to import a database dump using docksal/db:1.1-mysql-5.6.

The size of BLOB/TEXT data inserted in one transaction is greater than 10% of redo log size. Increase the redo log size using innodb_log_file_size.

The issue and the solution is explained on stackoverflow

Setting innodb_log_file_size=128M solved the problem (the default value is 32MB).

This looks to be only affecting mysql-5.6, but not 5.5, 5.7 and 8.0 images. While all have innodb_log_file_size=32MB by default, only 5.6 needs innodb_log_file_size bumped up.

@lmakarov lmakarov self-assigned this Nov 9, 2017
@achekulaev
Copy link
Member

Stumbled upon this today

@tamnv
Copy link

tamnv commented Apr 4, 2018

I have same issue when execute fin sqli dev.sql. The size of file is up to 2.8G, I already increase the innodb_log_file_size in my.cnf to 512M but it doesn't solve issue. Do I miss other settings?

@achekulaev
Copy link
Member

achekulaev commented Apr 4, 2018

@tamnv did you make sure that your setting has applied?

show variables where Variable_name like "innodb_log_file_size";

@lmakarov should we release 1.2 with this change?

@ilux251
Copy link

ilux251 commented Apr 4, 2018

You have to restart your mysql service.

@achekulaev
Copy link
Member

Well yes, of course. I guess documentation states that you need to restart the project.

@tamnv
Copy link

tamnv commented Apr 6, 2018

@achekulaev
It doesn't apply the settings when we check show variables where Variable_name like "innodb_log_file_size"; I restart service fin restart db but It still doesn't change anything.

@lmakarov
Copy link
Member Author

lmakarov commented Apr 6, 2018

@tamnv you can now switch to the new docksal/db image, which have been just released:

docksal/db:1.2-mysql-8.0
docksal/db:1.2-mysql-5.7
docksal/db:1.2-mysql-5.6
docksal/db:1.2-mysql-5.5

If you are still experiencing issues with not being able to override mysql settings, then submit a separate issue in the main project.

@tamnv
Copy link

tamnv commented Apr 6, 2018

@lmakarov Thank you, It works with docksal/db:1.2-mysql-5.6

@achekulaev
Copy link
Member

achekulaev commented Apr 6, 2018

@tamnv I see the issue is fixed for you, but on my.cnf

It doesn't apply the settings when we check

This ^ means your my.cnf was not valid. You can check logs for details fin logs db, but most likely you did not include section.
E.g. https://github.com/docksal/drupal7/blob/master/.docksal/etc/mysql/my.cnf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants