Percona XtraDB Cluster 5.6.34-26.19

Percona announces the release of Percona XtraDB Cluster 5.6.34-26.19 on December 14, 2016. Binaries are available from the downloads section or our software repositories.

Percona XtraDB Cluster 5.6.34-26.19 is now the current release, based on the following:

All Percona software is open-source and free. Details of this release can be found in the 5.6.34-26.19 milestone on Launchpad.

Deprecated

  • The following encryption modes are now deprecated:
    • encrypt=1
    • encrypt=2
    • encrypt=3

The default is encrypt=0 with encryption disabled. The recommended mode now is the new encrypt=4, which uses SSL files generated by MySQL.

For more information, see Encrypting PXC Traffic.

New Features

  • Added encrypt=4 mode for SST encryption that uses SSL files generated by MySQL. Modes 1, 2, and 3 are now deprecated.

Fixed Bugs

  • Optimized IST donor selection logic to avoid SST. Child processes are now cleaned-up and node state is resumed if SST fails.
  • Added init.ok to the list of files that do not get removed during SST.
  • Fixed error with ASIO library not acknowledging an EPOLLIN event when building Galera.
  • Fixed stalling of DML workload on slave node caused by FLUSH TABLE executed on the master.
    For more information, see 1629296.
  • Fixed super_read_only to not apply to Galera replication applier.
    For more information, see 1634295.
  • Redirected netcat output to stdout to avoid it in the log.
    For more information, see 1625968.
  • Enabled replication of ALTER USER statements.
    For more information, see 1376269.
  • Changed the wsrep_max_ws_rows variable to ignore non-replicated write-sets generated by DML action on temporary tables (explicit or implicit).
    For more information, see 1638138.
  • Fixed SST to fail with an error if SSL is not supported by socat, instead of switching to unencrypted mode.
  • Fixed SST with SSL to auto-generate a 2048-bit dhparams file for versions of socat before 1.7.3. These older versions use 512-bit dhparams file by default that gets rejected by newer clients with dh key too small error.
  • PXC-731: Changed the wsrep_cluster_name variable to read-only, because changing it dynamically leads to high overhead.
    For more information, see 1620439.
  • PXC-732: Improved error message when any of the SSL files required for SST are missing.
  • PXC-735: Fixed SST to fail with an error when netcat is used (transferfmt=nc) with SSL encryption (encrypt set to 2, 3 or 4), instead of silently switching to unencrypted mode.
  • Fixed faulty switch case that caused the cluster to stall when the repl.commit_order variable was set to 2 (LOCAL_OOOC mode that should allow out-of-order committing for local transactions).

Help us improve our software quality by reporting any bugs you encounter using our bug tracking system. As always, thanks for your continued support of Percona!

8 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
doonie

Seems like the galera lib API v26 is not pushed out with this release

2016-12-15 12:39:08 0 [Note] /usr/sbin/mysqld (mysqld 5.6.34-79.1-56-log) starting as process 20267 …
2016-12-15 12:39:08 20267 [Note] WSREP: Read nil XID from storage engines, skipping position init
2016-12-15 12:39:08 20267 [Note] WSREP: wsrep_load(): loading provider library ‘/usr/lib/libgalera_smm.so’
2016-12-15 12:39:08 20267 [ERROR] WSREP: provider interface version mismatch: need ’26’, found ’25’
2016-12-15 12:39:08 20267 [ERROR] WSREP: wsrep_load(): interface version mismatch: my version 26, provider version 25
2016-12-15 12:39:08 20267 [ERROR] WSREP: wsrep_load(/usr/lib/libgalera_smm.so) failed: Invalid argument (22). Reverting to no provider.
2016-12-15 12:39:08 20267 [Note] WSREP: Read nil XID from storage engines, skipping position init
2016-12-15 12:39:08 20267 [Note] WSREP: wsrep_load(): loading provider library ‘none’

Hrvoje Matijakovic

Can you please provide more information on distro version, and from which version are you trying to upgrade from.

doonie

Issue solved with Hrvoje, turns out that the server was using the wrong lib

ii percona-galera-3 3.8-3390-0ubuntu6 amd64 Galera replication framework for Percona XtraDB Cluster

and not

ii percona-xtradb-cluster-galera-3 3.19-1.xenial amd64 Metapackage for latest version of galera3.

thanks!

Tobias Brox

I have the opposite problem on EL6, using Percona-updated-x86_64 and 5.5:

170131 4:36:16 [ERROR] WSREP: provider interface version mismatch: need ’25’, found ’26’
170131 4:36:16 [ERROR] WSREP: wsrep_load(): interface version mismatch: my version 25, provider version 26

$ sudo yum downgrade Percona-XtraDB-Cluster-galera-3 percona-xtrabackup

Removed:
Percona-XtraDB-Cluster-galera-3.x86_64 0:3.19-1.rhel6 percona-xtrabackup.x86_64 0:2.3.6-1.el6

Installed:
Percona-XtraDB-Cluster-galera-3.x86_64 0:3.17-1.rhel6 percona-xtrabackup.x86_64 0:2.3.5-1.el6

… and the database server is up and running again.

Hrvoje Matijakovic

Hi Tobias,

Can you please provide more details about the installed packages that you currently have, and from what version you were trying the upgrade to this version.

Thank you

lyledodge

I’m also having the wsrep 26 vs. 25 version mismatch. This on Ubuntu 16.04 64-bit with Percona 5.6.34-26.19-1.xenial.

/var/lib/mysql/error.log:
2017-02-28 23:41:07 0 [Note] /usr/sbin/mysqld (mysqld 5.6.34-79.1-56) starting as process 3628 …
2017-02-28 23:41:07 3628 [Note] WSREP: Read nil XID from storage engines, skipping position init
2017-02-28 23:41:07 3628 [Note] WSREP: wsrep_load(): loading provider library ‘/usr/lib/libgalera_smm.so’
2017-02-28 23:41:07 3628 [ERROR] WSREP: provider interface version mismatch: need ’26’, found ’25’
2017-02-28 23:41:07 3628 [ERROR] WSREP: wsrep_load(): interface version mismatch: my version 26, provider version 25
2017-02-28 23:41:07 3628 [ERROR] WSREP: wsrep_load(/usr/lib/libgalera_smm.so) failed: Invalid argument (22). Reverting to no provider.
2017-02-28 23:41:07 3628 [Note] WSREP: Read nil XID from storage engines, skipping position init
2017-02-28 23:41:07 3628 [Note] WSREP: wsrep_load(): loading provider library ‘none’

Thanks for any tips. At this time my cluster is reduced to a single node, we’re alive but degraded.

lyledodge

It seems I *may* have resolved my issue by installing percona-xtradb-cluster-galera-3.x in place of percona-galera-3.

Should the upgrade to Percona 5.6.34-26.19-1.xenial have done this for me?