Weird SQL Error while Replicating

I encountered this weird SQL error / anomaly.

I have 5 replication slaves with one master. On the master, an insert statement was issued and it was replicated to all of the slaves except to one which I will call weird_slave. The weird_slave (MyISAM) complained that there was some SQL syntax error. I checked the insert statement and it looks pretty simple.

Also, the weird_slave has already been running for more than a couple of months now and it has received some variation of the insert statement.

I was thinking that the table could be corrupt and issued a check table and everything returned okay.

So, the question is why would the weird_slave complain about an SQL syntax error while the other slaves were okay with it. Sadly, I could not reproduce the error again. Also, I've tried to re-insert the same SQL statement on the weird_slave again and again and it was accepting it without complaining.

Cause of Replication Delay? I/O or SQL Thread?

I was thinking of this and could not figure it out or maybe I am just confused... Hehehe.

If MySQL is lagging behind the master (7,000 secs.), would it be caused by the I/O thread being slow or by the SQL thread (of course, this is assuming that I only have these two options to choose from)? If it is the I/O thread, what should I be looking for?

I've always assumed that the I/O thread would not cause a huge replication delay as it is just reading the binary logs from the master. So, if the Master_Log_File and Relay_Master_Log_File are the same and the Exec_Master_Log_Pos and Read_Master_Log_Pos are the same too, then I can assume that the replication delay is not based on the I/O thread, right?

And does anyone know how to compute the Seconds_Behind_Master???

MySQL Conference 2008

It's my first time here and it is really nice. I find it interesting to see so many people interested in MySQL.

MySQL - Sun Party

I attended the MySQL-Sun cocktail party yesterday (March 25, 2008) at the Jillian's @ The Metreon (101 Fourth Street, San Francisco, CA).

Live JasperSoft Seminar

I was lucky enough to attend the JasperSoft Seminar held at their headquarters in San Francisco yesterday (March 19, 2008). There were basically 3 sessions and I personally did not get much from the seminar.

What I found interesting was that I was able to talk to Guilio Toffoli who created the iReport which is basically the GUI software to create JasperReport xml files. We talked about performance limits of the software, problems that I had with designing the queries using SQLeonardo, and other stuff.

What's the Point?

The point is part of the line.
The line is part of the circle.
The circle is the wheel of the car.
The point is that we will never know what the point is.

10 traits to look for when you’re hiring a programmer

I found this interesting article that talks about things to look for in a programmer which I think is also suitable for a DBA.

http://blogs.techrepublic.com.com/10things/?p=319