Gathering the Information You Need
Information is the key to successful troubleshooting. In addition to using it for your own troubleshooting, it is critical when you open a support case. So donât ignore the sources and instruments that collect reports about problems, such as the error log.
That said, you canât log everything all the time. Logging puts a burden on your server. So you need to find a balance between the information that needs to be saved all the time and the information you can ignore until a real problem happens.
I recommend you always turn on instruments that do not need a lot of resources, such as the error logfile and operating system logs. Logging options that require light resources, such as MEM without the query analyzer, can be running constantly too. It is not thrifty to try to shave a little load off your server by turning off these instruments and giving up the help they will offer during a critical problem.
With regard to reporting tools that can decrease performance noticeably, be prepared to use them, but turn them off until a problem fires up. Use of these instruments can be implemented as an option in the application.
What Does It All Mean?
Even gigabytes of information are useless if you donât understand it. So read the error messages, suggestions from MEM, and so on. If you donât understand them, refer to the MySQL Reference Manual, books, blogs, forums, or other sources of information.
A search engine is a good companion. Just typing an error ...
Get MySQL Troubleshooting now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
