Great post. I found what I was looking for. Do you mind if I post this on my website and give you credit? If not, it’s ok.

Simple messages are the most powerful. Keep it simple is the advice given by top technologists. One reason why blogs are extremely popular is their simplicity. This simplicity comes from the shortness and focus of the message of the blog. This Log Buffer Edition collects some simple yet powerful blog posts for you in Log [...]

I like this blog ,because I learn some knowledge from it.Thank you very much.

sure, no problem

Great post. I found what I was looking for. Do you mind if I post this on my website and give you credit? If not, it’s ok.

SchoonerSQL 5.1 is now enterprise-ready: a fully tested GA product that can be deployed for your production environment. We have added some exciting features like Auto Async Failover across WAN, to make DBAs go ecstatic, and Intra-Schema Parallel Async Appliers to provide 4x throughput compared to MySQL 5.5 async replication. We also added Alerts for MySQL Admin Cluster GUI and a new feature called High Speed Incremental Recovery.

You want to know more? Join this webinar on December 14th 10am PST
https://www3.gotomeeting.com/register/988533686

MySQL doesn’t often crash, but, if you use MySQL on a production system you should have High Availability.

Maybe you’ve not heard of MHA.  Yoshinori Matsunobu only released it in July of this year (2011).  I’ve been reviewing it and I think you should too. There are a lot of people chasing after this “holy grail” and most systems are complex and / or hard to recover when they fail. MHA simple and easy to use.

MHA is a fail over tool. It’s designed to fail a master and promote a slave to a new master. (This is simply to say but you should read how it’s done.) It can monitor your master or you can manually fail over.  Failing …

Following the tradition, there will be a “MySQL and Friends” devroom at FOSDEM 2012. The devroom is scheduled for Sunday 5th February 2012, whole day. If you are interested to give a talk, please submit it before December 26th through this submission form.

Link to original announcement by Frédéric Descamps

When participating recently in a sprint held at Google to document four free software projects, I thought about what might have prompted Google to invest in this effort. Their willingness to provide a hotel, work space, and food for some thirty participants, along with staff support all week long, demonstrates their commitment to nurturing open source.

Google is one of several companies for which I'll coin the term "closed core." The code on which they build their business and make their money is secret. (And given the enormous infrastructure it takes to provide a search service, opening the source code wouldn't do much to stimulate competition, as I point out in a posting on O'Reilly's radar blog). But they depend on a huge range of free software, ranging from Linux …

Over the course of years, I have observed that the three most sensitive indicators of MySQL having a server lockup are the queries per second, number of connections, and number of queries running. Here is a chart of those three on a production system. Find the bad spot:

I am currently working on developing an automated system that detects abnormal behavior in these three metrics, but doesn’t require any a priori inputs or thresholds, e.g. you don’t have to tell it “more than X is bad.” (It could be that during a low period of the day, X is different than during the peak load.)

It turns out that this is hard to do reliably, without a lot of false positives and without false negatives (not triggering during an incident). If there is existing literature on the mathematical techniques to do this, I’d be …