[MXS-770] Add "PURGE { BINARY | MASTER } LOGS" functionality Created: 2016-06-16 Updated: 2019-08-01 Resolved: 2017-08-07 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | binlogrouter |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Hareesh Haridas | Assignee: | Massimiliano Pinto (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | 2017-38 | ||||||||
| Description |
|
Please add support for PURGE { BINARY | MASTER }LOGS. This is important in managing the binary logs and disk usage. ~Hareesh |
| Comments |
| Comment by Massimiliano Pinto (Inactive) [ 2017-08-04 ] |
|
Added PURGE BINARY LOGS TO ‘file’; deletes all files in binlogdir and GTID mariadb10_slave_gtid=On option is needed in order to keep the list of Documentation update and usage examples will be part of next commits. Tested with mariadb10_master_gtid=On and binlog_structure=flat|tree Current binlog file cannot be deleted. Some cases: MySQL [(none)]> purge binary logs to 'mysql-bin.00011s3'; MySQL [(none)]> purge binary logs to 'fishy-bin.AA011s3'; MySQL [(none)]> purge binary logs to 'mysql-bin.000118'; |
| Comment by Massimiliano Pinto (Inactive) [ 2017-08-07 ] |
|
MaxScale/commit/113d2ad87a3352ff4a6d97a72c9d6dd3e6a711cd In 'develop' branch |