断重启从库故障:电Last_Error: Slave failed to initialize relay log info structure from the repository

断电重启故障

2017-11-10T21:27:52.791849+08:00 0 [ERROR] Error in Log_event::read_log_event(): ‘read error‘, data_len: 68, event_type: 2
2017-11-10T21:27:52.791889+08:00 0 [Warning] Error reading GTIDs from relaylog: -1
2017-11-10T21:27:52.793147+08:00 0 [Note] Slave: MTS group recovery relay log info based on Worker-Id 1, group_relay_log_name /home/mysql57/relay/relay-bin.000083, group_relay_log_pos 95280470 group_master_log_name mysql-bin.000048, group_master_log_pos 95280257
2017-11-10T21:27:52.793191+08:00 0 [ERROR] Error looking for file after /home/mysql57/relay/relay-bin.000084.
2017-11-10T21:27:52.793405+08:00 0 [ERROR] Failed to initialize the master info structure
2017-11-10T21:27:52.793414+08:00 0 [ERROR] Failed to create or recover replication info repositories.
2017-11-10T21:27:52.793417+08:00 0 [Note] Check error log for additional messages. You will not be able to start replication until the issue is resolved and the server restarted.
2017-11-10T21:27:52.842687+08:00 0 [Note] Event Scheduler: Loaded 0 events
2017-11-10T21:27:52.842824+08:00 0 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: ‘5.7.9-log‘ socket: ‘/home/mysql57/run/mysql.sock‘ port: 3306 Source distribution
2017-11-10T21:28:06.755717+08:00 0 [Note] InnoDB: Buffer pool(s) load completed at 171110 21:28:06
2017-11-10T21:38:12.848189+08:00 732 [ERROR] Slave SQL for channel ‘‘: Slave failed to initialize relay log info structure from the repository, Error_code: 1872bug

#########bug导致:

https://bugs.mysql.com/bug.php?id=83713

修复:保存好从库位点信息

reset  slave  ;

start slave;

#####################

时间: 2024-11-05 22:34:44

断重启从库故障:电Last_Error: Slave failed to initialize relay log info structure from the repository的相关文章

【故障处理】ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repository

今天在使用冷备份文件重做从库时遇到一个报错,值得研究一下. 版本:MySQL5.6.27 一.报错现象 dba:(none)> start slave; ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repository 这个时候查看error.log: 2017-07-17 16:19:02 9022 [ERROR] Failed to open the relay log '.

ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repository

该问题的一般是由relay log没有在配置文件定义所致. 1.问题描述: mysql> start slave; mysql> system perror 1872 MySQL error code 1872 (ER_SLAVE_RLI_INIT_REPOSITORY): Slave failed to initialize relay log info structure from the repository 2.处理办法2.1.修改配置文件 诸如在my.cnf配置文件中添加如下项: r

Slave failed to initialize relay log info structure from the repository

前几天做主从同步的时候没什么问题,今天做双机热备的时候出现了问题,问题如下:Slave failed to initialize relay log info structure from the repository(服务器未能从存储库初始化中继日志信息结构)可能是某些记录的存在导致的把,所以就尝试的用mysql自带的还原给还原了一下,成功了,具体如下:我是在从库做的主库的数据同步,所以在linux中的从库中进行的mysql命令,先停止从库同步操作,再做还原mysql> stop slave;

MySQL报错ERROR1872(HY000):Slave failed to initialize

ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repository MySQL 5.6修复从库复制时报错 mysql> start slave; ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repository 报错原因: 从库已经存在之前的relay log 解决

Slave SQL_THREAD如何重放Relay log

复制的介绍: 根据日志定义的模式不一样,可以分为:Statement(SBR)模式,Row(RBR)格式或者是MIXED格式,记录最小的单位是一个Event,binlog日志前4个字节是一个magic number,接下来19个字节记录Format desc evnet:FDE.MySQL5.6版本增加了GTID复制. 下面对三种binlog格式的优缺点: Statement(基于语句级的复制): 优点: 1)Binlog文件较小 2)日志是包含用户执行的原始SQL,方便统计和审计 3)出现最早

处理更改 MySQL relay log 目录后 slave 无法启动故障

问题:更改 relay log 目录后 slave 无法启动 2018-08-03T02:53:36.172465Z 0 [ERROR] Failed to open the relay log './mysql03-relay-bin.000018' (relay_log_pos 9680848). 2018-08-03T02:53:36.172515Z 0 [ERROR] Could not find target log file mentioned in relay log info i

MySQL从库不能同步,报错Relay log read failure

问题:MySQL从库的数据不能同步,从库SHOW SLAVE STATUS提示如下错误: Last_SQL_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log)

MySQL复制ERROR 1794 (HY000): Slave is not configured or failed to initialize properly.

ERROR 1794 (HY000): Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log. error log中有类似日志:2016-05-10 17:21:25 1

故障案例:slave延迟很大

案例1:lvm机型,从库创建完成后,主库qps 2w,从库6k多.从某个时间点开始延迟在缓慢增加,一直涨到7w多秒才发现去处理:从库io的util很高 故障原因:查看配置发现这个从库开启了log_slave_updates,一直在产生binlog,当把这个参数禁用或者设置sync_binlog=0以后,util立马就降下来了,同步延迟也就慢慢变小了直到为0,此前已经发现多次使用lvm逻辑卷管理或者SSD的机器的udb只要开启了这个sync_binlog=1,好像磁盘util都很高,也没有深究为什