You are here

Galera Cluster Release Notes

Source: Github: codership / documentation

Galera Plugin version 4 Series

Galera plug-in 26.4.9 Release Notes, Release Date: 26 July 2021

Galera plug-in 26.4.8 Release Notes, Release Date: 8 March 2021

Galera plug-in 26.4.7 Release Notes, Release Date: 14 January 2021

Galera plug-in 26.4.6 Release Notes, Release Date: 19 October 2020

Galera plug-in 26.4.5 Release Notes, Release Date: 20 May 2020

Galera Plugin version 3 Series

Galera plug-in 25.3.34 Release Notes, Release Date: 26 July 2021

Galera plug-in 25.3.33 Release Notes, Release Date: 8 March 2021

Galera plug-in 25.3.32 Release Notes, Release Date: 14 January 2021

Galera plug-in 25.3.31 Release Notes, Release Date: 19 October 2020

Galera plug-in 25.3.30 Release Notes, Release Date: 3 June 2020

Galera plug-in 25.3.29 Release Notes, Release Date: 28 January 2020

Galera plug-in 25.3.28 Release Notes, Release Date: 3 September 2019

Galera plug-in 25.3.27 Release Notes, Release Date: 19 July 2019

Galera plug-in 25.3.26 Release Notes, Release Date: 15 April 2019

Galera plug-in 25.3.25 Release Notes, Release Date: 27 November 2018

Galera plug-in 25.3.24 Release Notes, Release Date: 31 August 2018

Galera plug-in 25.3.23 Release Notes, Release Date: 6 February 2018

Galera plug-in 25.3.22 Release Notes, Release Date: 13 October 2017

Galera plug-in 25.3.21 Release Notes, Release Date: 4 July 2017

Galera plug-in 25.3.20 Release Notes, Release Date: 25 January 2017

Galera plug-in 25.3.19 Release Notes, Release Date: 8 November 2016

Galera plug-in 25.3.18 Release Notes, Release Date: 14 July 2016

Galera plug-in 25.3.17 Release Notes, Release Date: 9 August 2016

Galera plug-in 25.3.16 Release Notes, Release Date: 4 May 2016

Galera plug-in 25.3.15 Release Notes, Release Date: 12 March 2016

Galera plug-in 25.3.14 Release Notes, Release Date: 14 January 2016

Galera plug-in 25.3.13 Release Notes, Release Date: 6 November 2015

Galera plug-in 25.3.12 Release Notes, Release Date: 28 August 2015

Galera plug-in 25.3.10 Release Notes, Release Date: 18 March 2015

MySQL wsrep Server 8.0 Series

MySQL wsrep 8.0.25-26.7 Release Notes, Release Date: 23 July 2021

MySQL wsrep 8.0.23-26.6 Release Notes, Release Date: 7 April 2021

MySQL wsrep 8.0.22-26.5 Release Notes, Release Date: 14 January 2021

MySQL wsrep 8.0.21-26.4 Release Notes, Release Date: 19 October 2020

MySQL wsrep 8.0.19-26.3 Release Notes, Release Date: 20 May 2020

MySQL wsrep Server 5.7 Series

MySQL wsrep 5.7.34-25.26 Release Notes, Release Date: 26 July 2021

MySQL wsrep 5.7.33-25.25 Release Notes, Release Date: 8 March 2021

MySQL wsrep 5.7.32-25.24 Release Notes, Release Date: 14 January 2021

MySQL wsrep 5.7.31-25.23 Release Notes, Release Date: 19 October 2020

MySQL wsrep 5.7.30-25.22 Release Notes, Release Date: 3 June 2020

MySQL wsrep 5.7.29-25.21 Release Notes, Release Date: 28 January 2020

MySQL wsrep 5.7.28-25.20 Release Notes, Release Date: 24 October 2019

MySQL wsrep 5.7.27-25.19 Release Notes, Release Date: 3 September 2019

MySQL wsrep 5.7.26-25.18 Release Notes, Release Date: 19 July 2019

MySQL wsrep 5.7.25-25.17 Release Notes, Release Date: 18 April 2019

MySQL wsrep 5.7.24-25.16 Release Notes, Release Date: 27 November 2018

MySQL wsrep 5.7.23-25.15 Release Notes, Release Date: 31 August 2018

MySQL wsrep 5.7.21-25.14 Release Notes, Release Date: 31 January 2018

MySQL wsrep 5.7.20-25.13 Release Notes, Release Date: 28 October 2017

MySQL wsrep 5.7.18-25.12 Release Notes, Release Date: 2 July 2017

MySQL wsrep 5.7.17-25.11 Release Notes, Release Date: 25 January 2017

MySQL wsrep 5.7.15-25.10 Release Notes, Release Date: 3 October 2016

MySQL wsrep Server 5.6 Series

MySQL wsrep 5.6.51-25.33 Release Notes, Release Date: 8 March 2021

MySQL wsrep 5.6.50-25.32 Release Notes, Release Date: 14 January 2021

MySQL wsrep 5.6.49-25.31 Release Notes, Release Date: 19 October 2020

MySQL wsrep 5.6.48-25.30 Release Notes, Release Date: 3 June 2020

MySQL wsrep 5.6.47-25.29 Release Notes, Release Date: 28 January 2020

MySQL wsrep 5.6.46-25.28 Release Notes, Release Date: 24 October 2019

MySQL wsrep 5.6.45-25.27 Release Notes, Release Date: 3 September 2019

MySQL wsrep 5.6.44-25.26 Release Notes, Release Date: 19 July 2019

MySQL wsrep 5.6.43-25.25 Release Notes, Release Date: 18 April 2019

MySQL wsrep 5.6.42-25.24 Release Notes, Release Date: 27 November 2018

MySQL wsrep 5.6.41-25.23 Release Notes, Release Date: 31 August 2018

MySQL wsrep 5.6.39-25.22 Release Notes, Release Date: 31 January 2018

MySQL wsrep 5.6.38-25.21 Release Notes, Release Date: 25 October 2017

MySQL wsrep 5.6.36-25.20 Release Notes, Release Date: 2 July 2017

MySQL wsrep 5.6.35-25.19 Release Notes, Release Date: 25 January 2017

MySQL wsrep 5.6.34-25.18 Release Notes, Release Date: 8 November 2016

MySQL wsrep 5.6.33-25.17 Release Notes, Release Date: 14 September 2016

MySQL wsrep 5.6.31-25.16 Release Notes, Release Date: 9 August 2016

MySQL wsrep 5.6.30-25.15 Release Notes, Release Date: 4 May 2016

MySQL wsrep 5.6.29-25.14 Release Notes, Release Date: 12 March 2016

MySQL wsrep 5.6.28-25.13 Release Notes, Release Date: 14 January 2016

MySQL wsrep 5.6.27-25.12 Release Notes, Release Date: 16 November 2015

MySQL wsrep 5.6.25-25.11 Release Notes, Release Date: 27 August 2015

MySQL wsrep 5.6.23-25.10 Release Notes, Release Date: 18 March 2015

MySQL wsrep 5.6.21-25.9 Release Notes, Release Date: 16 March 2015

MySQL wsrep Server 5.5 Series

MySQL wsrep 5.5.62-25.25 Release Notes, Release Date: 27 November 2018

MySQL wsrep 5.5.61-25.24 Release Notes, Release Date: 31 August 2018

