Mysql master-slave synchronization Last_IO_Errno: 1236 error solution, last_io_errno1236

Mysql master-slave synchronization Last_IO_Errno: 1236 error solution, last_io_errno1236

Mysql master-slave synchronization Last_IO_Errno: 1236 what is the cause of the error? How can we solve this problem? Let's take a look at the records and solutions for this problem with the editor.

<script>ec(2);</script>

Slave server error code:

Last_IO_Errno: 1236Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Slave can not handle replication events with the checksum that master is configured to log; the first event 'mysql-bin.000005' at 16750821, the last event read from '/usr/local/mysql/Binlog/mysql-bin.000005' at 16750821, the last byte read from '/usr/local/mysql/Binlog/mysql-bin.000005' at 120.'

I have roughly analyzed the cause. I personally think it is likely that the reason is due to the different mysql versions and the incomplete backup. This problem does not exist for mysql with the same configuration version. (There is no specific reason for the test due to time issues)

The master server is upgraded to the latest mysql (5.6.29) version due to the downtime caused by the last php, while the slave server uses the db of 5.5.49 version when I just compiled it, therefore, it may be caused by this problem. I did not go to the official document, but I just guessed it.

Another problem caused by different versions is:

[root@Backup tmp]# /usr/local/mysql/bin/mysql -uroot -p <./all.sql Enter password: ERROR 1064 (42000) at line 279: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'STATS_PERSISTENT=0' at line 11

I was lazy and re-compiled a mysql of the same version. The specific reason is different from the version. I did not study it carefully.

Slave temporary skip error method:

MySQL

mysql>slave stop;  #stop slavemysql>SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;mysql>slave start;  #start slave

Slave permanent skip error method:

Vi/etc/my. cnf [mysqld] slave-skip-errors = errors 1146, # skip errors of the specified error no type # slave-skip-errors = all # skip all errors

Summary

The above is all about the Mysql master-slave synchronization Last_IO_Errno: 1236 error solution. I hope it will be helpful to you. If you have any better solutions, leave a message for discussion.

If you are interested, refer to: Analysis of Different errors in MySQL table sorting rules, Introduction to MySQL Optimization in enterprise production, analysis of MYSQL subqueries and nested query optimization instances. If you have any questions, please leave a message, the editor will reply to you in a timely manner. Thank you for your support!