Solving slave MySQL: waiting for the slave SQL thread to free enough relay log space

Solution 1:

Your replication has stopped due to an unknown database cr_debug. Once you clear that up the log space should resolve itself. There are a few ways to resolve it depending on what result you want.

1. If you want that DB to be replicated then create it on the slave with the same table structure as your master. Depending on your situation you may have to do something to make sure it is consistent.

2. If you didn't intend for that database to get replicated then add an "replicate-ignore-db = cr_debug" to your configuration and restart replication. This will cause it to ignore all stataments from that DB in the unprocessed part of the log.

3)If you have a reason to believe that there is just the one statement (or a small handful) going to that DB you can actually just skip the statement using SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1. I don't recommend that though because it is very by hand and rather messy.