Percona ServerPercona is glad to announce the release of Percona Server 5.6.21-69.0 on October 7, 2014. Download the latest version from the Percona web site or from the Percona Software Repositories.

Based on MySQL 5.6.21, including all the bug fixes in it, Percona Server 5.6.21-69.0 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free. Complete details of this release can be found in the 5.6.21-69.0 milestone on Launchpad.

New Features:

Bugs Fixed:

  • Backup Locks did not guarantee consistent SHOW SLAVE STATUS information with binary log disabled. Bug fixed #1358836.
  • Audit Log Plugin would rotate the audit log in middle of an audit message. Bug fixed #1363370.
  • When the binary log is enabled on a replication slave, SHOW SLAVE STATUS performed under an active BINLOG lock could lead to a deadlock. Bug fixed #1372806.
  • Fixed a memory leak in Metrics for scalability measurement. Bug fixed #1334570.
  • Fixed a memory leak if secure-file-priv option was used with no argument. Bug fixed #1334719.
  • LOCK TABLES FOR BACKUP is now incompatible with LOCK TABLES, FLUSH TABLES WITH READ LOCK, and FLUSH TABLES FOR EXPORT in the same connection. Bug fixed #1360064.

Other bugs fixed: #1361568.

NOTE: Automatic upgrade for Percona Server with TokuDB on Debian/Ubuntu distribution will cause an error. In order to upgrade you’ll need to force the upgrade with “apt-get install -f” or remove the percona-server-tokudb-5.6 before upgrading and install it after the server package upgrade is done.

Release notes for Percona Server 5.6.21-69.0 are available in the online documentation. Please report any bugs on the launchpad bug tracker

4 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
Tim Callaghan

To be clear, this release includes the TokuDB storage engine version 7.5.1 (which is 7.5.0 plus a few bug fixes). It does not, however, include the Read Free Replication (RFR) functionality introduced in TokuDB v7.5.0. We are working hard to get this into the next release of Percona Server, and RFR requires code changes to Percona Server itself, not just the storage engine.

0
Vojtech Kurka

Is it possible there’s another memory leak still present?
We have this problem: with 50GB innodb buffer pool the server eats about 56GB of memory (RES) with the production workload – that’s OK. But then the memory consumption is increasing and after 3 days of runtime, it uses about 76GB of memory (RES) and the machine starts swapping out. We have the exact version of PerconaServer on the slave (without production workload, just the slave thread) and it doesn’t have this problem (54 GB mem RES after 7 days).

Vojtech

0
Hrvoje Matijakovic

Hi Vojtech,

Can you please report a bug here https://bugs.launchpad.net/percona-server/+filebug preferably with more details of your setup (ie. my.cnf) so we can try and reproduce the issue.

0
Vojtech Kurka

Hrvoje Matijakovic: OK, I’ve filed a bug.

0