Details
-
New Feature
-
Status: In Testing (View Workflow)
-
Critical
-
Resolution: Unresolved
-
None
Description
Original request:
We have a 130GB database, replicated to a backup cluster, and the binlog files consume 400GB of storage for a single day, without any option to reduce that to something more reasonable!
Implementation guidelines:
- Add variable to limit max binlog space (max-binlog-total-space and/or binlog_space_limit)
- Binlog size should be checked at during server start, binlog rotation, FLUSH LOGS, when writing to binary log or when max-binlog-total-size changes value.
- Add option --slave-connections-needed-for-purge with 1 as default. This is the minimum number of slaves
that needs to be connected for binary logs to be deleted. - Add status variable 'Binlog_disk_use' that shows current binary log space usage.
Attachments
Issue Links
- causes
-
MDEV-33116 int MYSQL_BIN_LOG::real_purge_logs_by_size(ulonglong): Assertion `reclaimed_space == found_space' failed
-
- Closed
-
-
MDEV-33282 Assertion `(longlong) binlog_space_total >= 0' failed in MYSQL_BIN_LOG::real_purge_logs_by_size
-
- Closed
-
-
MDEV-33319 max_binlog_total_size and slave_connections_needed_for_purge require wrong permissions
-
- Open
-
-
MDEV-33320 Assertion `(longlong) binlog_space_total >= 0' failed in MYSQL_BIN_LOG::real_purge_logs_by_size #2
-
- Closed
-
- is duplicated by
-
MDEV-33029 Add a mechanism to limit total binlog size on disk
-
- Closed
-
- relates to
-
MDEV-29195 relay_log_purge variable not very useful
-
- Open
-
-
MDEV-29196 Request new system variable: binlog_keep_max
-
- Open
-