MySQL wsrep 5.5.59-25.23 Release Notes, Release Date: 31 January 2018

MySQL wsrep 5.5.58-25.22 Release Notes, Release Date: 25 October 2017

MySQL wsrep 5.5.55-25.21 Release Notes, Release Date: 29 June 2017

MySQL wsrep 5.5.54-25.20 Release Notes, Release Date: 25 January 2017

MySQL wsrep 5.5.53-25.19 Release Notes, Release Date: 8 November 2016

MySQL wsrep 5.5.52-25.18 Release Notes, Release Date: 14 September 2016

MySQL wsrep 5.5.50-25.17 Release Notes, Release Date: 9 August 2016

MySQL wsrep 5.5.49-25.16 Release Notes, Release Date: 4 May 2016

MySQL wsrep 5.5.48-25.15 Release Notes, Release Date: 12 March 2016

MySQL wsrep 5.5.47-25.14 Release Notes, Release Date: 14 January 2016

MySQL wsrep 5.5.46-25.13 Release Notes, Release Date: 16 November 2015

MySQL wsrep 5.5.45-25.12 Release Notes, Release Date: 27 August 2015

MySQL wsrep 5.5.42-25.11 Release Notes, Release Date: 18 March 2015

Galera Plugin version 4 Series

Galera plug-in 26.4.9 Release Notes

Notable changes and fixes in Galera since latest release 4.8:

  • Networking code was fixed to handle address already in use in graceful manner.
  • Applying of streaming replication write sets was made to respect applying order more reliably.
  • Too early transaction replay was fixed.
  • IST failure handling was improved to allow resuming IST after process restart.
  • A new status variable wsrep_apply_waits was introduced to count the number of times an applier thread had to wait for its turn to apply a write set.
  • An issue of having incorrect certification results right after SST was fixed.
  • Occasional excessive GCache CPU consumption during IST was fixed.
  • GCS flow control now allows write set replication more reliably when the node is in Donor state.
  • Gcache recovery reliability was improved.
  • Wsrep provider option socket.ssl_reload is now exposed when SSL is enabled.

