November 23, 2014

Percona XtraDB Cluster 5.6.15-25.4 is now available

Percona XtraDB Cluster 5.6
Percona is glad to announce the new release of Percona XtraDB Cluster 5.6 on February 20th 2014. 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.3 and on Codership wsrep API 5.6.15-25.2 is now the current General Availability 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.4 milestone at Launchpad.

Bugs fixed

  • Parallel Applying was not functioning which was evident from the wsrep_cert_deps_distance being 1.0 at all times. Bug fixed #1277703.
  • Binlog events were created for the statements for non-InnoDB tables, but they were never cleaned from transaction cache, which could lead to node crash. Bug fixed #1277986.
  • Percona XtraDB Cluster didn’t validate the parameters of wsrep_provider_options when node was being started. Bug fixed #1260193.
  • clustercheck script would mark node as down on Debian based systems if it was run with default values because it was looking for the defaults-extra-file in the wrong directory. Bug fixed #1276076.
  • Deadlock would happen when NULL unique key was inserted. Workaround has been implemented to support NULL keys, by using the md5 sum of full row as key value. Bug fixed #1276424
  • Variables innodb-log-group-home-dir and innodb-data-home-dir are now handled by default (ie., there is no need to set them up in sst_special_dirs). Bug fixed #1276904.
  • Builds now use system Zlib instead of bundled one. Bug fixed #1277928.
  • If transaction size exceeds the wsrep_max_ws_size limit, there will appear a warning message in the error log and replication is skipped. However, the transaction was committed in the master node, and cluster would be in inconsistent state. Bug fixed #1280557.
  • Variable wsrep_load_data_splitting defaults to OFF now, using it turned ON with autocommit set to 0 is not recommended.
  • Other bugs fixed: #1279844.

Release notes for Percona XtraDB Cluster 5.6.15-25.4 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.

Comments

  1. Laurent says:

    Hi,

    Congratulations for this second 5.6 release of PXDBC !

    Could you give a status about Query Cache in 5.6 releases of PXDBC please ? Not yet supported ?

    Regards,

    Laurent

  2. @Laurent,

    It is supported partially:

    “To enable query cache, mysqld should be started with query_cache_type=1 and query_cache_size=0 and then query_cache_size should be changed to desired value during runtime.”

    https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1279220 is the bug to remove these restrictions as well.

  3. Laurent says:

    Hi Raghavendra,

    Thanks for this information ! When you say “partially”, could you please detail on what is supported or not ? Same as what we go with 5.5.xx : avoid to use multi-master with query cache enabled and direct all requests to only one node for each database or some improvements were done please ?

    Regards.

    Laurent

Speak Your Mind

*