Help
Note: You should write down or electronically record all observations while you conduct this procedure. Seeing the information consolidated in one place can sometimes present a much clearer body of evidence.
- Check the status on the master. Record any anomalies.
- Check the status on each slave. Record any anomalies.
- Read the error logs on all of your servers.
- Examine the process list on each server. Look for anomalies in status.
- If no errors are reported, attempt to restart the slave. Record any errors presented.
- Check the configuration of the server in question to ensure nothing has changed.
- Examine your notes and form a plan to research and fix the problem.
This procedure is oversimplified, but it should help you diagnose the replication problem more quickly than chasing the errors presented will (if there are any errors to chase).
Learn more about this topic from MySQL High Availability.
Server bottlenecks and failures are a fact of life in any database deployment, but they don't have to bring everything to a halt. MySQL provides several features that can protect you from outages, whether you're running directly on the hardware, on virtual machines, or in the cloud. This book shows you how to use these features effectively, and helps you determine which combination of features will give you the most reliable system for a price you can afford.
