Mysql replication, Slow resyncing of slave after an error
- by James Hackett
I have a slave that got an error about a months or so ago and got way behind the master. I fixed the error and now playing catchup with the master but its going very slowly. Its going at 1.3x real time. I was using less that 10% of the db resources when these writes were first happening so the speed of the server shouldn't be an issue.
Is there any settings I can switch to help the slave catch up with the master?