Build fixes:

  • CRC32C detection was improved to work correctly with GCC 4.8.
  • CK_TIMEOUT_MULTIPLER was restored in Debian build scripts to reduce unit test timeouts during builds (codership/galera#558).
  • Tests which rely on the availability of UDP multicast were disabled by default (codership/galera#595).

Galera plug-in 26.4.8 Release Notes

Notable fixes in Galera replication since last release by Codership (4.7):

  • Recovery to wrong position after process was killed during IST was fixed (codership/galera#210).
  • Support for X509 certificate chains (codership/galera#571).
  • Improved SSL error messages to contain also certificate verification error reason.
  • SSL certificates may now be reloaded by setting socket.ssl_reload=1 provider option.
  • Upgrade path from non-SSL to SSL cluster with socket.dynamic=1 provider option. With this option enabled, the cluster will operate in mixed mode allowing nodes to communicate over both TCP and SSL connections.
  • OpenSSL version in binary tarball build was bumped to 1.1.1k.

Build fixes:


Galera plug-in 26.4.7 Release Notes

Notable fixes in Galera replication since last release by Codership (4.6):


Other changes:

  • Build system was changed from SCons to CMake. SCons scripts are still available, but will not be actively maintained.

Galera plug-in 26.4.6 Release Notes

Notable fixes in Galera replication since last binary release by Codership (4.5):

  • The in-memory GCache index implementation was reworked to use sorted std::deque instead of std::map, leading to eightfold reduction in GCache memory footprint.
  • CRC32C implementation was reworked. Hardware CRC32C is now supported on x86_64 and ARM64 platforms.
  • Bus error due to unaligned access on Sparc64 platform was fixed.
  • Three new status variables were added: wsrep_flow_control_active, wsrep_flow_control_requested and wsrep_gmcast_segment.
  • Prevent GCache rollover on Donor during IST.
  • Binary tarball package was added in this release.

Other changes:

  • Unit tests were reworked to replace deprecated Check library API calls with supported ones (codership/galera#577).

Galera plug-in 26.4.5 Release Notes

Notable new features in Galera 4 series are:

  • Streaming replication will improve execution of large transactions by splitting transaction replication and applying into small fragments.
  • Optimized write set certification rules will improve foreign key support by reducing the number of foreign key related false conflicts in certification.
  • Support for group commit.

Notable fixes in Galera replication since last source release (4.4):

  • Buffer overflow with auto-evict has been fixed.
  • All GCache ring buffer capacity was not always restored in GCache recovery. This has been now fixed.
  • Error handling during bad network conditions has been improved to make node to attempt to leave cluster gracefully if there is a possibility for data inconsistency.

Notable fixes in Galera replication since latest release candidate (4.5-rc):

  • Error handling during frequent cluster configuration changes was improved.
  • A segmentation fault with multicast was fixed.

Galera Plugin version 3 Series

Galera plug-in 25.3.34 Release Notes

Notable changes and fixes in Galera since latest release 3.33.

  • IST failure handling was improved to allow resuming IST after process restart.
  • A new status variable wsrep_apply_waits was introduced to count the number of times an applier thread had to wait for its turn to apply a write set.
  • An issue of having incorrect certification results right after SST was fixed.
  • Occasional excessive GCache CPU consumption during IST was fixed.
  • GCS flow control now allows write set replication more reliably when the node is in Donor state.
  • Gcache recovery reliability was improved.

Build fixes:

  • CRC32C detection was improved to work correctly with GCC 4.8.
  • CK_TIMEOUT_MULTIPLER was restored in Debian build scripts to reduce unit test timeouts during builds (codership/galera#558).

Galera plug-in 25.3.33 Release Notes

Notable fixes in Galera since latest release 3.32.

  • Recovery to wrong position after process was killed during IST was fixed (codership/galera#210).
  • OpenSSL version in binary tarball build was bumped to 1.1.1k.

Build fixes:


Galera plug-in 25.3.32 Release Notes

Notable fixes in Galera since latest release 3.31.


Other changes:

  • Build system was changed from SCons to CMake. SCons scripts are still available, but will not be actively maintained.

Galera plug-in 25.3.31 Release Notes

Notable fixes in Galera replication since last binary release by Codership (3.30):

  • The in-memory GCache index implementation was reworked to use sorted std::deque instead of std::map, leading to eightfold reduction in GCache memory footprint.
  • CRC32C implementation was reworked. Hardware CRC32C is now supported on x86_64 and ARM64 platforms.
  • Bus error due to unaligned access on Sparc64 platform was fixed.
  • Three new status variables were added: wsrep_flow_control_active, wsrep_flow_control_requested and wsrep_gmcast_segment.
  • Prevent GCache rollover on Donor during IST.
  • Incorrect handling of return value from SST donate callback was fixed (codership/galera#284).
  • Binary tarball package is compiled with OpenSSL 1.1.1g.

Other changes:

  • Unit tests were reworked to replace deprecated Check library API calls with supported ones (codership/galera#577).

Galera plug-in 25.3.30 Release Notes

Notable fixes in Galera replication since last binary release by Codership (3.29):

  • GCache recovery was fixed to reclaim all available space in ring buffer.
  • Error handling during frequent cluster configuration changes was improved.
  • A segmentation fault with multicast was fixed.

Galera plug-in 25.3.29 Release Notes

Notable fixes in Galera replication since last binary release by Codership (3.28):

  • A bug in GCS where JOIN message was delivered even if the node was in DONOR state was fixed.
  • An issue where GCache could contain mixed histories from different clusters was fixed.
  • Setting socket.recv_buf_size was not effective because it was done after the socket was connected or accepted. Also the default value caused TCP receive buffer autotuning to be disabled. This lead to suboptimal performance in high bandwidth WAN clusters.
    The default value for socket.recv_buf_size was changed to 'auto' which lets the kernel to tune TCP receive buffer. A new variable socket.send_buf_size with default value auto was added to allow also send buffer tuning.
    (codership/galera#552)
  • GComm socket timestamping/liveness checking caused false positives during replication of large transactions, which caused excessive amounts of broken connections. (codership/galera#553)
  • Large transactions were able to monopolize bandwidth when segmentation was configured. This caused messages which were relayed by segment representative to be delayed. As a fix implemented fair queuing of messages. (codership/galera#553)
  • GComm EVS layer did excessive broadcasting to retransmit missing messages when packets were lost or delayed. The communication protocol was optimized to use point-to-point messaging to deliver missing messages and to rate limit retransmission requests. (codership/galera#554)
  • Because of a bug in quorum computation, two primary conflicting primary components were formed when the group merged and partitioned again while the new primary view was forming.
    (codership/galera#563)

Galera plug-in 25.3.28 Release Notes

Notable fixes in Galera replication since last binary release by Codership (3.27):


Galera plug-in 25.3.27 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.26):

  • Prevent protocol downgrade on rolling upgrade (codership/galera#537)
  • Fixed GCache page store bus error on NVMFS

Galera plug-in 25.3.26 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.25):

  • Too early GCache page release in GCache page store was fixed.
  • A check for duplicate node UUID was added to prevent node to join the cluster if another node with the same UUID alrady exists (codership/galera#533).
  • Dynamic symbol dispatch was disabled in libgalera_smm.so to allow using the library with applications which may be built with different versions of C++ libraries than the Galera library.
  • Internal handling of IPv6 address square bracket notation and scope_id handling was fixed (codership/galera#519, codership/galera#534)

Galera plug-in 25.3.25 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.24):

  • A new Galera configuration parameter cert.optimistic_pa was added. If the parameter value is set to true, full parallellization in applying write sets is allowed as determined by certification algorithm. If set to false, no more parallellism is allowed in applying than seen on the master.
  • Support for ECDH OpenSSL engines on CentOS 6 (codership/galera#520)
  • Fixed compilation on Debian testing and unstable (codership/galera#516, codership/galera#528)

Galera plug-in 25.3.24 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.23):

  • A support for new certification key type was added to allow more relaxed certification rules for foreign key references (codership/galera#491).
  • New status variables were added to display the number of open transactions and referenced client connections inside Galera provider (codership/galera#492).
  • GCache was sometimes cleared unnecessarily on startup if the recovered state had smaller sequence number than the highest found from GCache.
    Now only entries with sequence number higher than recovery point will be cleared (codership/galera#498).
  • Non-primary configuration is saved into grastate.dat only when if the node is in closing state (codership/galera#499).
  • Exception from GComm was not always handled properly resulting in Galera to remain in half closed state. This was fixed by propagating the error condition appropriately to upper layers (codership/galera#500).
  • A new status variable displaying the total weight of the cluster nodes was added (codership/galera#501).
  • The value of pc.weight did not reflect the actual effective value after setting it via wsrep_provider_options. This was fixed by making sure that the new value is taken into use before returning the control back to caller (codership/galera#505, MDEV-11959)
  • Use of ECHD algorithms with old OpenSSL versions was enabled (codership/galera#511).
  • Default port value is now used by garbd if the port is not explicitly given in cluster address (MDEV-15531).
  • Correct error handling for posix_fallocate().
  • Failed causal reads are retried during configuration changes.

Galera plug-in 25.3.23 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.22):

  • Write set serialization has been changed to use proper memory alignment in order to avoid crashes on platforms which do not allow unaligned memory access (codership/galera#445)

Galera plug-in 25.3.22 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.21):

  • Reporting last committed write set fixed to respect commit ordering (MW-341)
  • GComm socket level error handling improved to avoid backend thread exit in case of unexpected input from ASIO IO service (GAL-518)
  • Race condition fixed in GComm message sending codepath (GAL-520)
  • Fix for EVS protocol stall due to exhausted send window setting. This bug could stall cluster messaging until the next keepalive was sent by some node, causing intermittent pauses in write set replication. (GAL-521)
  • Code changes to avoid name collisions with FreeBSD system headers (GAL-523)

Galera plug-in 25.3.21 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.20):

  • Galera now considers umask when creating gcache files (GAL-505, codership/galera#449)
  • Clean abort is ensured when core piping is used (GAL-505)
  • Node state is marked unsafe when slave executes TOI (GAL-504)
  • A bug in send monitor that could cause the node to stop replicating under heavy write load has been fixed. (GAL-495)
  • URI parsing has been improved for IPv6 addresses (GAL-501, GAL-338, codership/galera#338)
  • GCache recovery fixes (GAL-494, GAL-500)
  • IST progress is reported in the log (GAL-491)
  • Improved build time checks for ASIO version (GAL-510)

Galera plug-in 25.3.20 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.19):

  • Galera can now be compiled with OpenSSL 1.1.0 (GAL-445, codership/galera#407)
  • Included asio library would fail to compile with some compilers (GAL-445, codership/galera#407)
  • Compilation could fail when compiling on FreeBSD (GAL-476)
  • An assertion could happen with two consecutive DDLs run under RSU (GAL-480)
  • A scons option, system_asio=0 is now available to prevent using the system asio library when compiling Galera
  • Compilation could fail if attempting to compile Galera with GCC 6 (GAL-484)
  • An scons option, deterministic_tests=1, is now available to disable non-deterministic Galera unit tests (GAL-470, codership/galera#432)

Galera plug-in 25.3.19 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.18):

  • A new wsrep provider option, gcache.recover, enables gcache to be recovered at restart. This allows the restarted node to serve IST to any other nodes that are also starting, which may speed up whole-cluster restarts.
  • An additional protection against restarting a cluster using a node that may not have all the transactions has been implemented. Unless a node was the last one to be shut down from the previous cluster, Galera will refuse to bootstrap from it until explicit action is taken by the operator.
  • Galera would refuse to start on PPC64EL (lp:1633226, GAL-418)
  • Galera would crash or enter an infinite loop in the asio library (GAL-416)
  • It was not possible to set pc.wait_prim and pc.wait_prim_timeout options using wsrep_provider_options (GAL-360, codership/galera#360)
  • For security reasons, SSLv2, SSLv3, TLS 1.0 will no longer be negotiated during SSL handshake (codership/galera#428)

Galera plug-in 25.3.18 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.17):

  • After a certain pattern of server restarts, an isolated node could stop attempting to reconnect to the cluster (GCF-890)
  • Galera would fail to compile with clang 3.8 (codership/galera#412)
  • The wsrep_desync_count variable could show a wrong value (GAL-401)

Galera plug-in 25.3.17 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.16):

  • A receive buffer size of 208K is now used for intra-node communications. This avoids a situation where the cluster could stall or split when using high-latency, low-bandwidth network links. A new option, socket.recv_buf_size can be used to control the size of the buffer.
  • Experimental support for Ubuntu 16.04 Xenial is now available.
  • A node could crash if an invalid value is used for gcs.max_packet_size (codership/galera#414)
  • A node could crash if the SHOW STATUS command is used (codership/galera#408)

Galera plug-in 25.3.16 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.15):

  • A counter is now used to track the number of desync operations currently running
  • A new option, gcomm.thread_prio, allows specifying the priority of the gcomm thread
  • A new option, ist.recv_bind can be used to listen for IST requests on a particular interface

Galera plug-in 25.3.15 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.14):


Galera plug-in 25.3.14 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.13):

  • Use system ASIO library when compiling, if available (codership/galera#367)
  • improvements to Debian packages that allow a Galera library package downloaded from galeracluster.com to be used with Percona XtraDB Cluster and MariaDB Cluster

Galera plug-in 25.3.13 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.12):

  • The 'could not find key from cert index' warning will no longer be printed in certain situations (codership/galera#361)
  • Fix compilation on the latest Debian release (codership/galera#321)
  • Fix compilation on FreeBSD
  • Several fixes to the build scripts to support various distros and architectures (codership/galera#321)

Galera plug-in 25.3.12 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.10):


Galera plug-in 25.3.10 Release Notes

New features and notable fixes in Galera replication since last binary release by Codership (3.9):

  • Improved support for running garbd under systemd and other minor packaging improvements.

MySQL wsrep Server 8.0 Series

MySQL wsrep 8.0.25-26.7 Release Notes, Release Date: 23 July 2021

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.23-26.6:

  • Changing system variable wsrep_on value during multi statement transaction is not allowed (MDEV-25226).
  • SST scripts for rsync and xtrabackup-v2 SST methods now accept ssl-ca, ssl-cert and ssl-key configuration varibles either in [sst] or [mysqld] configuration section. The old variables tca, tcert and tkey are now deprecated but still accepted if they are present in [sst] section in the configuration file.
  • Binlog purging was disabled when the mysqld server was started with --wsrep-recover option (codership/mysql-wsrep#381).
  • Clone SST method reliability was improved.
  • Parallel applying of write sets to tables without primary key was disabled (MDEV-25551).
  • Both MDL and InnoDB locking was improved to handle cluster-wide conflicts more gracefully.
  • Parallel applying for Foreign Key parent delete was fixed to respect applying order.

XtraBackup compatibility:

  • Percona XtraBackup version 8.0.25-17.0 or higher is required to perform XtraBackup based SSTs.

Packaging:

  • A dependency to stunnel package was added as it is needed for rsync SST SSL support.

MySQL wsrep 8.0.23-26.6 Release Notes, Release Date: 7 April 2021

Notable fixes in Galera since latest release 3.32.

  • Recovery to wrong position after process was killed during IST was fixed (codership/galera#210).
  • OpenSSL version in binary tarball build was bumped to 1.1.1k.

Build fixes:


MySQL wsrep 8.0.22-26.5 Release Notes

Notable new features in MySQL-wsrep 8.0 since latest release 8.0.21-26.4.

  • A new SST method based on Clone plugin was added.
  • A new variable wsrep_mode was introduced to wsrep behavior. The first application of the variable is to allow ignoring native replication filter rules if configured with `replicate-do-db` (codership/mysql-wsrep#372).
  • Logging was improved to display the origin of wsrep-lib and Galera related messages. Log messages prefixed with `P` come from Galera library, messages prefixed with `L` come from wsrep-lib.

Notable fixes in MySQL-wsrep since latest release 8.0.21-26.4.

  • Load data failure with foreign keys was fixed (codership/mysql-wsrep#375).
  • PS protocol compatibility with MySQL-wsrep was improved.
  • FreeBSD compatibility for Xtrabackup v2 SST script was improved (codership/mysql-wsrep#379).
  • BF-BF conflicts between OPTIMIZE/REPAIR/ALTER TABLE and DML in precense of foreign key constraints were suppressed (MDEV-21577).
  • Due to regression in mysqld_safe script recovery step was skipped when starting MySQL server, causing full SST to be donated when IST should have taken place. This issue affected systems which do not use systemd. This has now been fixed.

MySQL wsrep 8.0.21-26.4 Release Notes

New features in MySQL-wsrep since latest release 8.0.19-26.3.

  • Audit log plugin was merged from Percona XTraDB Cluster.

Notable fixes in MySQL-wsrep since latest release 8.0.19-26.3.

  • Wsrep patch was reworked to work with CATS InnoDB transaction scheduling algorithm.
  • Deadlock between DDL and applying transaction was fixed.
  • Server crash when starting transaction with wsrep_on disabled was fixed.
  • Several memory leaks and memory access errors reported by AddressSanitizer were fixed.
  • Generic binary tarball package was included in this release.
  • Fix for vulnerability CVE-2020-15180.

MySQL wsrep 8.0.19-26.3 Release Notes

Notable new features in MySQL-wsrep 8.0 series are:

  • Streaming replication will improve execution of large transactions by splitting transaction replication and applying into small fragments.
  • Three new Galera system tables have been added into mysql database: wsrep_cluster, wsrep_cluster_members and wsrep_streaming_log. A database administrator has now a view in cluster membership status via system tables.
  • Better integration with MySQL binlog group commit provides higher transaction throughput.
  • New synchronization functions WSREP_LAST_SEEN_GTID(), WSREP_LAST_WRITTEN_GTID() and WSREP_SYNC_WAIT_UPTO_GTID() have been introduced to help applications to implement read-your-writes and monotonic-reads consistency guarantees.
  • Optimized write set certification rules will improve foreign key support by reducing the number of foreign key related false conflicts in certification.

Notable fixes in MySQL-wsrep since latest release candidate (8.0.19-26.3-rc)

  • Server crash on START TRANSACTION after INSERT IGNORE was fixed.

Deprecated features:

  • System variable wsrep_preordered has been deprecated and will be removed in a future release.
  • System variable wsrep_mysql_replication_bundle was deprecated and will be removed in a future release.

MySQL wsrep Server 5.7 Series

MySQL wsrep 5.7.34-25.26 Release Notes

Notable fixes in MySQL-wsrep since the latest release 5.7.33-25.25:

  • SST scripts for rsync and xtrabackup-v2 SST methods now accept ssl-ca, ssl-cert and ssl-key configuration variables either in [sst] or [mysqld] configuration section. The old variables tca, tcert and tkey are now deprecated but still accepted if they are present in [sst] section in the configuration file.
  • Binlog purging was disabled when the mysqld server was started with --wsrep-recover option (codership/mysql-wsrep#381).
  • Parallel applying of write sets to tables without primary key was disabled (MDEV-25551).

Packaging:

  • A dependency to stunnel package was added as it is needed for rsync SST SSL support.

MySQL wsrep 5.7.33-25.25 Release Notes

Notable fixes in MySQL-wsrep since the last binary release by Codership (5.7.32-25.24).

  • Fixed mysqldump SST script to keep general_log, slow_query_log global variable values intact on donor (codership/mysql-wsrep#108).
  • Hanging of mysqld --help --verbose command was fixed (codership/mysql-wsrep#381).
  • Audit log plugin missing from Debian packages was added.
  • OpenSSL version in binary tarball build was bumped to 1.1.1k.
  • Global variables wsrep_provider and wsrep_notify_cmd were made read-only.

MySQL wsrep 5.7.32-25.24 Release Notes

Notable new features in MYSQL-wsrep 5.7 since latest release 5.7.32-25.24.

  • A new variable wsrep_mode was introduced to wsrep behavior. The first application of the variable is to allow ignoring native replication filter rules if configured with replicate-do-db (codership/mysql-wsrep#372).

Notable fixes in MySQL-wsrep since the last binary release by Codership (5.7.32-25.24).

  • Load data splitting was fixed to generate Xid events for binlog events also for intermediate commits (codership/mysql-wsrep#376).
  • FreeBSD compatibility for Xtrabackup v2 SST script was improved (codership/mysql-wsrep#379).
  • Due to regression in mysqld_safe script recovery step was skipped when starting MySQL server, causing full SST to be donated when IST should have taken place. This issue affected systems which do not use systemd. This has now been fixed.

MySQL wsrep 5.7.31-25.23 Release Notes

Notable fixes in MySQL-wsrep since the last binary release by Codership (5.7.30-25.22).

  • Binary tarball package is compiled with OpenSSL 1.1.1g.
  • Deadlock between DDL and applying transaction was fixed.
  • Fix for the following security vulnerability CVE-2020-15180.

MySQL wsrep 5.7.30-25.22 Release Notes

Notable fixes in MySQL-wsrep since the last binary release by Codership (5.7.29-25.21).

  • Crash recovery was improved to more consistent recovery from crash when binlogs are enabled.
  • A segmentation fault during SSL initialization was fixed.
  • Error handling of cluster wide conflicts was improved for a cluster which is acting as asynchronous slave for native MySQL master.

New features:

  • Audit log plugin was added.

MySQL wsrep 5.7.29-25.21 Release Notes

Notable fixes in MySQL-wsrep since the last binary release by Codership (5.7.28-25.20).

  • Fixed occasional hang during server shutdown. Due to race condition a client connection got sometimes stuck in waiting for network event from invalid file descriptor.

MySQL wsrep 5.7.28-25.20 Release Notes

  • none?

MySQL wsrep 5.7.27-25.19 Release Notes

Notable bugs fixed in this release:


MySQL wsrep 5.7.26-25.18 Release Notes

Notable bugs fixed in this release:


MySQL wsrep 5.7.25-25.17 Release Notes

New features in MySQL-wsrep:

  • Packages for openSUSE Leap 15 and Ubuntu 18.04 Bionic Beaver were added in this release.

MySQL wsrep 5.7.24-25.16 Release Notes

New features in MySQL-wsrep:

  • Auth_pam and auth_dialog plugins were added in this release.
  • Support for Ubuntu/Bionic was added in this release.

Notable bug fixes in MySQL-wsrep:


MySQL wsrep 5.7.23-25.15 Release Notes

Notable bug fixes in MySQL-wsrep:

  • New configuration option wsrep_certification_rules to enable more relaxed certification rules for foreign key references on child table inserts. This option is effective only with Galera version 3.24 or higher (codership/galera#491).
  • Resource leak in case of ROLLBACK TO SAVEPOINT followed by COMMIT has been fixed (codership/mysql-wsrep#318).
  • Foreign Key constraint violation in applier after ALTER TABLE ADD FOREIGN KEY was fixed by adding both parent and child table keys into ALTER TOI write set (codership/mysql-wsrep#332).
  • Possible node hang with conflicting inserts in Foreign Key child table was fixed (codership/mysql-wsrep#335).
  • Memory leak with native MySQL replication when InnoDB was used as a relay log info and master info repository has been fixed (codership/mysql-wsrep#329).

MySQL wsrep 5.7.21-25.14 Release Notes

Notable bug fixes in MySQL-wsrep:

  • Changing the variable wsrep_slave_threads was not effective after a node drops from the cluster and then joins back (codership/mysql-wsrep#319)

MySQL wsrep 5.7.20-25.13 Release Notes

Notable bug fixes in MySQL-wsrep:

  • Preserve --wsrep-recover log for future reference when starting the server. The preserved log is stored in a file under MySQL data directory, either in wsrep_recovery.ok or wsrep_recovery.fail depending on recovery success. (MW-318)
  • Avoid returning outdated values for wsrep_ready status variable (MW-384)
  • A bug which caused stored procedure with an error handler to commit a statement even in case of certification error was fixed. (MW-388)
  • Crash during LOAD DATA for partition engine was fixed (MW-394)
  • Fixed a crash caused by a dangling reference to wsrep status variables array. (MW-399)
  • Fixes to processing of foreign key cascades. (MW-402)
  • ACL checks are now enforced before replication for all DDL operations (MW-416)
  • ALTER EVENT statement failure on slave was fixed (MW-417)

MySQL wsrep 5.7.18-25.12 Release Notes

Notable bug fixes in MySQL-wsrep:

  • Fix for thread leak when changing the value of wsrep_slave_threads (MW-336)
  • The issue of DROP TABLE containing temporary tables resulting in binlog divergence has been fixed (MW-360)
  • RESET MASTER is now rejected if the wsrep provider is enabled and gtid_mode is ON (MW-362)
  • InnoDB buffer pool is not dumped anymore at server shutdown when --wsrep-recover option is given (MW-365)
  • Improved IPv6 support (MW-366)
  • Fixes for certfication key generation in the presence of foreign key constraints (MW-369)
  • Fix to debug assertion MW-379
  • SHOW STATUS will not block any more with wsrep_sync_wait=1 (MW-86)

MySQL wsrep 5.7.17-25.11 Release Notes

Notable changes in this release:
  • If needed, initialization of the initial MySQL database can be performed using the --initialize command:
    sudo /usr/sbin/mysqld --user=mysql --initialize --log-error=/tmp/mysqld_initialize.log
  • On systemd systems, bootstrapping the first node of the cluster is performed using the following command:
    sudo /usr/bin/mysqld_bootstrap

Notable bug fixes in MySQL-wsrep:

  • Using Galera cluster as an asynchronous replication slave with replication filtering could cause holes to form in the GTID sequence (MW-319)
  • An assertion could occur if --wsrep_log_conflicts=ON is used and the server was compiled with assertions enabled (MW-28, codership/mysql-wsrep#28)
  • If Galera had to perform transaction replaying on a particular transaction, the "affected rows" field in the message returned to the client could be incorrect (MW-329)
  • An "OK" message could be sent to the client even if a query was aborted due to a transaction conflict (MW-328)
  • An error about a transaction conflict could be delivered to the next client statement, rather than the statement it was about (MW-328)
  • Compilation with GCC 6 has been fixed (MW-332)
  • Running a ROLLBACK TO SAVEPOINT statement could cause the cluster to hang (MW-253)

MySQL wsrep 5.7.15-25.10 Release Notes

Notable changes in this release:

  • If needed, initialization of the initial MySQL database can be performed using the --initialize command:
    sudo /usr/sbin/mysqld --user=mysql --initialize --log-error=/tmp/mysqld_initialize.log
  • On systemd systems, bootstrapping the first node of the cluster is performed using the following command:
    sudo /usr/bin/mysqld_bootstrap

MySQL wsrep Server 5.6 Series

MySQL wsrep 5.6.51-25.33 Release Notes

  • Fixed mysqldump SST script to keep general_log, slow_query_log global variable values intact on donor (codership/mysql-wsrep#108).
  • Audit log plugin missing from Debian packages was added.
  • OpenSSL version in binary tarball build was bumped to 1.1.1k.
  • Global variables wsrep_provider and wsrep_notify_cmd were made read-only.

MySQL wsrep 5.6.50-25.32 Release Notes

Known issues with this release:

  • If using the Ubuntu 16.04 Xenial package, the server can not be bootstrapped using systemd. Please use the SysV init script with the bootstap option to bootstrap the node. Note that a server that has been started that way can not be controlled via systemd and must be stopped using the SysV script. Normal server startup and shutdown is possible via systemd.
  • Server cannot be started using 'service' command on Debian Stretch.

MySQL wsrep 5.6.49-25.31 Release Notes

Notable fixes in MySQL-wsrep since the last binary release by Codership (5.6.48-25.30).

  • Binary tarball package is compiled with OpenSSL 1.1.1g.
  • Deadlock between DDL and applying transaction was fixed.
  • Fix for security vulnerability CVE-2020-15180.

MySQL wsrep 5.6.48-25.30 Release Notes

Notable fixes in MySQL-wsrep since the last binary release by Codership (5.6.47-25.29).

  • Crash recovery was improved to more consistent recovery from crash when binlogs are enabled.
  • A segmentation fault during SSL initialization was fixed.
  • Error handling of cluster wide conflicts was improved for a cluster which is acting as asynchronous slave for native MySQL master.

MySQL wsrep 5.6.47-25.29 Release Notes

  • none?

MySQL wsrep 5.6.46-25.28 Release Notes

  • none?

MySQL wsrep 5.6.45-25.27 Release Notes

  • none?

MySQL wsrep 5.6.44-25.26 Release Notes

  • none?

MySQL wsrep 5.6.43-25.25 Release Notes

  • none?

MySQL wsrep 5.6.42-25.24 Release Notes

New features in MySQL-wsrep:

  • Auth_pam and auth_dialog plugins were added in this release.

Notable bug fixes in MySQL-wsrep:


MySQL wsrep 5.6.41-25.23 Release Notes

  • New configuration option wsrep_certification_rules to enable more relaxed certification rules for foreign key references on child table inserts. This option is effective only with Galera version 3.24 or higher (codership/galera#491).
  • Fixed a resource leak in case of ROLLBACK TO SAVEPOINT which was followed by COMMIT (codeship/mysql-wsrep#318).
  • InnoDB undo tablespaces are now included in rsync SST (mysql-wsrep#337).
  • Foreign Key constraint violation in applier after ALTER TABLE ADD FOREIGN KEY was fixed by adding both parent and child table keys into ALTER TOI write set (codeship/mysql-wsrep#332).
  • Memory leak with native MySQL replication when InnoDB was used as a relay log info and master info repository has been fixed. (codeship/mysql-wsrep#329).

MySQL wsrep 5.6.39-25.21 Release Notes

Notable bug fixes in MySQL-wsrep:

  • Changing the variable wsrep_slave_threads was not effective after a node drops from the cluster and then joins back (codeship/mysql-wsrep#319)

MySQL wsrep 5.6.38-25.21 Release Notes

Notable bug fixes in MySQL-wsrep:

  • Preserve --wsrep-recover log for future reference when starting the server. The preserved log is stored in a file under MySQL data directory, either in wsrep_recovery.ok or wsrep_recovery.fail depending on recovery success. (MW-318)
  • Avoid returning outdated values for wsrep_ready status variable (MW-384)
  • A bug which caused stored procedure with an error handler to commit a statement even in case of certification error was fixed. (MW-388)
  • Crash during LOAD DATA for partition engine was fixed (MW-394)
  • Fixed a crash caused by a dangling reference to wsrep status variables array. (MW-399)
  • Fixes to processing of foreign key cascades. (MW-402)
  • ACL checks are now enforced before replication for all DDL operations (MW-416)

MySQL wsrep 5.6.36-25.20 Release Notes

Notable bug fixes in MySQL-wsrep:

  • CREATE TABLE AS SELECT fixes (MW-317, MW-322)
  • Fix for thread leak when changing the value of wsrep_slave_threads (MW-336)
  • The issue of DROP TABLE containing temporary tables resulting in binlog divergence has been fixed (MW-360)
  • RESET MASTER is now rejected if the wsrep provider is enabled and gtid_mode is ON (MW-362)
  • InnoDB buffer pool is not dumped anymore at server shutdown when --wsrep-recover option is given (MW-365)
  • Improved IPv6 support (MW-366)
  • Fixes for certfication key generation in the presence of foreign key constraints (MW-369)
  • SHOW STATUS will not block anymore with wsrep_sync_wait=1 (MW-86)

MySQL wsrep 5.6.35-25.19 Release Notes

Notable bug fixes in MySQL-wsrep:

  • Using Galera cluster as an asynchronous replication slave with replication filtering could cause holes to form in the GTID sequence (MW-319)
  • An assertion could occur if --wsrep_log_conflicts=ON is used and the server was compiled with assertions enabled (MW-28, codeship/mysql-wsrep#28)
  • If Galera had to perform transaction replaying on a particular transaction, the "affected rows" field in the message returned to the client could be incorrect (MW-329)
  • An "OK" message could be sent to the client even if a query was aborted due to a transaction conflict (MW-328)
  • An error about a transaction conflict could be delivered to the next client statement, rather than the statement it was about (MW-328)
  • Compilation with GCC 6 has been fixed (MW-332)
  • Running a ROLLBACK TO SAVEPOINT statement could cause the cluster to hang (MW-253)

New features, notable changes and bug fixes in Oracle MySQL 5.6.35:

  • Incompatible Change: The mysqld_safe script has been fortified against various security vulnerabilities
  • INSERT operations on a table with an AUTO_INCREMENT key could result in a duplicate key error (Bug #76872))

MySQL wsrep 5.6.34-25.18 Release Notes

Notable bug fixes in MySQL-wsrep:


New features, notable changes and bug fixes in Oracle MySQL 5.6.34:

  • Incompatible change: The behavior of the --secure_file_priv option has changed and additional checks are performed on the value at server startup. The default value on most platforms has been changed to /var/lib/mysql-files. That directory is created at package installation time.
  • The yaSSL library has been upgraded to 2.4.2.

  • MySQL wsrep 5.6.33-25.17 Release Notes

    Notable bug fixes in MySQL-wsrep:


    New features, notable changes and bug fixes in Oracle MySQL 5.6.32 and 5.6.33:

    • CVE-2016-6662. An authenticated remote user could leverage the mysqld_safe script to obtain elevated local privileges;
    • It was possible to write log files ending with .ini or .cnf that later could be parsed as option files. The general query log and slow query log can no longer be written to a file ending with .ini or .cnf. (Bug #24388753)
    • Privilege escalation was possible by exploiting the way REPAIR TABLE used temporary files. (Bug #24388746)
    • Multiple buffer overflows were fixed

    MySQL wsrep 5.6.31-25.16 Release Notes

    New features and notable changes in MySQL-wsrep since last binary release by Codership (5.6.30):

    • An experimental package for Ubuntu 16.04 Xenial is now available. Please see below for more information.
    • The wsrep_max_ws_rows variable has been fixed and can be used to set the maximum number of rows a transaction can update, delete or insert. The new default value is 0, meaning no limit.
    • The wsrep_max_ws_size variable and the repl.max_ws_size wsrep provider option have been linked together. The new wsrep_max_ws_size default is 2Gb.
    • If the master becomes non-Primary and starts returning "Unknown error", an async slave that is using the MySQL-wsrep packages will keep retrying rather than stop immediately (MW-284)

    Notable bug fixes in MySQL-wsrep:

    • The server returned stale values from the NOW() function if transaction replay has happened on the connection.
    • Updating the wsrep_provider_options while the server was running could cause a memory leak (MW-175)
    • A spurious deadlock error could be returned if wsrep_on is set to OFF (MW-286)
    • The server could crash with a broken foreign key constraint (MW-285)

    New features, notable changes and bug fixes in Oracle MySQL 5.6.31:

    • Potential buffer overflow issues were fixed.

    MySQL wsrep 5.6.30-25.15 Release Notes

    New features and notable changes in MySQL-wsrep since last binary release by Codership (5.6.29):

    • DDL statements are no longer recorded in the general log on the slaves (MW-44)
    • a new status variable wsrep_desync_count, shows the number of desync operations currently in progress. The node syncs back to the cluster after the counter is back to zero

    New features, notable changes and bug fixes in MySQL 5.6.30:

    • mysql client programs now support the --ssl-mode option that can be used to force encryption to be used
    • replicating a DROP TABLE statement could fail under certain situations (Bug #77684, Bug #21435502, Bug #20797764, Bug #76493)
    • Improper host name checking in X509 certificates could permit man-in-the-middle attacks. (Bug #22295186, Bug #22738607)

    MySQL wsrep 5.6.29-25.14 Release Notes

    New features and notable changes in MySQL-wsrep since last binary release by Codership (5.6.28):

    • A new variable, wsrep_dirty_reads can be used to enable reading from a non-primary node
    • A new variable, wsrep_reject_queries can be used to instruct a node to reject incoming queries or terminate existing connections
    • Issuing FLUSH TABLES WITH READ LOCK will cause the node to stop participating in flow control so that the other nodes do not become blocked (MW-252)
    • The wsrep_sst_xtrabackup script has been updated from the upstream project
    • A Contribution agreement was added in order to facilitate future contributions to the project

    Notable bug fixes in MySQL-wsrep:

    • If wsrep_desync is already set, running DDL under RSU could fail (MW-246)
    • Wrong AUTO_INCREMENT values could be generated if Galera was a slave to an asyncronous master that is using STATEMENT replication (MW-248)
    • If a prepared statement was a victim of a conflict and Galera attempted to rerun it, the slave could abort (MW-255)

    New features and notable changes and bug fixes in MySQL 5.6.29:

    • yaSSL has been upgraded to version 2.3.9
    • A new session variable --innodb-tmpdir can be used to specify a separate temporary directory for ALTER TABLE operations
    • DROP TABLE statements that contain non-regular characters may cause replication to break (MySQL Bug #77249)

    MySQL wsrep 5.6.28-25.13 Release Notes

    New features and notable changes in MySQL-wsrep since last binary release by Codership (5.6.27):

    • If a query such as CREATE USER needs to be printed to the error log, any plaintext passwords will be obfuscated (codeship/mysql-wsrep#216)
    • All SHOW CREATE and SHOW CODE commands now observe the wsrep_sync_wait variable (codeship/mysql-wsrep#228)

    Notable bug fixes in MySQL-wsrep:


    New features and notable changes in MySQL 5.6.28:

    • Miscellaneous bug fixes in InnoDB
    • More error conditions when writing to the binary log are caught and handled based on the value of the binlog_error_action variable

    MySQL wsrep 5.6.27-25.12 Release Notes

    New features and notable changes in MySQL-wsrep since last binary release by Codership (5.6.25):

    • A "compat" package is now provided to allow MySQL-wsrep to be installed without removing packages such as Postfix which depend on older MySQL versions
    • The MySQL-wsrep packages are now built with OpenSSL rather than YaSSL (codeship/mysql-wsrep#121)
    • Galera error messages have been enhanced to contain the current schema name along with the query (codeship/mysql-wsrep#202)

    Notable bug fixes in MySQL-wsrep:


    New features and notable changes in MySQL 5.6.26 - 5.6.27:

    • security fix for the LogJam issue. The key length used for creating Diffie-Hellman keys has been increased to 2,048 bits.
    • yaSSL was upgraded to version 2.3.8
    • Miscellaneous fixes in InnoDB

    MySQL wsrep 5.6.25-25.11 Release Notes

    Codership (5.6.23):


    Notable bug fixes in MySQL-wsrep:

    • In mysqldump SST, the path to my.cnf file is passed to mysqldump, so that mysqldump-related options are read even if the my.cnf file is not in a default location (codeship/mysql-wsrep#153)
    • ROLLBACK TO SAVEPOINT inside a trigger could cause an assertion (codeship/mysql-wsrep#110)
    • The server could crash if wsrep_OSU_method was changed while a DDL was running (codeship/mysql-wsrep#90)

    New features and notable changes in MySQL 5.6.24 - 5.6.25:

    • Certain ALTER TABLE statements involving temporal columns can now avoid a table copy;
    • a new automatic_sp_privileges prevents different privilege settings on master and slave when running CREATE PROCEDURE
    • mysqlbinlog can now be used to replay log events, including GRA files, larger than 1.6Gb.

    Known issues with this release:

    • There is a package conflict on CentOS 6/7 which requires manual removal of postfix, mysql and mariadb libraries before installing mysql-wsrep

    MySQL wsrep 5.6.23-25.10 Release Notes

    Notable bug fixes in MySQL-wsrep since last binary release by Codership (5.6.21):

    • getifaddr() rather than ifconfig is used to detect the IP of the node, resulting in better compatibility with newer Linux distributions (codeship/mysql-wsrep#45).

    New features and notable changes in MySQL 5.6.22 - 5.6.23:

    • Support for SSL 2.0 and 3.0 has been disabled as they provide weak encryption;
    • yaSSL was upgraded to version 2.3.7;
    • Numerous fixes in InnoDB and native MySQL replication;

    MySQL wsrep 5.6.21-25.9 Release Notes

    New features and notable changes in MySQL-wsrep since last binary release by Codership (5.6.16):

    • The wsrep_causal_reads variable has been deprecated. A new variable, wsrep_sync_wait, has been introduced to allow causal checks to be specified separately for selects, updates and inserts (lp:1277053)
    • Improvements in the replication of events (lp:1312618)
    • SST is governed by a timeout so that the joiner does not hang if the donor dies (lp:1292991)
    • Table administration commands such as CHECK TABLE are now replicated (lp:1046726)

    New features and notable fixes in Galera replication since last binary release by Codership (3.5):

    • CRITICAL: fixed writeset fragmentation bug that could cause GTID inconsistency (codeship/galera#185)
    • Automatic node eviction: unstable nodes can be removed from the cluster if they fail to consistenly respond to heartbeat messages
    • Intelligent donor selection: the cluster will attempt to select a donor that can serve IST
    • A new provider option, pc.recovery, facilitates restart in case of a full cluster crash
    • A new status variable, wsrep_evs_repl_latency, displays the current latency within the cluster
    • SSL connections between nodes will now fail if there is no peer certificate (codeship/galera#188) plus numerous other fixes and enhancements.

    Notable bug fixes in MySQL-wsrep:


    New features and notable changes in MySQL 5.6.17 - 5.6.21:

    • InnoDB tables can be rebuilt in place using online DDL
    • DTrace Support
    • Numerous fixes in InnoDB and native MySQL replication

    MySQL wsrep Server 5.5 Series

    MySQL wsrep 5.5.62-25.25 Release Notes

    Notable bug fixes in MySQL-wsrep:

    • Maximum variable length was increased to 4096 in order to work around wsrep_provider_options truncation if the provider options string contains long variable values (codeship/mysql-wsrep#348).

    MySQL wsrep 5.5.61-25.24 Release Notes

    Notable bug fixes in MySQL-wsrep:

    • New configuration option wsrep_certification_rules to enable more relaxed certification rules for foreign key references on child table inserts. This option is effective only with Galera version 3.24 or higher (codership/galera#491).
    • Resource leak in case of ROLLBACK TO SAVEPOINT followed by COMMIT has been fixed (codeship/mysql-wsrep#318).
    • Foreign Key constraint violation in applier after ALTER TABLE ADD FOREIGN KEY was fixed by adding both parent and child table keys into ALTER TOI write set (codeship/mysql-wsrep#332).

    MySQL wsrep 5.5.29-25.23 Release Notes

    • none?

    MySQL wsrep 5.5.58-25.22 Release Notes

    Notable bug fixes in MySQL-wsrep:

    • Avoid returning outdated values for wsrep_ready status variable (MW-384)
    • Crash during LOAD DATA for partition engine was fixed (MW-394)
    • Fixes to processing of foreign key cascades. (MW-402)
    • ACL checks are now enforced before replication for all DDL operations (MW-416)

    MySQL wsrep 5.5.55-25.21 Release Notes

    Notable bug fixes in MySQL-wsrep:

    • CREATE TABLE AS SELECT fixes (MW-322)
    • Fixes for certification key generation in the presence of foreign key constraints (MW-369)

    MySQL wsrep 5.5.54-25.20 Release Notes

    Notable bug fixes in MySQL-wsrep:

    • Compilation with GCC 6 has been fixed (MW-332)

    Notable fixes in Oracle MySQL Community Edition 5.5.54:

    • Incompatible Change: The mysqld_safe script has been fortified against various security vulnerabilities

    MySQL wsrep 5.5.53-25.19 Release Notes

    Notable fixes in Oracle MySQL Community Edition 5.5.53:

    • Incompatible change: The behavior of the --secure_file_priv option has changed and additional checks are performed on the value at server startup. The default value on most platforms has been changed to /var/lib/mysql-files. That directory is created at package installation time.
    • The yaSSL library has been upgraded to 2.4.2.

    MySQL wsrep 5.5.52-25.18 Release Notes

    Notable fixes in Oracle MySQL Community Edition 5.5.51, 5.5.52:

    • CVE-2016-6662. An authenticated remote user could leverage the mysqld_safe script to obtain elevated local privileges;
    • It was possible to write log files ending with .ini or .cnf that later could be parsed as option files.
      The general query log and slow query log can no longer be written to a file ending with .ini or .cnf. (Bug #24388753)
    • Privilege escalation was possible by exploiting the way REPAIR TABLE used temporary files. (Bug #24388746)
    • Multiple buffer overflows were fixed

    MySQL wsrep 5.5.50-25.17 Release Notes

    New features and notable changes in MySQL-wsrep since last binary release by Codership (5.5.49):

    • An experimental package for Ubuntu 16.04 Xenial is now available. Please see below for more information.

    Notable bug fixes in MySQL-wsrep:

    • The server returned stale values from the NOW() function if transaction replay has happened on the connection.

    Notable fixes in Oracle MySQL Community Edition 5.5.50:

    • Several potential buffer overflow issues have been fixed.

    MySQL wsrep 5.5.49-25.16 Release Notes

    Notable fixes in MySQL 5.5.49:
    • mysql client programs now support the --ssl-mode option that can be used to force encryption to be used

    MySQL wsrep 5.5.48-25.15 Release Notes

    Notable fixes in MySQL 5.5.48:
    • yaSSL has been upgraded to version 2.3.9
    • DROP TABLE statements that contain non-regular characters may cause replication to break (MySQL Bug #77249)

    MySQL wsrep 5.5.47-25.14 Release Notes

    Notable bug fixes in MySQL-wsrep 5.5.47:

    • Limit binlog recovery so that the wsrep position found from storage engines is not exceeded. This is required to have consistent position between wsrep position stored in InnoDB header and recovered binlog (codeship/mysql-wsrep#226)

    MySQL wsrep 5.5.46-25.13 Release Notes

    New features and notable changes in MySQL-wsrep since last binary release by Codership (5.5.45):

    • A "compat" package is now provided to allow MySQL-wsrep to be installed without removing packages such as Postfix which depend on older MySQL versions

    Notable bug fixes in MySQL-wsrep:


    New features and notable changes in MySQL 5.5.46:

    • yaSSL was upgraded to version 2.3.8
    • Miscellaneous fixes in InnoDB

    MySQL wsrep 5.5.45-25.12 Release Notes

    New features and notable changes in MySQL-wsrep since last binary release by Codership (5.5.42):


    Notable bug fixes in MySQL-wsrep:

    • In mysqldump SST, the path to my.cnf file is passed to mysqldump, so that mysqldump-related options are read even if the my.cnf file is not in a default location (codeship/mysql-wsrep#153)

    New features and notable changes in MySQL 5.5.43 - 5.5.45:

    • Security: The key length for creating Diffie-Hellman keys has been increased from 512 to 2,048 bits
    • MySQL can now compile with OpenSSL 0.9.8e.
    • Miscelaneous fixes in InnoDB

    MySQL wsrep 5.5.42-25.11 Release Notes

    New features and notable changes in MySQL-wsrep since last binary release by Codership (5.5.37):

    • The wsrep_causal_reads variable has been deprecated. A new variable, wsrep_sync_wait, has been introduced to allow causal checks to be specified separately for selects, updates and inserts (lp:1277053)
    • improved support for distributions based on the .deb package format, such as Ubuntu.

    Notable bug fixes in MySQL-wsrep:

    • getifaddr() rather than ifconfig is used to detect the IP of the node, resulting in better compatibility with newer Linux distributions (codeship/mysql-wsrep#45).
    • Table administration commands such as CHECK TABLE are now replicated (lp:1046726)
    • Improvements in the replication of events (lp:1312618)
    • SST could fail with thousands of tables (lp:1294431)
    • Character unique keys could cause false certification failures (lp:1314854)
    • Node aborts if it first joins a non-primary component (lp:1334606)
    • Rsync SST could fail if the rsync port is already taken (lp:1099783)

    New features and notable changes in MySQL 5.5.38 - 5.5.42:

    • Support for SSL 2.0 and 3.0 has been disabled as they provide weak encryption.
    • Security issue with ALTER TABLE ... ADD FOREIGN KEY has been fixed (Bug #19471516. Bug #73650)
    • yaSSL was upgraded to version 2.3.7.
    • TRUNCATE TABLE is logged only when it executes successfully, in order to prevent inconsistencies. (Bug #17942050, Bug #71070)
    • Various fixes in InnoDB and native MySQL replication.