1.1. Tungsten Clustering 7.1.2 GA (3 Apr 2024)

Version End of Life. Not Yet Set

Release 7.1.2 contains a number of key bug fixes and improvements.

Note

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

Behavior Changes

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:

  • Installation and Deployment

    • The systemd startup scripts will now have a dependency on the time-sync service (if available) being started before tungsten components.

      Issues: CT-2257

Improvements, new features and functionality

  • Installation and Deployment

    • A new INI option has been added rest-api-admin-password which acts as an alias for the existing rest-api-admin-pass option.

      Issues: CT-2246

  • Command-line Tools

    • 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

  • Filters

    • A new filter, binarystringconversionfilter, was added to provide a way to convert varchar data from one charset into another.

      Issues: CT-981

Bug Fixes

  • Installation and Deployment

    • The tpm update command now properly recognizes the INI option dataservice-composite-datasources as an alias for composite-datasources.

      Issues: CT-2241

  • Core Replicator

    • 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.

      Note

      This bug was detected in v7.1.2 build 42, and fixed in v7.1.2 build 81

      Issues: CT-2284

  • Tungsten Connector

    • 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.

      Note

      This bug was detected in v7.1.2 build 42, and fixed in v7.1.2 build 81

      Issues: CT-2285

  • Tungsten Manager

    • 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