温馨提示×

温馨提示×

您好,登录后才能下订单哦!

密码登录×
登录注册×
其他方式登录
点击 登录注册 即表示同意《亿速云用户服务条款》

精致的参数 - max_binlog_files

发布时间:2020-03-02 04:12:51 来源:网络 阅读:702 作者:coveringindex 栏目:MySQL数据库

max_binlog_files,是Percona MySQL分支提供的限制binlog文件数量的参数,在删除归档数据、binlog增长很快的情况下,很实用的一个参数。


该参数也对正在被使用的binlog提供了保护,是purge不掉的,如下。



[root@mysql.sock][(none)]>purge binary logs to 'bin.016222';

Query OK, 0 rows affected, 1 warning (0.01 sec)


[root@mysql.sock][(none)]>>show warnings;

+---------+------+------------------------------------------------------------------------------------------------------+

| Level   | Code | Message                                                                                                        |

+---------+------+------------------------------------------------------------------------------------------------------+

| Warning | 1867 | file ./bin.016215 was not purged because it was being read by 1 thread(s), purged only 0 out of 7 files. |

+---------+------+------------------------------------------------------------------------------------------------------+

1 row in set (0.00 sec)


$ perror 1867

MySQL error code 1867 (ER_WARN_PURGE_LOG_IN_USE): file %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.


error日志中也是用体现的。


2019-09-18T01:02:56.643574+08:00 10326541 [Warning] file ./bin.016215 was not purged because it was being readby thread number 17218543

2019-09-18T01:03:18.196285+08:00 17244031 [Warning] file ./bin.016215 was not purged because it was being readby thread number 17218543


向AI问一下细节

免责声明:本站发布的内容(图片、视频和文字)以原创、转载和分享为主,文章观点不代表本网站立场,如果涉及侵权请联系站长邮箱:is@yisu.com进行举报,并提供相关证据,一经查实,将立刻删除涉嫌侵权内容。

AI