Version End of Life. Not Yet Set
Release 7.1.2 contains a number of key bug fixes and improvements.
v7.1.2 was re-released as build 81 on 13 May 2024 to fix two critical bugs that exist in the original build 42 release (CT-2284, CT-2285).
Due to JGroup libraries being updated in the 7.1.0 release, managers running releases older than 7.1.0 will not communicate with managers running 7.1.0+ therefore when upgrading to this release from anything older than 7.1.0, all nodes must be upgraded before proper cluster communication will be restored. Ensure the cluster is in MAINTENANCE before beginning the upgrade and do NOT SHUN nodes whilst a mix of manager versions are running.
The following changes have been made to Tungsten Cluster and may affect existing scripts and integration tools. Any scripts or environment which make use of these tools should check and update for the new configuration:
Improvements, new features and functionality
A new command, tungsten_mysql_ssl_setup, has been introduced to create all needed security files for the MySQL database server. tungsten_mysql_ssl_setup will act as a direct replacement for the mysql_ssl_rsa_setup command which is not included with either Percona Server or MariaDB. This command will now be called by tpm cert gen mysqlcerts instead of mysql_ssl_rsa_setup.
Issues: CT-2188
The tpm diag command now captures the output of sestatus and getenforce.
Issues: CT-2243
The tpm update command now properly recognizes the INI option dataservice-composite-datasources as an alias for composite-datasources.
Issues: CT-2241
Fixed an issue where the shard name of an event could be badly identified, which could potentially lead to deadlocks when parallel applier was enabled.
Issues: CT-2266
Fixed an issue caused by a MySQL behavior change in how a DROP TABLE is logged in the binlog, that made
the replicator unable to identify correctly if the query had tungsten metadata in it.
Issues: CT-2269
Event extraction can sometimes generate an empty fragment (for a multi fragment transaction). This in turn can lead to bad shard detection. While empty fragment is expected, shard detection will now use the last non-empty fragment.
This bug was detected in v7.1.2 build 42, and fixed in v7.1.2 build 81
Issues: CT-2284
Fixed an issue where some applications won't be able to connect to the connector under bridge mode and ip filtering in place through authorized_hosts.
Issues: CT-2261
Fixed a bug where any new connection to the connector would trigger a call to hostname, potentially exhausting CPU resources.
This bug was detected in v7.1.2 build 42, and fixed in v7.1.2 build 81
Issues: CT-2285
Fixes an issue with data source monitoring when client and server don't share the same default authentication plugins.
Issues: CT-2233
The tpm diag command no longer errors out on witness hosts installed with the Staging method.
Issues: CT-2262
Fixes a bug that would cause a switch to fail if the cluster had been idle for more than 15 minutes.
Issues: CT-2263