Percona XtraDB Cluster 5.5.29-23.7.1

Percona is glad to announce the release of Percona XtraDB Cluster on January 30th, 2013. Binaries are available from downloads area or from our software repositories.

This is an General Availability release. 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.

Bugs fixed

In some cases when node is recovered variable threads_running would become huge. Bug fixed #1040108 (Teemu Ollakka).

Variable wsrep_defaults_file would be set up to the value in the last configuration file read. Bug fixed by keeping the value found in the top configuration file. Bug fixed #1079892 (Alex Yurchenko).

Variable wsrep_node_name was initialized before the glob_hostname, which lead to empty value for wsrep_node_name if it wasn’t set explicitly. Bug fixed #1081389 (Alex Yurchenko).

Running FLUSH TABLES WITH READ LOCK when slave applier needed to abort transaction that is on the way caused the deadlock situation. Resolved by grabbing Global Read Lock before pausing wsrep provider. Bug fixed #1083162 (Teemu Ollakka).

Percona XtraDB Cluster would crash when processing a delete for a table with foreign key constraint. Bug fixed #1078346 (Seppo Jaakola).

When variable innodb_support_xa was set to 0, wsrep position wasn’t stored into the InnoDB tablespace. Bug fixed #1084199 (Teemu Ollakka).

Using XtraBackup for State Snapshot Transfer would fail due to mktemp error. Bug fixed #1080829 (Alex Yurchenko).

XtraBackup donor would run XtraBackup indefinitely if the xtrabackup --tmpdir was on tmpfs. Bug fixed #1086978 (Alex Yurchenko).

In some cases non-uniform foreign key reference could cause a slave crash. Fixed by using primary key of the child table when appending exclusive key for cascading delete operation. Bug fixed #1089490 (Seppo Jaakola).

Percona XtraDB Cluster would crash when binlog_format was set to STATEMENT. This was fixed by introducing the warning message. Bug fixed #1088400 (Seppo Jaakola).

An explicitly set wsrep_node_incoming_address may make “SHOW STATUS LIKE 'wsrep_incoming_addresses';” return the address without the port number. Bug fixed #1082406 (Alex Yurchenko).

Percona XtraDB Cluster would crash if the node’s own address would be specified in the wsrep_cluster_address variable. Bug fixed #1099413. (Alexey Yurchenko)

When installing from yum repository, Percona-XtraDB-Cluster-server and Percona-XtraDB-Cluster-client would conflict with mysql and mysql-server packages. Bug fixed #1087506 (Ignacio Nin).

Other bug fixes: bug fixed #1037165, bug fixed #812059.

Based on Percona Server 5.5.29-29.4 including all the bug fixes in it, Percona XtraDB Cluster 5.5.29-23.7.1 is now the current stable release. All of Percona‘s software is open-source and free.

Percona XtraDB Cluster
Call Us
+1-888-316-9775 (USA - Sales)
+1-208-473-2904 (USA - Sales)
+44-208-133-0309 (UK - Sales)
0-800-051-8984 (UK - Sales)
0-800-181-0665 (GER - Sales)
+1-877-862-4316 (Emergency)
+1-855-55TRAIN (Training)
+1-925-271-5054 (Training)

Table Of Contents

Previous topic

Percona XtraDB Cluster 5.5.29-23.7.2

Next topic

Percona XtraDB Cluster 5.5.28-23.7

This Page



© Copyright 2012-2014, Percona LLC and/or its affiliates.
Except where otherwise noted, this documentation is licensed under the following license:
CC Attribution-ShareAlike 2.0 Generic
Created using Sphinx 1.1.3.
This documentation is developed in Launchpad as part of the Percona XtraDB Cluster source code.
If you spotted innacuracies, errors, don't understood it or you think something is missing or should be improved, please file a bug.
]]>