xtrabackup !xtrabackup，可是為什麼會因此造成 binlog 沒有被正常清理呢？Binary log files are automatically removed after the server's binary log expiration period. Removal of the files can take place at startup and when the binary log is flushed.MySQL :: MySQL 8.0 Reference Manual :: 15.4.1.1 PURGE BINARY LOGS Statement
MySQL :: MySQL 8.0 Reference Manual :: 15.4.1.1 PURGE BINARY LOGS Statement
The binary log is a set of files that contain information about data modifications made by the MySQL server. The log consists of a set of binary log files, plus an index file (see Section 7.4.4, “The Binary Log”).
PURGE BINARY LOGS should not be issued while a LOCK INSTANCE FOR BACKUP statement is in effect for the instance, because it contravenes the rules of the backup lock by removing files from the server. From MySQL 8.0.28, this is disallowed.MySQL :: MySQL 8.0 Reference Manual :: 15.3.5 LOCK INSTANCE FOR BACKUP and UNLOCK INSTANCE Statements
Executing the LOCK INSTANCE FOR BACKUP statement requires the BACKUP_ADMIN privilege. The BACKUP_ADMIN privilege is automatically granted to users with the RELOAD privilege when performing an in-place upgrade to MySQL 8.0 from an earlier version.
LOCK INSTANCE FOR BACKUP 鎖時，是不能運行 PURGE BINARY LOGS。LOCK INSTANCE FOR BACKUP，並且還會運行 FLUSH NO_WRITE_TO_BINLOG BINARY LOGS 來刷新 Binary log，然後因為這個原因導致 log 中會出現以下錯誤：max_binlog_size 的設置 1GB (這也預設值），所以這台 MySQL 的 Binary log 沒有自主因為過大而觸發 binlog 的切換！LOCK INSTANCE FOR BACKUP 鎖，導致無法清除 binary log!max_binlog_sizemax_binlog_size：讓 Binary logs 更頻繁的 flush，從而有機會在 xtrabackup 以外的時間點觸發 purge。MySQL :: MySQL 8.0 Reference Manual :: 15.3.5 LOCK INSTANCE FOR BACKUP and UNLOCK INSTANCE Statements
Executing the LOCK INSTANCE FOR BACKUP statement requires the BACKUP_ADMIN privilege. The BACKUP_ADMIN privilege is automatically granted to users with the RELOAD privilege when performing an in-place upgrade to MySQL 8.0 from an earlier version.
MySQL :: MySQL 8.0 Reference Manual :: 15.4.1.1 PURGE BINARY LOGS Statement
The binary log is a set of files that contain information about data modifications made by the MySQL server. The log consists of a set of binary log files, plus an index file (see Section 7.4.4, “The Binary Log”).
Percona Community ForumXtrabackup flushing binary logs while still locked
Xtrabackup flushing binary logs while still locked
I’m just trying to ascertain if I have a Bug or not with xtrabackup, or if it is intended to work this way. I am using: MySQL (Oracle): 8.0.39 xtrabackup version: 8.0.35-31 When xtrabackup runs it runs using the --lock-ddl option which runs lock instance for backup. At the end of the process it runs FLUSH NO_WRITE_TO_BINLOG BINARY LOGS Then afterwards it runs UNLOCK INSTANCE From the logs: 2025-04-04T05:00:01.560946+01:00 0 [Note] [MY-011825] [Xtrabackup] Executing LOCK INSTANCE FOR BACK...
Percona Community Forum
MySQL binlog超过binlog_expire_logs_seconds阈值没有删除案例 - 潇湘隐者 - 博客园
MySQL binlog超过binlog_expire_logs_seconds阈值没有删除案例 - 潇湘隐者 - 博客园
生产环境有一套3个节点的MySQL InnoDB Cluster，MySQL的版本为Server version: 8.0.35 MySQL Community Server - GPL， 早上突然收到Zabbix的告警，其中一个节点出现空间告警："/data: Disk space is