October 23, 2014

Percona Server and XtraBackup weekly news, March 12th

Welcome to the weekly roundup and progress report. What’s new this week in Percona Server:

Modeling MySQL Capacity by Measuring Resource Consumptions

There are many angles you can look at the system to predict in performance, the model baron has published for example is good for measuring scalability of the system as concurrency growths. In many cases however we’re facing a need to answer a question how much load a given system can handle when load is […]

How to debug long-running transactions in MySQL

Among the many things that can cause a “server stall” is a long-running transaction. If a transaction remains open for a very long time without committing, and has modified data, then other transactions could block and fail with a lock wait timeout. The problem is, it can be very difficult to find the offending code […]

Percona reaches 1000-customer milestone

Customer 1000 has signed on with Percona (press release). Many thanks to all of our customers!

Percona Server 5.1.55-12.6

Percona Server version 5.1.55-12.6 is now available for download. It is now the current stable release version. Changes Fixed compiler warnings in both the core server and in XtraDB. (Alxey Kopytov, Yasufumi Kinoshita) Bugs Fixed Bug #602047 – The ROWS_READ columns of TABLE_STATISTICS and INDEX_STATISTICS were not properly updated when a query involved index lookups […]

Percona Server and XtraBackup weekly news, March 5th

What’s new this week in Percona Server:

How Percona diagnoses MySQL server stalls

We receive many requests for help with server stalls. They come under various names: lockup, freeze, sudden slowdown. When something happens only once or twice a day, it can be difficult to catch it in action. Unfortunately, this often leads to trial-and-error approaches, which can drag on for days (or even months), and cause a […]

What is innodb_support_xa?

A common misunderstanding about innodb_support_xa is that it enables user-initiated XA transactions, that is, transactions that are prepared and then committed on multiple systems, with an external transaction coordinator. This is actually not precisely what this option is for. It enables two-phase commit in InnoDB (prepare, then commit). This is necessary not only for user-initiated […]