Remove the dependency on openssl/engine.h - fixes codership/galera#663.
Writeset serialization during IST fails because the seqno locking mechanism does not prevent underlying data stores from discarding released actions, requiring the locked seqno to be passed to stores to enforce discard limits.
Fixed ssl_cipher parameter type to string.
When a node progresses from JOINED to SYNCED, a race condition may prevent it from being counted in the commit cut; ensure it is included upon announcing SYNCED and delay advancing the commit cut until the node's last applied value exceeds the current commit cut.
GCS protocol version bumped.
Expose versions of all protocols agreed on by quorum via status call.

Note that since the GCS protocol version has been bumped, a rolling downgrade is not possible after the whole cluster has upgraded to the new version.

Galera plug-in 26.4.20 Release Notes, Release Date: 2 August 2024

Notable changes and fixes in Galera since latest release 4.19:

Improve error and warning messages handling in the library. System error numbers and messages are hidden from thrown exceptions, except for the cases where the exception is thrown because of error from system call. Some warning level messages in gcomm and GCS have been changed to info level in cases where the message does not require action from the administrator.

Galera plug-in 26.4.19 Release Notes, Release Date: 1 July 2024

Notable changes and fixes in Galera since latest release 4.18:

WSREP_KEY_SHARED key type is being phased out since it had insufficiently strict certification rules that may lead to certification test passes where it should fail. WSREP_KEY_REFERENCE fixes this, and all new writesets will be constructed using this. WSREP_KEY_SHARED is supported for backwards compatibility.
A memory leak in the commit cut action has been fixed.
Network level node isolation, which can help shut down all communication with the rest of the cluster to achieve a fail-silent crash.
GCS level protocol bumped, as error voting for joiner in the JOINED state was broken when group-wide commit cut (implied SUCCESS vote) was not taken into account when processing error vote requests from the JOINED node.

Galera plug-in 26.4.18 Release Notes, Release Date: 26 March 2024

Notable changes and fixes in Galera since latest release 4.17:

The garbd process hangs due to exceptions in the GCS layer not being caught within the receive loop, necessitating a forceful termination. Fixing this requires catching all exceptions within the loop, closing the connection first, and then continuing until a 'SELF-LEAVE' message ensures graceful exit.
When using SSL, crashes of garbd during graceful node shutdowns may occur, and result in the cluster becoming non-Primary; garbd now ignores the SIGPIPE signal to prevent this.
socket_ssl_compression is deprecated, now it isn't attempt to be set, and the user receives a warning if it was explicitly set.
Fixed commit cut tracking on node leave, and bumped GCS protocol version for backwards compatibility.
Executing the gcomm join process in the database server thread can lead to issues during allowlist callbacks, which should only be handled by Galera service threads. The gcomm join process is run within the gcomm service thread now.

Galera plug-in 26.4.17 Release Notes, Release Date: 8 January 2024

Notable changes and fixes in Galera since latest release 4.16:

"Zero-level" certification keys are implemented. Currently there are 3 levels of resource keys: schema, table, row, yet one common resource used by every writeset, a node. The key is added by default to every writeset with the default type WSREP_KEY_SHARED. Now, node-wide operations can be performed with the same semantics as regular transactions.
Non-SYNCED nodes are not counted when calculating commit cut - maximum seqno that is no longer needed in certification index; situations may arise when group commit cut is applied before all preceding events are committed on a non-SYNCED node, now drain all monitors to ensure that preceding events are committed.
Stability of node joining process for gmcast improved when new nodes are connecting concurrently as nodes previously may arrive at a different conclusion on which nodes will be blocked, however now, connections are explicitly allowed from all nodes which may be accepted as members in the next view.
Stability of node joining process for EVS improved by dropping EVS join messages without own identified in joining state, to avoid starting membership protocol before at least one of the existing nodes has seen at least one join message from a joiner.
Improve "Failed to report last committed" warning to make it more accurate and user-friendly.
Note that there is a new package signing key, 8DA84635

Galera plug-in 26.4.16 Release Notes, Release Date: 18 August 2023

Notable changes and fixes in Galera since latest release 4.15:

Removed out-of-order certification for BF aborted transactions.
Better error handling when the socket is closed, also cleaned up excessive debug logging.

Galera plug-in 26.4.15 Release Notes, Release Date: 16 June 2023

Notable changes and fixes in Galera since latest release 4.14:

An assertion is relaxed when Galera is configured with commit order disabled.
In certificate index preload, an assertion in handle_ist_trx_preload() fails if the first handled IST preload write set has failed certification, and incrementing the index position caused the certificate index to end up with the wrong position; now fixed by appending dummy writeset sequence numbers into Certification::trx_map_.
ASAN reported memory leak if gcs is closed after becoming joined but before reaching synced.

Galera plug-in 26.4.14 Release Notes, Release Date: 8 March 2023

Notable changes and fixes in Galera since latest release 4.13:

Memory leak in the gcs gcomm backend fixed (tp_ object deleted in GCommConn destructor).
protonet.backend option deprecated since it only supports one option, asio, and the option will be removed in future release. Related, protonet.version is also deprecated.
Deprecation message for socket.ssl_compression as SSL compression cannot be enabled and the option will be removed in future releases.
library could parse incorrect parameters as long as it had a "good" prefix, i.e. evs.*, so fix prevents setting of invalid option values
Parsing of ISO8601 durations previously accepted invalid values, now fixed.
in addition to ISO8601 format, parsing durations now supports real number representation.

Galera plug-in 26.4.13 Release Notes, Release Date: 24 November 2022

