Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have MySQL Replication working between two servers in master-master mode.

Replication has been working from day 1.

The IO Thread and the SQL Thread has never died. However, the Slave SQL thread dies very, very often.

The log only says:

120913 17:58:50 [Note] Slave I/O thread killed while reading event
120913 17:58:50 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.004109',
    position 101146947
120913 17:58:50 [Note] Error reading relay log event: slave SQL thread was killed

I've Googled for the problem, but found no indication of what to look for or how to resolve the issue.

What could be causing the thread to die?

share|improve this question
Do you have any additional slaves replicating from either Master ? – RolandoMySQLDBA Sep 13 '12 at 12:48

When the IO Thread dies, it usually dies for these reasons

  • Network Issues

The first two reasons are obvious, but many have been victimized by network connectivity. For example, if there are enough dropped packets along the traceroute of the IP you are using as the Master, the IO Thread will just die off. By default, mysql attempts to reconnect to the Master every 60 seconds.

The mysqld process does not record network level issues, but a dying IO Thread is usually a dead giveaway (no pun intended). If this is happening often, go to work troubleshooting the traceroute on that IP (perhaps ifconfig on that Master IP).

share|improve this answer
+1 for the pun! – Phil Sep 13 '12 at 13:12

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.