# Percona XtraDB Cluster 5.7.24-31.33 Is Now Available

**URL:** <https://forums.percona.com/t/percona-xtradb-cluster-5-7-24-31-33-is-now-available/6772>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [January 4, 2019, 8:15am UTC](https://forums.percona.com/t/percona-xtradb-cluster-5-7-24-31-33-is-now-available/6772 "2019-01-04T08:15:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hrvojem](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/hrvojem/32/6_2.png) [@hrvojem](https://forums.percona.com/u/hrvojem)\
**Post date:** [January 4, 2019, 8:15am UTC](https://forums.percona.com/t/percona-xtradb-cluster-5-7-24-31-33-is-now-available/6772/1 "2019-01-04T08:15:56Z")

</div>

Percona is glad to announce the release of Percona XtraDB Cluster 5.7.24-31.33 (PXC) on January 4, 2019. Binaries are available from the [downloads section](http://www.percona.com/downloads/Percona-XtraDB-Cluster-57/) or from our [software repositories](https://www.percona.com/doc/percona-xtradb-cluster/5.7/install/index.html).

Percona XtraDB Cluster 5.7.24-31.33 is now the current release, based on the following:  
[LIST]  
[_][Percona Server for MySQL 5.7.24](https://www.percona.com/doc/percona-server/5.7/release-notes/Percona-Server-5.7.24-26.html)  
[_]Galera Replication library 3.25  
[_]Galera/Codership WSREP API Release 5.7.24  
[/LIST]Deprecated  
The following variables are deprecated starting from this release:  
[LIST]  
[_]wsrep\_preordered was used to turn on transparent handling of preordered replication events applied locally first before being replicated to other nodes in the cluster. It is not needed anymore due to the [carried out performance fix](https://jira.percona.com/browse/PXC-2128) eliminating the lag in asynchronous replication channel and cluster replication.  
[_]innodb\_disallow\_writes usage to make InnoDB avoid writes during SST was deprecated in favor of the innodb\_read\_only variable.  
[LIST]  
[_]wsrep\_drupal\_282555\_workaround avoided the duplicate value creation caused by buggy auto-increment logic, but the correspondent bug is already fixed.  
[_]session-level variable binlog\_format=STATEMENT was enabled only for pt-table-checksum, which would be addressed in following releases of the Percona Toolkit.  
[/LIST]  
[/LIST]Fixed Bugs  
[LIST]  
[_][PXC-2220](https://jira.percona.com/browse/PXC-2220): Starting two instances of Percona XtraDB Cluster on the same node could cause writing transactions to a page store instead of a galera.cache ring buffer, resulting in huge memory consumption because of retaining already applied write-sets.  
[_][PXC-2230](https://jira.percona.com/browse/PXC-2230): rgcs.fc\_limit=0 not allowed as dynamic setting to avoid generating flow control on every message was still possible in my.cnf due to the inconsistent check.  
[_][PXC-2238](https://jira.percona.com/browse/PXC-2238): setting read\_only=1 caused race condition.  
[_][PXC-1131](https://jira.percona.com/browse/PXC-1131): mysqld-systemd threw an error at MySQL restart in case of non-existing error-log in Centos/RHEL7.  
[_][PXC-2269](https://jira.percona.com/browse/PXC-2269): being not dynamic, the pxc\_encrypt\_cluster\_traffic variable was erroneously allowed to be changed by a SET GLOBAL statement.  
[\*][PXC-2275](https://jira.percona.com/browse/PXC-2275): checking wsrep\_node\_address value in the wsrep\_sst\_common command line parser caused parsing the wrong variable.  
[/LIST]  
Help us improve our software quality by reporting any bugs you encounter using our [bug tracking system](https://jira.percona.com/). As always, thanks for your continued support of Percona!