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

Set limits on binlog size #233

Closed
calind opened this issue Feb 15, 2019 · 0 comments
Closed

Set limits on binlog size #233

calind opened this issue Feb 15, 2019 · 0 comments
Milestone

Comments

@calind
Copy link
Member

calind commented Feb 15, 2019

We should set the following variables with sensible defaults:

if PVC >= 2G:
    binlog_space_limit = 50% * PVC
    max_binlog_size = min(25% * `binlog_space_limit`, 1G)
else:
    max_allowed_packet = 4M
    binlog_space_limit = 33% * PVC
    max_binlog_size = min(33% * `binlog_space_limit`, 256M)

This takes into consideration:

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.

@calind calind added this to the 0.2.5 milestone Feb 15, 2019
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
@AMecea AMecea closed this as completed in 959692b Feb 21, 2019
chapsuk pushed a commit to chapsuk/mysql-operator that referenced this issue Oct 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants