[MDEV-13188] Implement max_binlog_files directive from Percona Created: 2017-06-27 Updated: 2023-06-05 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Onni Hakala | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 4 |
| Labels: | None | ||
| Description |
|
Currently there's no way to prevent the huge size of binarylogs which are generated in a short period of time. In our case we use binlog for MASTER-SLAVE replication and a high traffic weekend filled up the diskspace in the master server. Percona has implemented max_binlog_files directive which can be used to ensure the maximum disk usage of binarylogs with conjunction with max_binlog_size directive. See more: https://www.percona.com/doc/percona-server/LATEST/flexibility/max_binlog_files.html |
| Comments |
| Comment by Nicolas Payart [ 2018-01-04 ] |
|
Before working on this feature (which is a real progress I think), you should consider the following issue opened on Percona bug tracker: https://jira.percona.com/browse/PS-275 I do not know if this is relevant but the author mentions some drawbacks using max_binlog_files variable and suggest a variable max_binlog_space or binlog_space_limit instead. |
| Comment by COUNOTTE CEDRIC [ 2023-06-05 ] |
|
This would be a useful option! Be it max_binlog_files or binlog_space_limit. |