Announcing Percona XtraDB Cluster 5.5.29-23.7.1

Announcing 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.

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 might 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.
We did our best to eliminate bugs and problems, but this is a software, so bugs are expected. If you encounter them, please report them to our bug tracking system.


Share this post

Comments (8)

  • Patrik Reply


    source, deb and rpm but no binary release?

    January 31, 2013 at 7:38 am
  • Hrvoje Matijakovic Reply

    Hi Patrik,

    Binary release is now available as well.

    January 31, 2013 at 12:01 pm
  • Laurent Reply

    Hi Hrvoje Matijakovic,

    We did the upgrade to 5.5.29 on a Debian server with the Percona apt repository configured but got some problems with the upgrade which I listed/detailled on the 3rd post of this google groups topic :!topic/percona-discussion/bOEclT7K7o

    Do you have any informations or already reported/known problems with this upgrade please ?
    Moreover, do you have any clue of the cause of the errors we got please ?

    Thanks by advance.



    February 1, 2013 at 5:14 am
  • Hrvoje Matijakovic Reply

    Hi Laurent,

    Nobody reported any problems with this release yet.
    I’ve reported this as
    One of our build engineers will check it out, can you please subscribe to the bug in case any additional information is required.

    Thank you for reporting this,

    February 1, 2013 at 5:42 am
  • Laurent Reply

    Hi Hrvoje,

    Thanks for your quick reply and action.
    In parallel, I had some reply from another Galera/Percona XtraDB user on codership google groups that had the same behavior :!topic/codership-team/CgxIeofjJss

    I will subscribe to the bug entry on launchpad.



    February 1, 2013 at 6:37 am
  • Ahmed Medhat Reply


    I believe that the bug of RPM rhel5 packages conflicting with mysql/mysql-server/mysql-libs is still persistent in some form, I’ll try finding the bug and re-opening it however let me put a snippet here from attempting to update from the previous version 5.5.28-23.7.370.rhel5, I am sure that if I attempted to revert those changes within the SRPM I would successfully update the RPM since the old version gets installed/updated so easily without problems.

    [root@****]# ll
    total 33816
    drwxr-xr-x 2 root root 4096 Feb 3 23:05 .
    drw——- 12 root root 4096 Feb 3 23:04 ..
    -rw-r–r– 1 root root 9496400 Jan 30 18:44 Percona-XtraDB-Cluster-client-5.5.29-
    -rw-r–r– 1 root root 3665947 Jan 30 18:44 Percona-XtraDB-Cluster-devel-5.5.29-
    -rw-r–r– 1 root root 20427834 Jan 30 18:44 Percona-XtraDB-Cluster-server-5.5.29-
    -rw-r–r– 1 root root 1017261 Jan 30 18:44 Percona-XtraDB-Cluster-shared-5.5.29-

    [root@****]# yum localupdate *
    Loaded plugins: fastestmirror
    Setting up Local Package Process
    Examining Percona-XtraDB-Cluster-client-5.5.29- 1:Percona-XtraDB-Cluster-client-5.5.29-
    Marking Percona-XtraDB-Cluster-client-5.5.29- as an update to 1:Percona-XtraDB-Cluster-client-5.5.28-23.7.370.rhel5.x86_64
    Loading mirror speeds from cached hostfile
    * addons:
    * base:
    * epel:
    * extras:
    * updates:
    addons | 1.9 kB 00:00
    base | 1.1 kB 00:00
    epel | 3.7 kB 00:00
    extras | 2.1 kB 00:00
    updates | 1.9 kB 00:00
    Excluding Packages in global exclude list
    Examining Percona-XtraDB-Cluster-devel-5.5.29- 1:Percona-XtraDB-Cluster-devel-5.5.29-
    Marking Percona-XtraDB-Cluster-devel-5.5.29- as an update to 1:Percona-XtraDB-Cluster-devel-5.5.28-23.7.370.rhel5.x86_64
    Examining Percona-XtraDB-Cluster-server-5.5.29- 1:Percona-XtraDB-Cluster-server-5.5.29-
    Marking Percona-XtraDB-Cluster-server-5.5.29- as an update to 1:Percona-XtraDB-Cluster-server-5.5.28-23.7.370.rhel5.x86_64
    Examining Percona-XtraDB-Cluster-shared-5.5.29- 1:Percona-XtraDB-Cluster-shared-5.5.29-
    Marking Percona-XtraDB-Cluster-shared-5.5.29- as an update to 1:Percona-XtraDB-Cluster-shared-5.5.28-23.7.370.rhel5.x86_64
    Resolving Dependencies
    –> Running transaction check
    —> Package Percona-XtraDB-Cluster-client.x86_64 1:5.5.29- set to be updated
    —> Package Percona-XtraDB-Cluster-devel.x86_64 1:5.5.29- set to be updated
    —> Package Percona-XtraDB-Cluster-server.x86_64 1:5.5.29- set to be updated
    —> Package Percona-XtraDB-Cluster-shared.x86_64 1:5.5.29- set to be updated
    –> Finished Dependency Resolution

    Dependencies Resolved

    Package Arch Version Repository Size
    Percona-XtraDB-Cluster-client x86_64 1:5.5.29- /Percona-XtraDB-Cluster-client-5.5.29- 32 M
    Percona-XtraDB-Cluster-devel x86_64 1:5.5.29- /Percona-XtraDB-Cluster-devel-5.5.29- 8.4 M
    Percona-XtraDB-Cluster-server x86_64 1:5.5.29- /Percona-XtraDB-Cluster-server-5.5.29- 65 M
    Percona-XtraDB-Cluster-shared x86_64 1:5.5.29- /Percona-XtraDB-Cluster-shared-5.5.29- 3.4 M

    Transaction Summary
    Install 0 Package(s)
    Upgrade 4 Package(s)

    Total size: 109 M
    Is this ok [y/N]: y
    Downloading Packages:
    Running rpm_check_debug
    ERROR with rpm_check_debug vs depsolve:
    mysql conflicts with Percona-XtraDB-Cluster-client-5.5.29-
    mysql-devel conflicts with Percona-XtraDB-Cluster-devel-5.5.29-
    mysql-libs conflicts with Percona-XtraDB-Cluster-shared-5.5.29-
    mysql-server conflicts with Percona-XtraDB-Cluster-server-5.5.29-
    (1, [u’Please report this error in'])

    February 3, 2013 at 4:12 pm
  • Laurent Reply


    We hit a bug concerning this release and it seems this is 5.5.29 that introduced this bug as 5.5.28 is not concerned, I entered a bug entry on launchpad :

    Could it be possible that it’s related to the above mentionned fix against FK bugs mentionned in the ChangeLog please ? :
    – Percona XtraDB Cluster would crash when processing a delete for a table with foreign key constraint. Bug fixed #1078346 (Seppo Jaakola).
    – 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).



    February 6, 2013 at 7:51 am
  • Ahmed Medhat Reply


    Following up the rhel5 RPM upgrade/install problem, it looks like the fix applied for the Foreign Key resulting in a new test-build available through where it includes a fix for the RPM upgrade/install bug as well, though its not mentioned anywhere nor there were a reply added to the bug report followup.

    Regardless of all, thanks for fixing this issue as well.

    February 8, 2013 at 4:23 pm

Leave a Reply