Notable changes and fixes in Galera since latest release 4.12:

Complete IO for client handshake before starting an asynchronous read to fix an occasional connection failure when establishing new cluster connections.
EOF-while-reading errors now suppressed when using OpenSSL 3.0.

Galera plug-in 26.4.12 Release Notes, Release Date: 16 May 2022

Notable changes and fixes in Galera since latest release 4.11:

WORK_DIR parameter added for garb.cnf and launch scripts to ensure Galera Arbitrator handles recovery files better (this includes command line option to specify working directory), fixing codership/galera#313
Fixes to renaming fc_master_slave to fc_single_primary
Catch local_endpoint() and remote_endpoint() exceptions, so they are not propagated to the stack, fixing a cluster crash and MDEV-25068
SSL options are explicitly initialised in garbd, fixing MDEV-28158
Compiles with old Boost versions, e.g. < 1.53.0

Galera plug-in 26.4.11 Release Notes

Notable changes and fixes in Galera since latest release 4.10:

Incremental State Transfer (IST) progress reporting via the event service interface has been implemented, and the GCache can report ring buffer recovery progress via the event service interface.
Library side allowlist functionality corresponding to MDEV-27246 was added.
Ring buffer has been enhanced to avoid segfaults if an invalid buffer leaks past the initial recovery scan. dump_map() method implemented for ring buffer to get more detailed debugging.
Join messages are always sent when not in JOINER state; this relaxed condition is required for the correct handling of the desync counter especially in the DONOR state. This fixes MDEV-27459.
To avoid printing garbage when logging certification conflicts, we stopped printing TrxHandleSlave state history, which is also mostly uninteresting since the state graph is linear. Fixes codership/galera#605 and codership/galera#606
For applications that do not track the provider side transaction lifetime accurately, we have a defensive mechanism to not attempt releasing the transaction for writeset handle with null opaque.
Library has had changes to allow it to be compiled as a CMake subproject.
Intermediate libraries are added as STATIC to allow cmake -DBUILD_SHARED_LIBS:BOOL=ON to work correctly, fixing codership/galera#611.

Galera plug-in 26.4.10 Release Notes

Notable changes and fixes in Galera since latest release 4.9:

Error handling during IST failures was improved.
Provider option gcs.fc_master_slave was deprecated in favor of gcs.fc_single_primary.
OpenSSL library version has been updated to version 1.1.1l in binary tarball release.
Packages for Debian 11/Bullseye are now provided.

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:

