November 24, 2014

Percona Server 5.6.16-64.0 is now available

Percona Server version 5.6.16-64.0

Percona Server version 5.6.16-64.0

Percona is glad to announce the release of Percona Server 5.6.16-64.0 on March 10th, 2014 (Downloads are available here and from the Percona Software Repositories.

Based on MySQL 5.6.16, including all the bug fixes in it, Percona Server 5.6.16-64.0 is the current GA release in the Percona Server 5.6 series. All of Percona’s software is open-source and free, all the details of the release can be found in the 5.6.16-64.0 milestone at Launchpad.

New Features:

  • Percona Server has implemented Backup Locks that can be used as a lightweight alternative to FLUSH TABLES WITH READ LOCK for taking physical and logical backups.
  • Percona Server has split a new LRU manager thread out of the InnoDB cleaner thread, that performs LRU flushes and evictions to refill the free lists.
  • Percona Server now has server-side support for TokuDB Compression option syntax.
  • Percona Server has implemented Slow Query Log Rotation and Expiration feature to provide users with better control of slow query log disk space usage.
  • Ability to change database for mysqlbinlog has been ported from Percona Server 5.1.
  • In order to comply with Linux distribution packaging standards Percona‘s version of libmysqlclient has been renamed to libperconaserver. The old name was conflicting with the upstream libmysqlclient. Except for packaging, libmysqlclient and libperconaserverclient of the same version do not have any differences. Users wishing to continue using libmysqlclient will have to install the corresponding package of their distribution, such as mysql-lib for CentOS and libmysqlclient18 for Ubuntu/Debian. Users wishing to build software against libperconaserverclient should install libperconaserverclient-dev package. An old version of Percona-built libmysqlclient will be available for download.

Bugs Fixed:

  • The XtraDB version number in univ.i was incorrect. Bug fixed #1277383.
  • Percona Toolkit UDFs were only shipped with RPM packages. Bug fixed #1159625.
  • A debug server build will crash if, while performing a bulk insert to a partitioned table, one of the partitions will return a failure for end_bulk_insert handler call. Bug fixed #1204871 (upstream #71270).
  • Percona Server 5.6 installation on Debian would fail due to default config reference to /etc/mysql/conf.d which didn’t exist. Bug fixed #1206648.
  • Due to a regression in the buffer pool mutex split, a combination of InnoDB compression, write workload, and multiple active purge threads could lead to a server crash. Bug fixed #1247021.
  • Server would crash on startup when XA support functions were activated by a second storage engine. Fix for this bug was ported from MariaDB. Bug fixed #1255549 (upstream #47134).
  • FLUSH STATUS could cause a server crash on the next transaction commit if two XA-supporting storage engines are in use. Fix for this bug was ported from MariaDB. Bugs fixed #1255551 (upstream #70854).
  • auth_pam.so shared library needed for PAM Authentication Plugin was missing from RPM packages. Bug fixed #1268246.
  • Fix for bug #1227581, a buffer pool mutex split regression, was not complete, thus a combination of write workload to InnoDB compressed table and a tablespace drop could crash the server. Bug fixed #1269352.
  • Binary RPM packages couldn’t be built from source tarballs on Fedora 19. Bug fixed #1229598.
  • Percona Server compilation with Performance Schema turned off would fail due to regression introduced by the 5.6 priority mutex framework. Bug fixed #1272747.
  • The InnoDB page cleaner thread could have incorrectly decided whether the server is busy or idle on some of its iterations and consequently issue a too big flush list flushing request on a busy server, causing performance instabilities. Bug fixed #1238039 (upstream #71988).
  • Percona Server had different server version value when installing from Source and from Binary/RPM. Bug fixed #1244178.
  • InnoDB did not handle the cases of asynchronous and synchronous I/O requests completing partially or being interrupted. Bugs fixed #1262500 (upstream #54430), and #1263087 (Andrew Gaul).
  • The fix for upstream bug #70768 may cause a high rate of RW lock creations and destructions, resulting in a performance regression on some workloads. Bug fixed #1279671 (upstream #71708).
  • Debian and Ubuntu packaging has been reworked to meet the packaging standards. Bug fixed #1281261.
  • Fixed the CMake warnings that were happening when Makefile was generated. Bugs fixed #1274827, upstream bug fixed #71089 and #1274411 (upstream #71094).
  • On Ubuntu Precise multiple architecture versions of libmysqlclient18 couldn’t be installed side by side. Bug fixed #1052636.
  • Percona Server source tree has been reorganized to match the MySQL source tree layout closer. Bug fixed #1014477.
  • Performance Schema autosizing heuristics have been updated to account for Percona Server-specific wait/synch/mutex/sql/THD::LOCK_temporary_tables mutex. Bug fixed #1264952.

Other bugs fixed: #1276445, #1005787, #1285064, #1229598, and #1277505 (upstream #71624).

[UPDATE 2014-03-12]: Changes that were made for Ubuntu/Debian packages may cause the warnings during the upgrade (in some cases package manager might warn you that you are doing a downgrade). It is safe to ignore the warning. You won’t have that warning in next versions. If you’re experiencing any issues during the upgrade/install process please report a bug. These changes have been done in order to improve our packaging quality.

Release notes for Percona Server 5.6.16-64.0 are available in our online documentation. Bugs can be reported on the launchpad bug tracker.

Comments

  1. Arnoldas says:

    Percona-Server-server-56-5.6.16-rel64.0.el6.x86_64 no TokuDB engine for CentOS yet? :(

    – Percona Server now has server-side support for TokuDB Compression option syntax.

    I want to try out TokuDB Compression and see how it works.

  2. Hrvoje Matijakovic says:

    @Arnoldas

    TokuDB is currently available only in the special Percona Server with TokuDB engine build described here: http://www.percona.com/doc/percona-server/5.6/tokudb/tokudb_installation.html#tokudb-installation

    CentOS packages are available from the yum testing repo. Once the repo is enabled you just need to install PS with TokuDB engine package:

    yum install Percona-Server-tokudb-56.x86_64

  3. Arnoldas says:

    @Hrvoje

    Thanks for explanation, I am on it, and my tests show very good results on compression with LZMA, just what I was looking for.

  4. Hrvoje, am I right, that this build is suitable for production use (instead of described in the your previous topic ALPHA one: http://www.mysqlperformanceblog.com/2014/03/03/percona-server-5-6-16-64-0-with-tokudb-engine-now-available/)?

  5. Hrvoje Matijakovic says:

    @Eugene

    Those two builds are different products. This is a standard GA release of Percona Server 5.6 (without the TokuDB engine). The other is a new release of Percona Server with TokuDB storage engine and it’s currently considered ALPHA quality.

  6. arekm says:

    libmysqlclient -> libperconaserverclient rename is crazy :-( Now it is not enough to install percona server as mysql replacement.

    You now also need to build and install mysql libmysqclient since all existing binary software links with libmysqclient.

    (using someone else old libmysqclient build is not a sane option obviously)

Speak Your Mind

*