Hello, I'm currently testing out replication on a high volume innodb based database. This has been working great for several weeks, but when I came in this morning I found my slave had the following error:
031212 23:30:24 Slave: query 'UPDATE monitor_tunnel_cisco_phase_2 SET counter=0, timestamp=NOW() WHERE monitor_id=3735 AND monitor_server_id=1 AND phase_2_id=6290' partially completed on the master and was aborted. There is a chance that your master is inconsistent at this point. If you are sure that your master is ok, run this query manually on the slave and then restart the slave with SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; SLAVE START; . Error_code: 1053 031212 23:30:24 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'slave_test_binlog.169' position 6404579 I was able to resolve this easily by running the query on the slave, setting the skip counter to 1, and restarting the slave. However I would like to know why this error was caused. I can find no log of any such error on my master. Should a failed query on the master have shown up in my /var/log/mysql/mysql.err? What would cause the query to have partially completed and aborted? Everything seems fine on the master so I'm not sure why the query was aborted. My master is running 4.0.13 and my slave is running 4.0.16 could this be the cause of the error? John A. McCaskey Software Development Engineer IP Sciences, Inc. [EMAIL PROTECTED] 206.633.0449
