Announcement of Percona XtraDB Cluster 5.5.23

Posted on:



Share Button

Our previous GA release of Percona XtraDB Cluster caused a lot of interest and feedback. I am happy to announce next version Percona XtraDB Cluster 5.5.23, which comes with bug fixes and improvements.

List of changes:

  • Fixes merged from upstream (Codership-mysql)
  • Support for MyISAM, now changes to MyISAM tables are replicated to other nodes
  • Improvements to XtraBackup SST methods, better error handling
  • New SST wsrep_sst_method=skip, useful when you start all nodes from the same sources (i.e. backup)
  • Ability to pass list of IP addresses for a new node, it will connect to the first available

Binaries are available from downloads area or from our repositories.

For this release we will provides binaries for Ubuntu 12.04, they are coming soon.

If you want to know more how to migrate to XtraDB Cluster, we will be giving a free webinar on June 6th.

This is an General Availability release. We did our best to eliminate bugs and problems during alpha and beta testing release, but this is a software, so bugs are expected. If you encounter them, please report to our bug tracking system.


Share Button

Vadim Tkachenko

Vadim leads Percona's development group, which produces the Percona Server, Percona Server for MongoDB, Percona XtraDB Cluster and Percona XtraBackup. He is an expert in solid-state storage, and has helped many hardware and software providers succeed in the MySQL market.

MySQL, Percona Software, XtraDB Cluster

  • Panagiotis Theodoropoulos

    Support for MyISAM, now changes to MyISAM tables are replicated to other nodes

    means is supported fulltext index and search?

  • Glad to see support for MyISAM tables! Just curious – how is this done without transactions?

  • Panagiotis,

    it is supported on level as MyISAM supports


    it works like global table lock for MyISAM table. As MyISAM is not transactional
    there is not much we can do it.

  • Thanks for this new version.
    The IP addresses list feature is a very good idea !

    I’d like to know if a feature that will permit to skip some bases (innodb or myisam) in the cluster will be announced soon ?
    Because actually we have to create another mysql instance to do this and it’s not really convenient.

  • Hi, is this release “production ready”?

  • Gilles,

    you can filter what tables to replicate using regular replication filter i.e. replicate_*,
    for it does not affect a node propagation. The new node still will copy all databases and instances.

  • Emanuelis,

    Yes, “This is a General Availability release.”

  • is there any documentation available?

  • Steve,

    You can get more information there

    Codership Wiki

  • Thanks for your answer but I don’t understand what you wanna mean about replicate_* filters.
    Those filters are used with mysql replication so it means that I have to configure replication on the node where I want to skip a database ?
    In this context i assume that the node has to be out of the cluster. Am I right ?

  • Gilles,

    You just set replicate_* filters in my.cnf per node and that node will filter events using that rule.

  • Guys,

    Thanks for adding MyISAM support to replication. When you get a chance add “wsrep_replicate_myisam=1” to the documentation :)

  • Hi Vadim,

    Does this version of Percona XtraDB Cluster includes fixes released by Codership with Galera 2.1 (https://launchpad.net/galera/2.x/23.2.1) on May 19th please ?
    For MySQL-wsrep patches 23.6 (https://launchpad.net/codership-mysql/5.5/5.5.23-23.6), I think the response is surely no since the percona version is 5.5.23-23.5-333.squeeze ?



  • Laurent,

    Changes made after May-14 is not included, but there should not be many of them.
    And we are going to have 5.5.24 release soon with all current fixes.

  • Hi Vadim,

    Thanks for these informations, I did see release 5.5.24 which solved my question !

    Could you please tell more informations about this feature ” Ability to pass list of IP addresses for a new node, it will connect to the first available ” ? I did not find anything related in the documentation.
    Is it related to the “wsrep_cluster_address” parameter and “gcomm” value please ? If it is, how do we pass multiple IP addresses for node to try to connect to please ?

    Thks by advance.


  • Laurent,

    This is “wsrep_urls” parameter in [mysqld_safe] section,
    so mysqld_safe script tries IPs one-by-one.

Leave a Reply