# ERROR 1220 (HY000): 执行命令 'PURGE BINARY LOGS' 时出错：在文件索引中找不到目标日志文件

- **ID:** `database/mysql-binlog-purge-failure`
- **领域:** database
- **类别:** data_error
- **错误码:** `1220`
- **验证级别:** ai_generated
- **修复率:** 85%

## 根因

PURGE BINARY LOGS 命令中指定的二进制日志文件在二进制日志索引文件中不存在，通常是由于该文件被手动删除或索引文件损坏。

## 版本兼容性

| 版本 | 状态 | 引入 | 弃用 |
|------|------|------|------|
| MySQL 5.7 | active | — | — |
| MySQL 8.0 | active | — | — |
| MySQL 8.4 | active | — | — |
| MariaDB 10.5 | active | — | — |
| MariaDB 10.6 | active | — | — |

## 解决方案

1. ```
   通过列出所有现有 binlog 文件来重建二进制日志索引文件：`ls -1 /var/lib/mysql/mysql-bin.* > /var/lib/mysql/mysql-bin.index` 并确保文件权限正确。然后重试 PURGE BINARY LOGS。
   ```
2. ```
   谨慎使用 RESET MASTER（它会删除所有 binlog）来清理索引并重新开始。仅在不需要时间点恢复时执行：`RESET MASTER;`
   ```
3. ```
   如果特定 binlog 文件缺失，识别间隙并使用 FLUSH LOGS 创建新日志，然后清除到该新日志：`FLUSH LOGS; PURGE BINARY LOGS TO 'mysql-bin.000new';`
   ```

## 无效尝试

- **Run PURGE BINARY LOGS TO 'mysql-bin.000999' again with a different filename** — If the index file is corrupted, any filename will fail with the same error until the index is rebuilt (90% 失败率)
- **Delete the binary log index file manually and restart MySQL** — Deleting the index file without rebuilding it will cause MySQL to fail to start or lose track of all binlogs (95% 失败率)
- **Set expire_logs_days to 0 to disable purging** — This only stops automatic purging; the manual PURGE command will still fail due to the index issue (70% 失败率)