Atomic library linkage fixes for Debian platforms (codership/galera#558).
CMake post build check fixes to use correct objdump binary (codership/galera#558).
Byteswap compilation failures on FreeBSD were fixed (codership/galera#581).
Hardware CRC32C support for FreeBSD/ARM.

Galera plug-in 26.4.7 Release Notes

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

CRC32 hardware support compatibility was improved on ARM based architectures (codership/galera#579, codership/galera#582).
A race condition in GCache locking was fixed.
Garbd compatibility issue with MariaDB 10.5 was fixed (MDEV-23647).

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.37 Release Notes, Release Date: 16 May 2022

Notable changes and fixes in Galera since latest release 3.36:

WORK_DIR parameter added for garb.cnf and launch scripts to ensure Galera Arbitrator handles recovery files better (this includes command line option to specify working directory), fixing codership/galera#313

Galera plug-in 25.3.36 Release Notes

Notable changes and fixes in Galera since latest release 3.35:

Ring buffer has been enhanced to avoid segfaults if an invalid buffer leaks past the initial recovery scan. dump_map() method implemented for ring buffer to get more detailed debugging.
Join messages are always sent when not in JOINER state; this relaxed condition is required for the correct handling of the desync counter especially in the DONOR state. This fixes MDEV-27459.
Intermediate libraries are added as STATIC to allow cmake -DBUILD_SHARED_LIBS:BOOL=ON to work correctly, fixing codership/galera#611.

Galera plug-in 25.3.35 Release Notes

Notable changes and fixes in Galera since latest release 3.34.

OpenSSL library version has been updated to version 1.1.1l in binary tarball release.

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:

Atomic library linkage fixes for Debian platforms (codership/galera#558).
CMake post build check fixes to use correct objdump binary (codership/galera#558).
Byteswap compilation failures on FreeBSD were fixed (codership/galera#581).
Hardware CRC32C support for FreeBSD/ARM.

Galera plug-in 25.3.32 Release Notes

Notable fixes in Galera since latest release 3.31.

CRC32 hardware support compatibility was improved on ARM based architectures (codership/galera#579, codership/galera#582).
A race condition in GCache locking was fixed.

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):

Enhanced duplicate UUID detection (original bug codership/galera#533).
Fixed build issues on hppa, hurd-i386, kfreebsd (codership/galera#539).

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):

Fixes for compiling on Alpha / HP PA / s390x architectures (codership/galera#389)
A Contribution agreement was added in order to facilitate future contributions (codership/galera#386)

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):

Support for Debian Jessie (codership/galera#264)
Galera will abort gracefully if there is no disk space to write the required gcache files (codership/galera#324)
Gcache files are removed faster than before in order to reduce Galera disk usage (codership/galera#317)
Better error logging in case of SSL errors or misconfiguration (codership/galera#290)
The configuration in /etc/sysconfig/garb is now properly honored by the garbd systemd service (codership/galera#267)
Arbitrator service no longer starts automatically on package installation, giving the user the opportunity to configure it first (codership/galera#266)
Miscellaneous fixes in the garb startup script (codership/galera#186)

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.4 Series

MySQL wsrep 8.4.3-26.21 Release Notes, Release Date: 3 December 2024

Notable changes and fixes in MySQL-wsrep since the latest release 8.4.2-26.20:

wsrep_ready is now atomic.
Foreign key checks are skipped in applying during IST, controlled by new wsrep_mode APPLIER_SKIP_FK_CHECKS_IN_IST (not on by default).
Node crashes if TOI fails during IST while executing CREATE TABLE due to an unpopped Strict_error_handler, fixed by ensuring thd->pop_internal_handler() is called before returning.
ALTER TABLE RENAME caused BF ABORT on two nodes due to transactional MDL-locks not being released after an implicit commit failure from a certification error, fixed by ensuring locks are released even when the commit fails.
The SKIP LOCKED option in SELECT FOR UPDATE caused an assertion failure when attempting to lock a supremum record already held by a high-priority transaction, fixed by handling unexpected DB_SKIP_LOCKED return codes as DB_DEADLOCK to abort the operation.
Fix wsrep_cluster_conf_id to show correct value (which is not -1 the default, 18446744073709551615).
Fix an assert in SELECT FOR UPDATE SKIP LOCKED.
wsrep_diag.sql script was updated to filter out MDL locks on performance_schema tables caused by querying the metadata_locks table itself.
Fix issue of continuing to check multiple foreign key constraints despite an error is resolved by ensuring that wsrep_row_upd_check_foreign_constraints() stops further checks and errors out immediately if the error state is not DB_SUCCESS.
Watchdog moved into a separate thread to avoid blocking the InnoDB monitor.
Fix DROP TABlE IF EXISTS could still be missing certification keys from referenced tables.
Refactor Galera MDL-conflict handling by introducing wsrep_bf_info to securely store conflict logging data and holding appropriate locks during MDL-conflict logging to ensure thread safety and prevent data changes.
Ensure fail-silent semantics during crashes by shutting down Galera networking and suppressing Galera/wsrep logging upon fatal signals, preventing interference with stack traces and core dumping.
RESET MASTER is no longer supported in 8.4, and is replaced with RESET BINARY LOGS AND GTIDS.
Port component_keyring_vault from PXC.

MySQL wsrep 8.4.2-26.20 Release Notes, Release Date: 2 August 2024

wsrep_provider_options is now implemented as a plugin, meaning system variables are generated dynamically from options read from the provider. Options can be dynamic or readonly.
the default SST method is now switched to using the CLONE plugin (other methods, like rsync, are still available).
the wsrep allowlist allows you to add IPs for Galera Cluster node addresses that can make SST/IST requests.

MySQL wsrep Server 8.0 Series

MySQL wsrep 8.0.40-26.21 Release Notes, Release Date: 3 December 2024

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.39-26.20:

wsrep_ready is now atomic.
Foreign key checks are skipped in applying during IST, controlled by new wsrep_mode APPLIER_SKIP_FK_CHECKS_IN_IST (not on by default).
Node crashes if TOI fails during IST while executing CREATE TABLE due to an unpopped Strict_error_handler, fixed by ensuring thd->pop_internal_handler() is called before returning.
ALTER TABLE RENAME caused BF ABORT on two nodes due to transactional MDL-locks not being released after an implicit commit failure from a certification error, fixed by ensuring locks are released even when the commit fails.
The SKIP LOCKED option in SELECT FOR UPDATE caused an assertion failure when attempting to lock a supremum record already held by a high-priority transaction, fixed by handling unexpected DB_SKIP_LOCKED return codes as DB_DEADLOCK to abort the operation.
Fix wsrep_cluster_conf_id to show correct value (which is not -1 the default, 18446744073709551615).
Fix an assert in SELECT FOR UPDATE SKIP LOCKED.
wsrep_diag.sql script was updated to filter out MDL locks on performance_schema tables caused by querying the metadata_locks table itself.
Fix issue of continuing to check multiple foreign key constraints despite an error is resolved by ensuring that wsrep_row_upd_check_foreign_constraints() stops further checks and errors out immediately if the error state is not DB_SUCCESS.
Watchdog moved into a separate thread to avoid blocking the InnoDB monitor.
Fix DROP TABlE IF EXISTS could still be missing certification keys from referenced tables.
Refactor Galera MDL-conflict handling by introducing wsrep_bf_info to securely store conflict logging data and holding appropriate locks during MDL-conflict logging to ensure thread safety and prevent data changes.
Ensure fail-silent semantics during crashes by shutting down Galera networking and suppressing Galera/wsrep logging upon fatal signals, preventing interference with stack traces and core dumping.

MySQL wsrep 8.0.39-26.20 Release Notes, Release Date: 2 August 2024

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.37-26.19:

DROP TABLE could cause MDL BF-BF conflicts during concurrent operations.
Make the CLONE SST script more robust when dealing with SSL.
Deprecate wsrep_convert_lock_to_trx.
Wsrep now always waits for unobtrusive MDL locks.
new testing for SST for a database with 10'000 tables (and the reason we skipped releasing 8.0.38 as an upstream bug was present causing mysqld to crash)

MySQL wsrep 8.0.37-26.19 Release Notes, Release Date: 1 July 2024

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.36-26.18:

running GRANT with wsrep_forced_binlog_format=ROW produced an unrecoverable binary log (binlog). Now wsrep_forced_binlog_format is only effective for DML operations, and is also marked as deprecated because binlog_format has been deprecated as of MySQL 8.0.34 (the only possible logging format is ROW, making this option redundant).
Support for table names with special characters.
Binlog coordinated wsrep recovery now improved.
Ported MDEV-29293 (MariaDB stuck on starting commit state (waiting on commit order critical section) Export), reorganising BF abort codepaths so that mutex locking cycles does not happen when accessing the victim THD from BF THD. This fixes the occasional stuck on starting commit state.
WSREP_SST_OPT_PORT unset variable check fixed.
the GRA log file was malformed due to missing Format_description_log_event; it is now easier to read with mysqlbinlog.
race condition in wsrep InnoDB watchdog fixed.
fix unexpected server abort after MDL conflict between RSU and local command
improve MDL conflict reporting by printing all lock types.
fix applying failures due to MDL deadlocks by making sure that appliers get higher priority compared to locally executing DDLs in MDL deadlock resolving.
Improve "BF applier failed to open_and_lock_tables" warning.

MySQL wsrep 8.0.36-26.18 Release Notes, Release Date: 30 April 2024

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.35-26.17:

Fix broken clone SST when port configuration variable is not explicitly set.

MySQL wsrep 8.0.36-26.17 Release Notes, Release Date: 26 March 2024

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.35-26.16:

Recovering the GTID in case log file contains non-text bytes have been fixed, ensuring --wsrep-recover option functions correctly.
CLONE SST has a few fixes: port settings from my.cnf read if not specified in wsrep_sst_address, it doesn't use client authentication credentials from my.cnf, it uses caching_sha2_password now for user creation for SST, no longer mysql_native_password, and there are better diagnostic messages when used with SSL.
More diagnostic functionality including adding transaction sequence numbers and source IDs for ignored errors, and logging of event of row-based replication buffer file creation. Skipping doublewrite recovery is only printed when wsrep_debug is set.
Standardized TOI error voting in Galera Cluster by using only MySQL error codes, addressing inconsistencies caused by locale differences and non-deterministic execution paths. This ensures uniform voting outcomes for TOI event failures. However, this can break backwards compatibility and opens up a possibility of a cluster split, so the server side wsrep protocol version is bumped to 7 in order to keep the old behaviour until the cluster is fully upgraded.
Resolved an issue where a combination of native deadlocks and BF aborts in stored procedures led to assertion failures. The solution skips wsrep BF abort error handling for sub-statements, ensuring error handling only post sub-statement execution.
Fixed an issue where autocommit SELECT FOR UPDATE queries, if BF aborted, could lead to inconsistencies and assertions within InnoDB.
Error handling for SELECT FOR UPDATE inside transaction.
wsrep_notify_status view should be passed down.

MySQL wsrep 8.0.35-26.16 Release Notes, Release Date: 8 January 2024

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.34-26.15:

During the joiner CLONE SST process, a temporary user is created and dropped, and this is added to the binary log by default and sets off the MySQL GTID; joiner process operations are now disabled from binlogging.
When using wsrep_notify_cmd, the script is now only called when Galera has already formed a view or when it is synced or the donor, preventing any untoward hangs.
SST user account management has changed. Now there is automatic creation of temporary accounts for SST, and the credentials are passed to the SST script via socket (not environment variables), and the user is deleted after the SST script returns as complete. If additional privilege grants are needed for a particular SST method, wsrep_sst_auth is still respected. This works for mysqldump, CLONE, xtrabackup.
INFORMATION_SCHEMA.PROCESSLIST is deprecated, and now PERFORMANCE_SCHEMA.PROCESSLIST is used instead, and one can find information on appliers and rollback threads via SELECT * FROM performance_schema.processlist WHERE NAME = 'thread/sql/wsrep_applier_thread'; or 'thread/sql/wsrep_rollback_thread'.
Foreign key constraint check retrying is implemented, as foreign key constraint checks may occasionally fail even though the constraints are not violated. The number of retries by default is 1, and can be controlled by the new system variable: wsrep_applier_FK_failure_retries.
Note that there is a new package signing key, 8DA84635.

MySQL wsrep 8.0.34-26.15 Release Notes, Release Date: 18 August 2023

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.33-26.14:

When the server as started with read-only=ON, the mode toggled off during concurrent load due to a race condition.
Condition to replay a transaction via autocommit retry is now based entirely on wsrep_conflict_state, not accessing the lex tree as it is not guaranteed to be in a well-formed state (not user visible, but notable as to how wsrep_retry_autocommit now works).
INFO-level wsrep messages are now logged with SYSTEM_LEVEL priority by default, as WSREP information level messages are crucial for debugging replication issues. New variable, wsrep_info_level introduced to allow changing the priority to INFORMATION_LEVEL if needed.
During CREATE TABLE AS SELECT, Galera will not support wsrep_forced_binlog_format=MIXED|STATEMENT, and it will result in ROW with a warning.
Fix an inconsistency caused by ROLLBACK TO SAVEPOINT.
Systemd multi-instance support fixed.

MySQL wsrep 8.0.33-26.14 Release Notes, Release Date: 16 June 2023

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.32-26.13:

When inside a stored function or trigger, the current statement transaction should not allow commit or rollback.
wsrep_start_position contains the wsrep GTID position, local seqno for asynchronous replication, server ID and server UUID all in one argument, slash-separated.
Nodes now use the same server UUID (generated on the seed node) to binlog events that don't go through wsrep; this makes histories comparable provided the user executes such operations in agreed order on all the nodes. Previously wsrep nodes kept generating their own individual server UUIDs. A new wsrep_sync_server_uuid configuration variable, if set to true, the node then respects server UUID received from the donor node; otherwise the node generates its own server UUID. This concerns binlog events not replicated via wsrep which continues to be logged with cluster UUID. Default is such that all nodes generate their own server UUIDs.
When needed, the datadir initialization is now fixed in the clone SST script.
Asynchronous parallel replication enforces the same commit order in replica as was in the replication source, by default, and is configurable by replica_preserve_commit_order; while parallel apply is configured by replica_parallel_workers=4 (the default). The replication worker now waits for asynchronous replication commit order of the replication source before calling for wsrep replication.
Fix server abort when the binary log is rotated upon reaching maximum size. This was caused by an optimization that skips blocking operations of compressing GTID set during storing them into the GTIDs table during the binlog rotation. Thus, we skip wsrep commit hooks execution for implicit internal transaction of storing GTIDs.
In some Linux distributions, xtrabackup installs plugins under lib64 as opposed to lib; now we search in both locations.

MySQL wsrep 8.0.32-26.13 Release Notes, Release Date: 6 April 2023

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.31-26.12:

All output from wsrep_diag.sql goes to the same output stream.
Better handling of SST scripts with ASan builds.
Memory leak around apply failure, ALTER TABLESPACE, fixed.
The wsrep patch works with lock order debug instrumentation.
Removed check for innodb_lock_schedule_algorithm as it does not exist in MySQL 8.

MySQL wsrep 8.0.31-26.12 Release Notes, Release Date: 8 March 2023

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.30-26.11:

mysqladmin now displays all status variables for wsrep, overriding the default upper limit to be read from the server.
A wsrep_diag.sql script contains useful diagnostics queries for troubleshooting wsrep related issues.
Better handling of Total Order Isolation, from mistakenly skipped replication to error reporting.
mysqld_bootstrap script handles interruptions.
Now have version_comment variable to display server version releases.
the wsrep position can be recovered even if wsrep is off.
New wsrep_mode APPLIER_IGNORE_MISSING_TABLE which enables the server to skip failures with table open at applying time, but only if the log event contains other tables that are open. This is the default setting now, improving multi-table updates involving triggers.

MySQL wsrep 8.0.30-26.11 Release Notes, Release Date: 24 November 2022

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.28-26.10:

OpenSSL 3.0 compatibility exists.
Audit log character set information asset fix, since the default character set changed from utf8 to utf8mb3.
New keyring_vault plugin for encryption.
CLONE SST cleanup when joiner is killed does not reserve the listen port any longer.
DDL XIDs now use the wsrep seqno.
innodb_wsrep_applier_lock_wait_timeout made read-write.
Deprecated wsrep_slave_UK_checks variable with the default set to ON.
Roles are replicated (CREATE ROLE/DROP ROLE).
Variable innodb_wsrep_applier_lock_wait_timeout is now dynamic.
In rare instances, fixed an inconsistency with an import operation where TRUNCATE is issued on a table having a Foreign Key constraint, while there is concurrent DML for the FK parent table.
Fix wsrep_recover crash when gtid_mode=ON.
Galera now truncates trailing strings and pads characters according to the collation rules for a given key column.

We have one word of warning to all users upgrading from a previous version that happen to use INSTANT ALTER. Users can check whether INSTANT ALTER is used by running:

SELECT NAME FROM INFORMATION_SCHEMA.INNODB_TABLES WHERE TOTAL_ROW_VERSIONS > 0;

If tables with row versions are found, it is recommended to run OPTIMIZE TABLE for those tables before upgrading to 8.0.30.

Please refer to our release blog for more information.

MySQL wsrep 8.0.28-26.10 Release Notes, Release Date: 16 May 2022

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.27-26.9:

Progress reporting is implemented from the xtrabackup SST script. If pv is present, the SST stream is piped through pv.
Progress reporting for CLONE SST can be disabled if progress=none is set in [sst].
wsrep_sst_rsync has been refactored.
wsrep_sst_xtrabackupv2 now includes the PORT variable by default (4444).
Fixes a crash on shutdown after starting an XA transaction (MDEV-26575) and also disallows XA when Galera library is loaded (XA is not supported in the community release edition).
innodb_disallow_writes has been refactored to ensure that disk writes do not leak the MySQL data directory when node is in SST donor state.
Fixes a race condition in wsrep_sst_rsync by performing all disk I/O blocking before creating the tables_flushed file.

MySQL wsrep 8.0.27-26.9 Release Notes, Release Date: 14 February 2022

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.26-26.8:

Progress reporting is now supported from SST scripts.
- total N: signals new SST stage and reports estimated total work
- complete N: reports completed work in the current stage
Progress reporting is enabled for CLONE SST as well, as there is a dedicated monitoring process that periodically queries the performance_schema.events_stages_current table.
There is a new wsrep_recover utility script to simplify cluster recovery procedures that will determine the last committed GTID of a crashed or stopped node.
The xtrabackup-v2 SST script was fixed to handle XtraBackup --strict option, which is enabled by default as of 8.0.27. Specifically the --binlog-option was removed from the script.
REPAIR or OPTIMIZE<*code> commands do not acquire MDL locks on parent tables, so wsrep_append_fk_parent_table() is unnecessary for OPTIMIZE and REPAIR, fixing a crash on REPAIR VIEW that was created from an INFORMATION_SCHEMA table.
New variable innodb-wsrep-applier-lock-wait-timeout to configure the timeout in seconds after which the wsrep watchdog starts killing local transactions that are blocking the applier (0 disables the watchdog).
A wsrep transaction is started before appending the table level key to ensure that valid transaction ID is always available for Galera library.
WSREP related errors sent to COM_STMT_PREPARE commands.
Parallel apply improvements: CREATE TABLE .. LIKE is marked as unsafe and a transaction is marked as unsafe when it traverses into a cascade delete operation. This fixes MDEV-26803.
CREATE TABLE with FOREIGN KEY constraint failed to apply in parallel, now will get referenced tables appended as keys in the writeset. This fixes MDEV-27276.

MySQL wsrep 8.0.26-26.8 Release Notes, Release Date: 15 November 2021

Notable changes and fixes in MySQL-wsrep since the latest release 8.0.25-26.7:

New wsrep_mode IGNORE_CASCADING_FK_DELETE_MISSING_ROW_ERROR was added to work around applying errors with cascading delete. This is a workaround for MySQL Bug 80821.
A rare deadlock between cluster configuration change and FLUSH TABLES WITH READ LOCK was fixed.
Executing FLUSH TABLES is now allowed also when not in primary component.
A bug which caused streaming replication transaction to roll back locally but not in the cluster was fixed (MDEV-26707).
New SST configuration options donor-timeout and joiner-timeout were added.
MDL BF-BF conflict between ALTER and UPDATE was fixed. A certification key corresponding to MDL lock taken for table referenced by foreign key constraint is added to write set to make parallel applying dependencies correct.
Write set applying reliability was improved by introducing periodic check for long lock waits for applied write sets.
Terminology change: The use of 'master' and 'slave' was deprecated. The following system variables were renamed:
- wsrep_slave_threads -> wsrep_applier_threads
- wsrep_slave_FK_checks -> wsrep_applier_FK_checks
- wsrep_slave_UK_checks -> wsrep_applier_UK_checks
- wsrep_restart_slave -> wsrep_restart_replica
Packages for Debian 11/Bullseye are now provided.
OpenSSL library version has been updated to version 1.1.1l in binary tarball release.

XtraBackup compatibility:

Percona XtraBackup version 8.0.26-18.0 or higher is required to perform XtraBackup based SSTs.

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:

Atomic library linkage fixes for Debian platforms (codership/galera#558).
CMake post build check fixes to use correct objdump binary (codership/galera#558).
Byteswap compilation failures on FreeBSD were fixed (codership/galera#581).
Hardware CRC32C support for FreeBSD/ARM.

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.44-25.36 Release Notes, Release Date: 8 January 2024

Notable changes and fixes in MySQL-wsrep since the latest release 5.7.43-25.35:

Merge upstream 5.7.44 and manpages into the release.
Note that there is a new package signing key, 8DA84635.

MySQL wsrep 5.7.43-25.35 Release Notes, Release Date: 18 August 2023

Notable changes and fixes in MySQL-wsrep since the latest release 5.7.42-25.34:

When the server as started with read-only=ON, the mode toggled off during concurrent load due to a race condition.
Condition to replay a transaction via autocommit retry is now based entirely on wsrep_conflict_state, not accessing the lex tree as it is not guaranteed to be in a well-formed state (not user visible, but notable as to how wsrep_retry_autocommit now works).

MySQL wsrep 5.7.42-25.34 Release Notes, Release Date: 16 June 2023

Notable changes and fixes in MySQL-wsrep since the latest release 5.7.41-25.33:

When inside a stored function or trigger, the current statement transaction should not allow commit or rollback.

MySQL wsrep 5.7.41-25.33 Release Notes, Release Date: 6 April 2023

Notable changes and fixes in MySQL-wsrep since the latest release 5.7.40-25.32:

All output from wsrep_diag.sql goes to the same output stream.

MySQL wsrep 5.7.40-25.32 Release Notes, Release Date: 8 March 2023

Notable changes and fixes in MySQL-wsrep since the latest release 5.7.39-25.31:

wsrep_sync_wait is skipped during trigger execution.
A wsrep_diag.sql script contains useful diagnostics queries for troubleshooting wsrep related issues.
mysqld_bootstrap script handles interruptions.
wsrep_recover is an enhanced new addition, backported from 8.0 to aid in recovery of crashed clusters.
The wsrep position can be recovered even if wsrep is off.
New wsrep_mode APPLIER_IGNORE_MISSING_TABLE which enables the server to skip failures with table open at applying time, but only if the log event contains other tables that are open. This is the default setting now, improving multi-table updates involving triggers.
Better handling of Total Order Isolation, from mistakenly skipped replication to error reporting.

MySQL wsrep 5.7.39-25.31 Release Notes, Release Date: 27 October 2022

Notable changes and fixes in MySQL-wsrep since the latest release 5.7.38-25.30:

The InnoDB wsrep applier lock wait timeout from 8.0 has been backported. In introduces the innodb_wsrep_applier_lock_wait_timeout variable to improve the reliability in resolving cluster conflicts.
The variable wsrep_slave_UK_checks has been deprecated and the default behaviour has changed to being ON.

MySQL wsrep 5.7.38-25.30 Release Notes, Release Date: 19 August 2022

Notable changes and fixes in MySQL-wsrep since the latest release 5.7.37-25.29:

Distinguish between unset ssl_mode and ssl_mode explicitly set to "DISABLED"

MySQL wsrep 5.7.37-25.29 Release Notes, Release Date: 16 May 2022

Notable changes and fixes in MySQL-wsrep since the latest release 5.7.36-25.28:

innodb_disallow_writes has been refactored to ensure that disk writes do not leak the MySQL data directory when node is in SST donor state.
Fixes a race condition in wsrep_sst_rsync by performing all disk I/O blocking before creating the tables_flushed file.

MySQL wsrep 5.7.36-25.28 Release Notes, Release Date:

Notable changes and fixes in MySQL-wsrep since the latest release 5.7.35-25.27:

Parallel apply improvements: CREATE TABLE .. LIKE is marked as unsafe and a transaction is marked as unsafe when it traverses into a cascade delete operation. This fixes MDEV-26803.
CREATE TABLE with FOREIGN KEY constraint failed to apply in parallel, now will get referenced tables appended as keys in the writeset. This fixes MDEV-27276.

MySQL wsrep 5.7.35-25.27 Release Notes

Notable fixes in MySQL-wsrep since the latest release 5.7.34-25.26:

A node hang caused by cluster write conflicts with innodb_thread_concurrency configured were fixed (codership/mysql-wsrep#364).
A node hang caused by deadlock between TRUNCATE TABLE and a query in cleanup phase was fixed.
New wsrep_mode IGNORE_CASCADING_FK_DELETE_MISSING_ROW_ERROR was added to work around applying errors with cascading delete. This is a workaround for MySQL Bug 80821.
New SST configuration options donor-timeout and joiner-timeout were added.
Executing FLUSH TABLES is now allowed also when not in primary component.
OpenSSL library version has been updated to version 1.1.1l in binary tarball release.

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:

Fixed segmentation fault when setting wsrep_provider='none' (codership/mysql-wsrep#308).

MySQL wsrep 5.7.26-25.18 Release Notes

Notable bugs fixed in this release:

Work around 'pure virtual function called' crash on Centos 6 (codership/mysql-wsrep#298)
Fixed an applying bug of SET PASSWORD which caused password to be exposed as plain text on slave nodes (codership/mysql-wsrep#356)
Fixed a shutdown bug which caused mysqld process to exit before applier threads were shut down gracefully (codership/mysql-wsrep#353)
Fixed use-after-delete bug which caused segmentation fault (codership/mysql-wsrep#352)

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:

Rsync SST was not copying tablespace from the donor node (codership/mysql-wsrep#334).
Fixes for transaction replaying from stored procedures (codership/mysql-wsrep#336).
Fixed a regression where transaction replaying caused a crash when AUTOCOMMIT=OFF (codership/mysql-wsrep#344).
Fixes for transaction replaying from event scheduler (codership/mysql-wsrep#347).
Fixed crash in write set applying with binlog_rows_query_log_events option enabled (codership/mysql-wsrep#343).
Maximum variable value length was increased in order to avoid truncation of long wsrep_provider_options variable string (codership/mysql-wsrep#348).

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:

Rsync SST was not copying tablespace from the donor node (codeship/mysql-wsrep#334).
Fixes for transaction replaying from stored procedures (codeship/mysql-wsrep#336).
Fixes for transaction replaying from event scheduler (codeship/mysql-wsrep#347).
Fixed crash in write set applying with binlog_rows_query_log_events option enabled (codeship/mysql-wsrep#343).
Maximum variable value length was increased in order to avoid truncation of long wsrep_provider_options variable string (codeship/mysql-wsrep#348).

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:

The ALTER USER statement is now replicated correctly (MW-305, codeship/mysql-wsrep#292, lp:1376269)
The wsrep_max_ws_rows could cause SELECT queries that use temporary tables to return an error (MW-309, lp:1638138)

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:

Galera would crash on startup if compiled with GCC 6 (MW-267, codeship/mysql-wsrep#267)

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:

FLUSH TABLES could cause the cluster to hang (codeship/mysql-wsrep#237)
The following transaction could be needlessly aborted if the previous one was aborted (codeship/mysql-wsrep#248)
A node could hang under workload containing both DDL and DML statements (codeship/mysql-wsrep#233)

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:

IB atomic builtins are no longer used when compiling as they may cause the server to hang (codeship/mysql-wsrep#221)
query cache is now compatible with wsrep_sync_wait (codeship/mysql-wsrep#201)
a deadlock could occur between the applier thread and an aborted transaction (codeship/mysql-wsrep#184)
a memory leak could occur when using SHOW STATUS (codership/galera#308)
DDL was not recorded in InnoDB header, causing InnoDB to recover to an earlier position (codeship/mysql-wsrep#31)
an assertion could happen with Prepared Statements (codeship/mysql-wsrep#125, codeship/mysql-wsrep#126)

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):

Various forms of FLUSH that are replicated in traditional MySQL async replication are now also replicated in Galera under TOI (codeship/mysql-wsrep#67)
The applier thread will now honor FLUSH TABLES WITH READ LOCK, FLUSH FOR EXPORT and will block until the lock is released (codeship/mysql-wsrep#113)
support for Debian Jessie (codeship/mysql-wsrep#127)
The SST password is no longer passed via the command line or visble in the error log or ps output (codeship/mysql-wsrep#141)
The xtrabackup SST script has been updated from the upstream source (codeship/mysql-wsrep#143)

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:

Important: fixes for transactions exceeding the maximum writeset size(lp:1309669, lp:1270920)
Updating a unique key could cause parallel applying to hang (lp:1280896)
Replication could fail with inserts to table with single unique key (lp:1299116)
Node aborts if it first joins a non-primary component (lp:1334606)
Xtrabackup SST fails if /tmp/test directory exists (lp:1294760)
Character unique keys could cause false certification failures (lp:1314854)
DROP DATABASE may hang when run against a server with many tables (lp:1309241)
SST could fail with thousands of tables (lp:1294431)
Rsync SST could fail if the rsync port is already taken (lp:1099783)
Dropping a temporary MyISAM table could cause an assertion (codeship/mysql-wsrep#11, codeship/mysql-wsrep#13)
gvwstate.dat was removed during xtrabackup SST (codeship/mysql-wsrep#8)

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:

IB atomic builtins are no longer used when compiling as they may cause the server to hang (codeship/mysql-wsrep#221)
query cache is now compatible with wsrep_sync_wait (codeship/mysql-wsrep#201)

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):

The SST password is no longer passed via the command line or visble in the error log or ps output (codeship/mysql-wsrep#141)
The xtrabackup SST script has been updated from the upstream source (codeship/mysql-wsrep#143)

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.

tags:

galera cluster

galera

release

Languages

Login

Search form

You are here

Galera Cluster Release Notes

Galera Plugin version 4 Series

Galera Plugin version 3 Series

MySQL wsrep Server 8.4 Series

MySQL wsrep Server 8.0 Series

MySQL wsrep Server 5.7 Series

MySQL wsrep Server 5.6 Series

MySQL wsrep Server 5.5 Series

Galera Plugin version 4 Series

Galera plug-in 26.4.21 Release Notes, Release Date: 3 December 2024

Galera plug-in 26.4.20 Release Notes, Release Date: 2 August 2024

Galera plug-in 26.4.19 Release Notes, Release Date: 1 July 2024

Galera plug-in 26.4.18 Release Notes, Release Date: 26 March 2024

Galera plug-in 26.4.17 Release Notes, Release Date: 8 January 2024

Galera plug-in 26.4.16 Release Notes, Release Date: 18 August 2023

Galera plug-in 26.4.15 Release Notes, Release Date: 16 June 2023

Galera plug-in 26.4.14 Release Notes, Release Date: 8 March 2023

Galera plug-in 26.4.13 Release Notes, Release Date: 24 November 2022

Galera plug-in 26.4.12 Release Notes, Release Date: 16 May 2022

Galera plug-in 26.4.11 Release Notes

Galera plug-in 26.4.10 Release Notes

Galera plug-in 26.4.9 Release Notes

Galera plug-in 26.4.8 Release Notes

Galera plug-in 26.4.7 Release Notes

Galera plug-in 26.4.6 Release Notes

Galera plug-in 26.4.5 Release Notes

Galera Plugin version 3 Series

Galera plug-in 25.3.37 Release Notes, Release Date: 16 May 2022

Galera plug-in 25.3.36 Release Notes

Galera plug-in 25.3.35 Release Notes

Galera plug-in 25.3.34 Release Notes

Galera plug-in 25.3.33 Release Notes

Galera plug-in 25.3.32 Release Notes

Galera plug-in 25.3.31 Release Notes

Galera plug-in 25.3.30 Release Notes

Galera plug-in 25.3.29 Release Notes

Galera plug-in 25.3.28 Release Notes

Galera plug-in 25.3.27 Release Notes

Galera plug-in 25.3.26 Release Notes

Galera plug-in 25.3.25 Release Notes

Galera plug-in 25.3.24 Release Notes

Galera plug-in 25.3.23 Release Notes

Galera plug-in 25.3.22 Release Notes

Galera plug-in 25.3.21 Release Notes

Galera plug-in 25.3.20 Release Notes

Galera plug-in 25.3.19 Release Notes

Galera plug-in 25.3.18 Release Notes

Galera plug-in 25.3.17 Release Notes

Galera plug-in 25.3.16 Release Notes

Galera plug-in 25.3.15 Release Notes

Galera plug-in 25.3.14 Release Notes

Galera plug-in 25.3.13 Release Notes

Galera plug-in 25.3.12 Release Notes

Galera plug-in 25.3.10 Release Notes

MySQL wsrep Server 8.4 Series

MySQL wsrep 8.4.3-26.21 Release Notes, Release Date: 3 December 2024

MySQL wsrep 8.4.2-26.20 Release Notes, Release Date: 2 August 2024

MySQL wsrep Server 8.0 Series

MySQL wsrep 8.0.40-26.21 Release Notes, Release Date: 3 December 2024

MySQL wsrep 8.0.39-26.20 Release Notes, Release Date: 2 August 2024

MySQL wsrep 8.0.37-26.19 Release Notes, Release Date: 1 July 2024

MySQL wsrep 8.0.36-26.18 Release Notes, Release Date: 30 April 2024

MySQL wsrep 8.0.36-26.17 Release Notes, Release Date: 26 March 2024

MySQL wsrep 8.0.35-26.16 Release Notes, Release Date: 8 January 2024

MySQL wsrep 8.0.34-26.15 Release Notes, Release Date: 18 August 2023

MySQL wsrep 8.0.33-26.14 Release Notes, Release Date: 16 June 2023

MySQL wsrep 8.0.32-26.13 Release Notes, Release Date: 6 April 2023

MySQL wsrep 8.0.31-26.12 Release Notes, Release Date: 8 March 2023

MySQL wsrep 8.0.30-26.11 Release Notes, Release Date: 24 November 2022

MySQL wsrep 8.0.28-26.10 Release Notes, Release Date: 16 May 2022

MySQL wsrep 8.0.27-26.9 Release Notes, Release Date: 14 February 2022

MySQL wsrep 8.0.26-26.8 Release Notes, Release Date: 15 November 2021

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

MySQL wsrep 8.0.21-26.4 Release Notes