MySQL replication Environment Slave error & how to solve the problem of quot;Got fatal error 1236 from master when reading data"
This article mainly explains "MySQL replication environment Slave error" Got fatal error 1236 from master when reading data "how to solve", interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Next let the editor to take you to learn "MySQL replication environment Slave error" Got fatal error 1236 from master when reading data "how to solve it"!
MySQL replication environment Slave node reports an error
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)
Where to view the binary log on the Master node
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)
View the binary log of the Master node
Mysql > show master logs
+-+ +
| | Log_name | File_size |
+-+ +
| | mysql-bin.000010 | 3780 | |
| | mysql-bin.000011 | 1734 | |
+-+ +
2 rows in set (0.06 sec)
View the binary log of the Slave node
Mysql > show binary logs
+-+ +
| | Log_name | File_size |
+-+ +
| | mysql-bin.000008 | 154 | |
| | mysql-bin.000009 | 154 | |
+-+ +
2 rows in set (0.02 sec)
Reason for reporting an error:
The binary log was deleted on the Master node, resulting in the IO thread of the Slave node not getting the specified binary log.
The parameter to automatically delete the binary log is set on the Master node, and the binary log will be deleted automatically after 5 days. However, the database where the Slave node is located has not been started, and the IO thread cannot get the binary log of the Master node when it starts again.
Mysql > show variables like'% expire%'
+-+ +
| | Variable_name | Value |
+-+ +
| | disconnect_on_expired_password | ON |
| | expire_logs_days | 5 | |
+-+ +
2 rows in set (0.02 sec)
Solution:
Unless the main library has a binary log backup, the Slave node needs to be rebuilt
At this point, I believe that everyone on the "MySQL replication environment Slave error" Got fatal error 1236 from master when reading data "how to solve" have a deeper understanding, might as well to the actual operation of it! Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!
