Mysql Master/Slave problem handling records

Mysql master-Slave problem handling records Slave server downtime, resulting in the slave server startup after the show Slave status \ G prompt error Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'binlog truncated in the middle of event' solution: Master: show master status \ G # record the following information of the Master File: mysql-MasterSlave.000006 Position: 174367 Slave: slave stop; reset slave; change master to master_host = '2017. 168.1.126 ', master_user = 'user', master_password = 'PW ', master_log_file = 'mysql-MasterSlave.000006', master_log_pos = 174367; Note: Starting from mysql 5.5, Mysql joins semi-synchronous replication, and the usage of load data from master is canceled, after the MySQL Slave/Master instance recovers from an exception, MySQL Slave can process unfinished or discarded Master write data, such as log failure data, to obtain the source data from the master again. Similarly, restarting the Master instance does not cause Slave to lose data.