]]> ]]>

Preventing MySQL Emergencies

Preventing downtime-causing emergencies in MySQL can be difficult because they are caused by complex combinations of several things going wrong. Efforts to be proactive may be sincere, but without knowledge of the causes of emergencies, they often fail to prevent further problems. This white paper explains dozens of ways that real emergencies could have been prevented in production systems, and suggests specific actions to accomplish these. It grew from a study of hundreds of downtime-causing emergencies for Percona's customers, and is the companion to an article in the Q1 2011 issue of IOUG's SELECT magazine, which presents analysis of the causes and natures of the incidents. Each recommendation in this paper could have prevented at least one incidence of production downtime. The paper includes checklists that can be used to help perform and document the measures discussed.

February 2011


Authors

Baron Schwartz

Baron Schwartz

Chief Performance ArchitectPercona

Baron is the lead author of High Performance MySQL, and creator of Maatkit. He consults with Percona's customers, and develops tools and practices for Percona's team.



Our MySQL white papers are free and require no registration to download. They are released under the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 license.

Contact Us 24 Hours A Day
Support Contact us 24×7
Emergency? Contact us for help now!
Sales North America (888) 316-9775 or
(208) 473-2904
Sales
Europe
+44-208-133-0309
Sales Latin America +54-0800-666-3243 (Arg.)
+55-0800-020-4918 (Brazil)
Training (855) 55TRAIN or
(925) 271-5054
Share This
]]> ]]>