Description:
Was checking on the systems after the master cluster had gone down, and found that the slave SQL thread had stopped. Not 100% sure what caused this thread to stop. I am thinking that the slave missed a drop database because TESTER1 does not exist in the database.
Never the less, the error message below provides nothing useful as to what needs to be corrected.
050714 1:37:27 [Note] NDB Binlog: CREATE TABLE Event: REPL$TESTER1/t1
050714 1:37:32 [Note] NDB Binlog: CREATE TABLE Event: REPL$TESTER1/t1
050714 1:37:33 [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.000004' position 25082440
How to repeat:
unkown
Suggested fix:
If it was a missing database, then the error should read:
050714 1:37:33 [ERROR] Error running query, Database not found, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master1.000004' position 25082440
or
050714 1:37:33 [ERROR] Error running query, Database TESTER1 does not exist, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master1.000004' position 25082440
