Percona XtraDB Cluster 5.6.15-25.2 first Release Candidate is now available

Percona is glad to announce the first RC release of Percona XtraDB Cluster 5.6 on December 18th, 2013. Binaries are available from downloads area or from our software repositories.

Based on Percona Server 5.6.15-63.0 including all the bug fixes in it, Galera Replicator 3.2 and on Codership wsrep API 5.6.15-25.2 is now the first RELEASE CANDIDATE release. All of Percona‘s software is open-source and free, all the details of the release can be found in the 5.6.15-25.2 milestone at Launchpad.

New Features:

  • Percona XtraDB Cluster now supports stream compression/decompression with new xtrabackup-sst compressor/decompressor options.
  • New wsrep_reject_queries has been implemented that can be used to reject queries for that node. This can be useful if someone wants to manually run maintenance on the node like mysqldump without need to change the settings on the load balancer.
  • XtraBackup SST now supports innodb_data_home_dir and innodb_log_home_dir in the configuration file with sst_special_dirs option.
  • New wsrep_local_cached_downto status variable has been introduced. This variable shows the lowest sequence number in gcache. This information can be helpful with determining IST and/or SST.
  • Garbd init script and configuration files have been packaged for CentOS and Debian, in addition, in Debian garbd is packaged separately in percona-xtradb-cluster-garbd-3.x package.

Bugs Fixed:

  • When grastate.dat file was not getting zeroed appropriately it would lead to RBR error during the IST. Bug fixed #1180791.
  • init stop script on CentOS didn’t wait for the server to be fully stopped. This would cause unsuccessful server restart because the start action would fail because the daemon would still be running. Bug fixed #1254153.
  • DELETE FROM statement (without WHERE clause) would crash slaves if master did not have binlogging enabled. Bug fixed #1254179.
  • Missing protection for brute force threads against InnoDB lock wait time out would cause applier to fail with lock wait timeout exceeded on rsync SST donor. Bug fixed #1255501.
  • Recent optimizations in 3.x branch introduced a regression in base filename construction which could lead big transactions to fail with: WSREP: Failed to open file '...'. Bug fixed #1255964.
  • Joiner node would not initialize storage engines if rsync was used for SST and the first view was non-primary. Bug fixed #1257341.
  • Table level lock conflict resolving was releasing the wrong lock. Bug fixed #1257678.
  • Resolved the perl dependencies needed for Percona XtraDB Cluster 5.6. Bug fixed #1258563.
  • Obsolete dependencies have been removed from Percona XtraDB Cluster. Bug fixed #1259256.
  • CREATE TABLE AS SELECT process would remain hanging in case it was run in parallel with the DDL statement on the selected table. Bug fixed #1164893.
  • Naming of the Galera packages have been fixed to avoid the confusion, ie. Percona-XtraDB-Cluster-galera-56 is Percona-XtraDB-Cluster-galera-3 now. Bug fixed #1253923.
  • Fixed rsync SST for compatibility with rsync version 3.1.0. Bug fixed #1261673.

Other bugs fixed: #1261138 and #1254633.

Note: On CentOS 5/6, those who may have installed deprecated percona-xtrabackup-20 with Percona XtraDB Cluster 5.6 due to bug #1226185, the upgrade may fail, the dependency issue has been fixed since then, hence replace percona-xtrabackup-20 with percona-xtrabackup before upgrade.

Release notes for Percona XtraDB Cluster 5.6.15-25.2 are available in our online documentation along with the installation and upgrade instructions. We did our best to eliminate bugs and problems during the testing release, but this is a software, so bugs are expected. If you encounter them, please report them to our bug tracking system.

Percona XtraDB Cluster Errata can be found in our documentation.

Share this post

Comment (1)

  • Micu

    Is there an approximate date for the final release?


    January 10, 2014 at 3:32 am

Comments are closed.

Use Percona's Technical Forum to ask any follow-up questions on this blog topic.