Percona XtraDB Cluster moved to 5.6.21-25.8

Milestone information

Percona XtraDB Cluster moved to
Hrvoje Matijakovic
Release registered:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata


Assigned to you:
No blueprints or bugs assigned to you.
1 Alexey Kopytov, 1 David Bennett, 1 Hrvoje Matijakovic, 1 Raghavendra D Prabhu
No blueprints are targeted to this milestone.
27 Fix Released

Download files for this release

File Description Downloads

Release notes 


View the full changelog

New Features

Galera 3.8 introduces auto-eviction for nodes in the cluster experiencing network issues like packet loss. It is off by default and is turned on with evs.auto_evict option. This feature requires EVS protocol version (evs.version) 1. During the EVS protocol upgrade all membership changes are communicated over EVS protocol version 0 to preserve backwards compatibility, protocol is upgraded to the highest commonly supported version when forming a new group so if there exist a single node with older version in the group, the group protocol version remains as 0 and auto-eviction is not functional. (#1274192).

Percona XtraDB Cluster now supports backup locks in XtraBackup SST (in the default xtrabackup-v2 wsrep_sst_method). Backup locks are used in lieu of FLUSH TABLES WITH READ LOCK on the donor during SST. This should allow for minimal disruption of existing and incoming queries, even under high load. Thus, this should allow for even faster SST and node being in ‘donor/desynced’ state. This also introduces following constraints: Percona XtraDB Cluster 5.6.21 requires Percona XtraBackup 2.2.5 or higher; An older (< 5.6.21) joiner cannot SST from a newer (>= 5.6.21) donor. This is enforced through SST versioning (sent from joiner to donor during SST) and logged to error log explicitly. (#1390552).

Percona XtraDB Cluster is now shipped with Galera MTR test suite.

Bugs fixed

Percona XtraDB Cluster now shows a warning in case additional utilities, like pv which may not affect critical path of SST, are not installed. Bug fixed #1248688.

Fixed the UNIV_DEBUG build failures. Bug fixed #1384413.

mysqldump SST can now use username/password from wsrep_sst_auth under group of [sst] in my.cnf in order not to display the credentials in the error log. Bug fixed #1293798.

Normal shutdown under load would cause server to remain hanging because replayer failed to finish. Bug fixed #1358701.

wsrep_causal_reads variable was not honored when declared as global. Bug fixed #1361859.

Assertion failure lock != ctx->wait_lock has been fixed. Bug fixed #1364840.

garbd would not work when cluster address was specified without the port. Bug fixed #1365193.

Fixed wsrep options compiler warnings in Fedora 20. Bug fixed #1369916.

If mysqld gets killed during the SST it will leave an unclean data directory behind. This would cause Percona XtraDB Cluster to fail when the server would be started next time because the data directory would be corrupted. This was fixed by resuming the startup in case wsrep-recover failed to recover due to corrupted data directory. The old behavior is still achievable through --exit-on-recover-fail command line parameter to mysqld_safe or exit-on-recover-fail under [mysqld_safe] in my.cnf. Bug fixed #1378578.

Percona XtraDB Cluster now reads environment variables for mysqld from following files (if present): /etc/default/mysql in Debian/Ubuntu; /etc/sysconfig/mysql in CentOS 6 or lower; /etc/sysconfig/mysql in CentOS 7 with mysql.service; /etc/sysconfig/XYZ in CentOS 7 with <email address hidden> (/etc/sysconfig/bootstrap is supplied by default). Bug fixed #1381492.

gvwstate.dat file was removed on joiner when Xtrabackup SST Configuration method was used. Bug fixed #1388059.

Percona XtraDB Cluster now detects older joiners which don’t have the backup lock support. Bug fixed #1390552.

Longer wsrep-recover is now handled gracefully in Debian init scripts rather than returning immediately with a false positive fail.

wsrep-recover log is now also written to mysql error log now.

Issue with stale PID files and Debian init script have been fixed now. It now emits a warning for stale PID files.

sst_in_progress file is not removed anymore in case of failed SST.

In case stored procedure containing a non-InnoDB statement (MyISAM) performed autocommit, that commit would be entered two times: at statement end and next time at stored procedure end. Bug fixed #2.

TOI now skips replication if all tables are temporary. Bugs fixed #11 and #13.

Two appliers conflicting with local transaction and resulting later in (acceptable) BF-BF lock conflict, would cause cluster to hang when the other BF thread would not grant the lock back after its local transaction got aborted. Bug fixed #7.

Bootstrapping a node tried to resolve gcomm address list specified in wsrep-cluster-address. Bug fixed #88.

xtrabackup-v2 SST did not clean the undo log directory. Bug fixed #1394836.

Inserts to a table with autoincrement primary key could result in duplicate key error if another node joined or dropped from the cluster during the insert processing. Bug fixed #1366997.

Other bugs fixed #1378138, #1377226, #1376965, #1356859, #1026181, #1367173, #1390482, #1391634, and #1392369.

0 blueprints and 27 bugs targeted

Bug report Importance Assignee Status
1373796 #1373796 SST: Joiner stuck in 'joining', but error log reports 'synced' 3 High David Bennett  10 Fix Released
1384413 #1384413 Debug builds fail 4 Medium Alexey Kopytov  10 Fix Released
1026181 #1026181 RSU processor remains hanging 1 Undecided   10 Fix Released
1248688 #1248688 Soft failure/warning on SST dependencies 1 Undecided   10 Fix Released
1274192 #1274192 Bad network on one node takes a whole cluster down 1 Undecided   10 Fix Released
1293798 #1293798 mysqldump SST is broken in current head 1 Undecided   10 Fix Released
1318866 #1318866 InnoDB: Assertion failure in thread 47550051727680 in file line 5579 1 Undecided   10 Fix Released
1356859 #1356859 Mtr against a standalone mysql-codership: innodb.innodb-autoinc 1 Undecided   10 Fix Released
1358701 #1358701 shutdown hangs because of failing replayer 1 Undecided   10 Fix Released
1361859 #1361859 global.wsrep_causal_reads no longer honored 1 Undecided   10 Fix Released
1364840 #1364840 Failing assertion: lock != ctx->wait_lock 1 Undecided   10 Fix Released
1365193 #1365193 garbd does not work when specifying cluster address without the port 1 Undecided   10 Fix Released
1366997 #1366997 Duplicate entry error for primary key following cluster size change 1 Undecided   10 Fix Released
1367173 #1367173 segmentation faults from mtr rpl suite 1 Undecided   10 Fix Released
1367956 #1367956 Garbd - errors in init script stop/start functions 1 Undecided   10 Fix Released
1369916 #1369916 Compiler warning around wsrep options 1 Undecided   10 Fix Released
1376965 #1376965 Merge RPM and debian packaging for galera 1 Undecided   10 Fix Released
1377226 #1377226 Reconcile relay log rollback in do_apply_event for 5.6.21 1 Undecided Raghavendra D Prabhu  10 Fix Released
1378578 #1378578 Resume mysqld startup in case wsrep-recover fails 1 Undecided   10 Fix Released
1381492 #1381492 percona-xtradb-cluster init script is not honoring /etc/default/ 1 Undecided   10 Fix Released
1388059 #1388059 Xtrabackup SST clobbers the gvwstate.dat file on a Joiner 1 Undecided   10 Fix Released
1390482 #1390482 mysql-systemd start-post in case of failure 1 Undecided   10 Fix Released
1390552 #1390552 Detect older joiner on donors with backup lock support 1 Undecided   10 Fix Released
1391634 #1391634 Restart logic with systemd 1 Undecided   10 Fix Released
1392369 #1392369 wsrep_cluster_address is dynamic, but our documentation says it is not 1 Undecided Hrvoje Matijakovic  10 Fix Released
1392388 #1392388 garbd runs as root on debian 1 Undecided   10 Fix Released
1394836 #1394836 sst xtrabackup-v2 did not clean undo log dir 1 Undecided   10 Fix Released
This milestone contains Public information
Everyone can see this information.