2019-11-30 04:10:36 47114 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
2019-11-30 04:10:36 47114 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log ‘binlog.002260’ at position 329464093
2019-11-30 04:10:36 47114 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the ‘START SLAVE Syntax’ in the MySQL Manual for more information.
2019-11-30 04:10:46 47114 [ERROR] Slave I/O: error reconnecting to master ‘repli@172.31.1.67:3306’ - retry-time: 60 retries: 1, Error_code: 2013
2019-11-30 04:11:56 47114 [ERROR] Slave I/O: error reconnecting to master ‘repli@172.31.1.67:3306’ - retry-time: 60 retries: 2, Error_code: 2013
2019-11-30 04:13:06 47114 [ERROR] Slave I/O: error reconnecting to master ‘repli@172.31.1.67:3306’ - retry-time: 60 retries: 3, Error_code: 2013
2019-11-30 04:14:16 47114 [ERROR] Slave I/O: error reconnecting to master ‘repli@172.31.1.67:3306’ - retry-time: 60 retries: 4, Error_code: 2013
2019-11-30 04:15:26 47114 [ERROR] Slave I/O: error reconnecting to master ‘repli@172.31.1.67:3306’ - retry-time: 60 retries: 5, Error_code: 2013
2019-11-30 04:16:37 47114 [ERROR] Slave I/O: error reconnecting to master ‘repli@172.31.1.67:3306’ - retry-time: 60 retries: 6, Error_code: 2013
2019-11-30 04:17:47 47114 [ERROR] Slave I/O: error reconnecting to master ‘repli@172.31.1.67:3306’ - retry-time: 60 retries: 7, Error_code: 2013
2019-11-30 04:18:57 47114 [ERROR] Slave I/O: error reconnecting to master ‘repli@172.31.1.67:3306’ - retry-time: 60 retries: 8, Error_code: 2013
2019-11-30 04:20:07 47114 [ERROR] Slave I/O: error reconnecting to master ‘repli@172.31.1.67:3306’ - retry-time: 60 retries: 9, Error_code: 2013
2019-11-30 04:21:17 47114 [ERROR] Slave I/O: error reconnecting to master ‘repli@172.31.1.67:3306’ - retry-time: 60 retries: 10, Error_code: 2013
2019-11-30 04:22:22 47114 [Note] Slave: connected to master ‘repli@172.31.1.67:3306’,replication resumed in log ‘binlog.002260’ at position 329464093
2019-11-30 05:04:29 47114 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
2019-11-30 05:04:29 47114 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log ‘binlog.002261’ at position 38361784
2019-11-30 05:04:29 47114 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the ‘START SLAVE Syntax’ in the MySQL Manual for more information.
2019-11-30 05:24:01 47114 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
2019-11-30 05:24:01 47114 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log ‘binlog.002261’ at position 105884756
2019-11-30
[ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
我来答
添加附件
收藏
分享
问题补充
3条回答
默认
最新
回答交流
Markdown
请输入正文
提交
相关推荐
mysql proxy 选择 ProxySQL 还是 KingShard?
回答 1
已采纳
实测,proxysql在高并发时扛不住,会中断服务。如果只是想实现failover,还是搭建mgr或用MHA比较好。
mysql8.0 root密码被锁定了,怎么解决?
回答 1
已采纳
建议在配置文件用skipgranttables方式修改密码https://www.modb.pro/db/24271
mysql 通讯协议为什么不直接采用http而是自己分装 TCP 呢?
回答 1
已采纳
这个就要从OSI7层模型说起来,建议你了解一下。http是基于TCP协议在应用层的文本传输协议,在应用层。如果用http,需要走多个节点去解析,完全没有自我封装TCP协议来的快。
MySQL count有必要做冗余吗?
回答 2
已采纳
不知道我对你的问题理解的对不对,简单说下我的想法,仅供参考:innodb的话没必要count冗余吧,InnoDB支持事务,其中大部分操作都是行级锁,所以可能表的行数可能会被并发修改,那么缓存记录下来的
MySQL 可以运行在 FreeBSD、Linux或Windows系统。
回答 1
已采纳
当然可以。
在Linux7上编码mysql8源码时总是提示devtoolset-10-gcc找不到,已经安装了gcc10.3了,还是提示找不到,这是为什么?
回答 2
已采纳
centos7.9下,会默认指向devtoolset10gcc10.2.12.1.el7.x8664:GCCversion10,比gcc10.3版本低,或者看下这个gcc是哪个rpm安装的
MySQL使用In-Place方式5.7.35升级至最新,会有什么问题吗?
回答 3
已采纳
只要能升级上来,正常启动就没有问题。剩下的就是看看应用适配情况,jdbc的更换什么的。本地升级需要停机一下。其他没什么。
ubuntu22使用clion调试mysql8.0.28源码遇到openssl问题
回答 2
这可能是因为你的系统中存在多个版本的 OpenSSL,而 cmake 可能没有找到正确的版本。你可以尝试以下方法:1. &n
MySQLdb的SSCursor为什么会越来越慢?
回答 1
mysql的本身不适合做一些复杂处理的工作。对于游标嵌套循环,遍历结果比对一行一行,生成临时表,随着数据量增加,逻辑复杂性能下降太厉害了。sql语句尽量走索引。这个确实有点不好调试。看看能不能用普遍的
mysql版本区别
回答 1
一两句话说不完,建议去看官方文档,不过5.5和5.6就不必要看了,已经EOL了。https://dev.mysql.com/doc/refman/8.0/en/
问题信息
请登录之后查看
邀请回答
暂无人订阅该标签,敬请期待~~