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.

Sign up for GitHub

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

Jump to bottom

Bug Report: innodb_log_buffer_size #352

Open
kochetovd opened this issue Sep 27, 2024 · 2 comments
Open

Bug Report: innodb_log_buffer_size #352

kochetovd opened this issue Sep 27, 2024 · 2 comments

Comments

@kochetovd
Copy link
Collaborator

image

Bug Report: innodb_log_buffer_size
I’ve also encountered an issue with the innodb_log_buffer_size recommendation. The current value is 2147479552, and the recommended value is 2147483648. However, I’m unable to apply the recommended value, either manually or through Releem’s automation. While larger values can be applied successfully, this specific integer seems un-applicable. I’ve tried manually setting it both in the configuration file and through the MariaDB console without success.
@kochetovd
Copy link
Collaborator Author

Created an issue https://jira.mariadb.org/browse/MDEV-35010 and got an answer

Even though the parameter is unsigned, its maximum value has been declared as LONG_MAX (0x7fffffff) at least since MySQL 5.5. That value is being adjusted further down from to 2147479552 (0x7ffff000), because the parameter must be a multiple of 4096 bytes.

@kochetovd
Copy link
Collaborator Author

Fixed recommendation of innodb_log_buffer_size variable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kochetovd