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

Pantheon database will not pull due to size of BLOB/TEXT data #313

Closed
Senpai opened this issue Sep 1, 2017 · 2 comments
Closed

Pantheon database will not pull due to size of BLOB/TEXT data #313

Senpai opened this issue Sep 1, 2017 · 2 comments
Assignees
Labels
bug Something aint working right!
Milestone

Comments

@Senpai
Copy link
Contributor

Senpai commented Sep 1, 2017

Error noted during lando pull:

Pulling database...
ERROR 1118 (42000) at line 11645: 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.
@Senpai Senpai added the bug Something aint working right! label Sep 1, 2017
@Senpai Senpai self-assigned this Sep 1, 2017
@pirog pirog added this to the 3.0.0-rc.1 milestone Sep 2, 2017
@pirog
Copy link
Sponsor Member

pirog commented Sep 2, 2017

@Senpai i was able to replicate this. Boosting log size to see if that helps.

@pirog
Copy link
Sponsor Member

pirog commented Sep 2, 2017

@Senpai yeah boosting the log size seems to work for me, we should definitely default our config to the "does it work" side of things so im going to roll out a fix to bump the log size.

That said its probably also worth investigating why such a large single transaction exists in the database to begin with since im guessing such a thing might manifest itself in other ugly ways. Probably worth pinging @reynoldsalec on that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something aint working right!
Projects
None yet
Development

No branches or pull requests

2 participants