Hi, I have a busy MySQL slave which is directly updated by a periodic "purge" script which throws away irrelevant data.
Occassionally, (er, a few times a day, actually), the slave "quietly" falls over, but ITS slaves trip with "[SQL...] 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 SQL_SLAVE_SKIP_COUNTER=1; SLAVE START;" Looking in the binlog, I find the affected SQL has error-code 1053 - about which perror knows nothing. I think this must be some timeout or locking issue or something. Does anyone know what the error means for certain ? Is there something I can tweak to alleviate the problem ? MySQL v3.23.51. regards, Martin -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
