-
-
Notifications
You must be signed in to change notification settings - Fork 276
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
Set limits on binlog size #233
Milestone
Comments
AMecea
added a commit
that referenced
this issue
Feb 18, 2019
AMecea
added a commit
that referenced
this issue
Feb 19, 2019
AMecea
added a commit
that referenced
this issue
Feb 19, 2019
AMecea
added a commit
that referenced
this issue
Feb 20, 2019
AMecea
added a commit
that referenced
this issue
Feb 20, 2019
AMecea
added a commit
that referenced
this issue
Feb 20, 2019
chapsuk
pushed a commit
to chapsuk/mysql-operator
that referenced
this issue
Oct 16, 2023
Signed-off-by: Alkin Tezuysal <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should set the following variables with sensible defaults:
This takes into consideration:
max_allowed_packet
: 4MB in 5.7 and 64MB in 8.0max_binlog_size
: no less than fewmax_allowed_packet
(eg. 2x)binlog_space_limit
: no less than fewmax_binlog_size
(https://www.percona.com/doc/percona-server/5.7/flexibility/max_binlog_files.html#binlog_space_limit)Considering the minimum requirements (
max_binlog_size
= 2 *max_allowed_packet
,binlog_space_limit
= 2 *max_binlog_size
) there is at least a 256MB requirement for binlog.The text was updated successfully, but these errors were encountered: