Help
The best bug reports are those that describe errors that can be demonstrated or repeated using an isolated test case, for example, a replication problem that can be demonstrated on a test master and slave, and that has a minimal set of data needed for the problem. Often this is nothing more than a complete and accurate report of the configuration and event in question.
To report a bug, visit http://bugs.mysql.com and (if you have not done so already) register for an account. When you enter your bug report, be sure to describe the problem as completely as possible. For fastest results and a quick resolution, include as many of the following details as possible:
- Record all error messages verbatim.
- Include the binary log (in full or an excerpt).
- Include the relay log (in full or an excerpt).
- Record the configuration of the master and slave.
- Copy the results of the
SHOW MASTER STATUSandSHOW SLAVE STATUScommands. - Provide copies of all error logs.
Note: Be sure to exhaust all of the above techniques and explore the problem using all of the available tools.
The MySQL bug tracking tool will keep you apprised of your bug submission by sending you email alerts whenever the bug report is updated.
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.
