[MDEV-29195] relay_log_purge variable not very useful Created: 2022-07-28  Updated: 2023-06-06

Status: Open
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.5.16
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Xan Charbonnet Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-31404 Implement binlog_space_limit In Testing

 Description   

I have a backup slave server, where I take regular snapshots of the database via LVM.

By default, with relay_log_purge enabled, the relay log files get deleted as soon as the server has processed them. I thought it might be handy to hang onto them, in case they were useful if the need to restore from these snapshots ever arose, so I disabled relay_log_purge.

I was expecting the relay log files to be automatically deleted once relay_log_space_limit was hit, but instead once that limit was hit, new relay logs stopped being written and replication ground to an ugly halt.

It seems to me that the behavior should be to cycle out old relay logs when relay_log_space_limit is hit, or if that is unset, when the partition fills up. That would allow me to keep as much relay log "as possible" while also not having to manually (is that even possible/recommended?) delete old log files.



 Comments   
Comment by Xan Charbonnet [ 2022-08-14 ]

The solution here might end up being related to the solution for MDEV-29196.

Generated at Thu Feb 08 10:06:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.