Bug #11368 Cluster Slave has issue processing from relay log after cluster failure
Submitted: 15 Jun 2005 23:23 Modified: 23 Jul 2005 13:59
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1.0-wl2325-wl1354-new OS:Linux (Linux)
Assigned to: Tomas Ulin CPU Architecture:Any

[15 Jun 2005 23:23] Jonathan Miller
The slave SQL thread has issues processing the relay log after a cluster has failed and been brought back on-line. The error message given does not acutally tell you what the issue that needs to be fixed is.

I tried to recover from this but was unable to.

1) Setup master cluster with bank test running.
2) take cluster backup and copy to slave system
3) restore dump on slave cluster and find position in master bin log to start processing from
3) start the slave
4) crash the cluster
5) restart the slave
At this point the SQL thread will abort.

I tired the following
1) stop the slave
2) reset the slave
3) change the epoch in apply_status back to original (from 348 back to 319)
4) reset the slave where to start processing in the masters bin log
5) started the slave

The SQL thread still aborted with the same message. 
Note: the mysqld had cored (see: Bug #11366) so the relay log may have been corrupted.

The message:
050615 23:17:37 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master1.000003' position 9329568

How to repeat:
see above
[23 Jul 2005 13:59] Tomas Ulin
error messages have been added