您好,登錄后才能下訂單哦!
本篇內(nèi)容主要講解“MySQL復(fù)制環(huán)境Slave報錯"Got fatal error 1236 from master when reading data"怎么解決”,感興趣的朋友不妨來看看。本文介紹的方法操作簡單快捷,實用性強。下面就讓小編來帶大家學(xué)習(xí)“MySQL復(fù)制環(huán)境Slave報錯"Got fatal error 1236 from master when reading data"怎么解決”吧!
MySQL復(fù)制環(huán)境Slave節(jié)點報錯
mysql> show slave status\G
*************************** 1. row ***************************
Slave_IO_State:
Master_Host: 10.20.30.10
Master_User: repl
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000008
Read_Master_Log_Pos: 920
Relay_Log_File: mysqld-relay-bin.000018
Relay_Log_Pos: 4
Relay_Master_Log_File: mysql-bin.000008
Slave_IO_Running: No
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 920
Relay_Log_Space: 154
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 1236
Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 1
Master_UUID: 203fe772-177e-11e7-b15c-000c296b3b20
Master_Info_File: /mysql_data_57/master.info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
Master_Retry_Count: 86400
Master_Bind:
Last_IO_Error_Timestamp: 170624 17:03:05
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set:
Executed_Gtid_Set:
Auto_Position: 0
Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:
1 row in set (0.00 sec)
在Master節(jié)點上查看二進制日志的位置
mysql> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000011 | 1734 | | | |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)
查看Master節(jié)點的二進制日志
mysql> show master logs;
+------------------+-----------+
| Log_name | File_size |
+------------------+-----------+
| mysql-bin.000010 | 3780 |
| mysql-bin.000011 | 1734 |
+------------------+-----------+
2 rows in set (0.06 sec)
查看Slave節(jié)點的二進制日志
mysql> show binary logs;
+------------------+-----------+
| Log_name | File_size |
+------------------+-----------+
| mysql-bin.000008 | 154 |
| mysql-bin.000009 | 154 |
+------------------+-----------+
2 rows in set (0.02 sec)
報錯原因:
在Master節(jié)點上刪除了二進制日志,導(dǎo)致Slave節(jié)點的IO線程獲取不到指定的二進制日志
在Master節(jié)點上設(shè)置了自動刪除二進制日志的參數(shù),5天后會自動刪除二進制日志;而Slave節(jié)點所在的數(shù)據(jù)庫一直沒有啟動,再次啟動時IO線程獲取不到Master節(jié)點的二進制日志
mysql> show variables like '%expire%';
+--------------------------------+-------+
| Variable_name | Value |
+--------------------------------+-------+
| disconnect_on_expired_password | ON |
| expire_logs_days | 5 |
+--------------------------------+-------+
2 rows in set (0.02 sec)
解決方法:
除非主庫有二進制日志備份,否則需要重建Slave節(jié)點
到此,相信大家對“MySQL復(fù)制環(huán)境Slave報錯"Got fatal error 1236 from master when reading data"怎么解決”有了更深的了解,不妨來實際操作一番吧!這里是億速云網(wǎng)站,更多相關(guān)內(nèi)容可以進入相關(guān)頻道進行查詢,關(guān)注我們,繼續(xù)學(xué)習(xí)!
免責(zé)聲明:本站發(fā)布的內(nèi)容(圖片、視頻和文字)以原創(chuàng)、轉(zhuǎn)載和分享為主,文章觀點不代表本網(wǎng)站立場,如果涉及侵權(quán)請聯(lián)系站長郵箱:is@yisu.com進行舉報,并提供相關(guān)證據(jù),一經(jīng)查實,將立刻刪除涉嫌侵權(quán)內(nèi)容。