Replication 1594错误解决

*************************** 1. row ***************************
               Slave_IO_State: 
                  Master_Host: 192.168.199.10
                  Master_User: replication
                  Master_Port: 3306
                Connect_Retry: 30
              Master_Log_File: prddb1-bin.000081
          Read_Master_Log_Pos: 314995585
               Relay_Log_File: bak10-relay-bin.000045
                Relay_Log_Pos: 792805691
        Relay_Master_Log_File: prddb1-bin.000080
             Slave_IO_Running: No
            Slave_SQL_Running: No
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  Replicate_Wild_Ignore_Table: 
                   Last_Errno: 1594
                   Last_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), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 1023759536
              Relay_Log_Space: 1388743985
              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: 0
                Last_IO_Error: 
               Last_SQL_Errno: 1594
               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), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.


解决方案
IO SQL进程都是NO的状态
查看二进制文件读取信息进度
/mysqldata/data/ relay-log.info
Cat relay-log.info
./bak10-relay-bin.000045
792805691
prddb1-bin.000080 #IO执行到的那个文件
1023759536


STOP SLAVE;
CHANGE MASTER TO 
master_log_file='prddb1-bin.000080',
master_log_pos=1023759536;
START SLAVE;