Tungsten Replicator 7.1.2

Build: 81

Release Date: 13 May 2024

End of Life Date: 7 Jul 2026

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

Warning

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.

Behavior Changes (1)

The following changes 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 (1)

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

Improvements, new features and functionality (4)

Installation and Deployment (1)

• A new INI option has been added rest-api-admin-password which acts as an alias for the existingrest-api-admin-pass option.
  Issue: CT-2246

Command-line Tools (2)

• The tpm diag command now captures the output of sestatus and getenforce.
  Issue: CT-2243
• 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.
  Issue: CT-2188

Filters (1)

• A new filter, binarystringconversion, was added to provide a way to convert varchar data from one charset into another.
  Issue: CT-981

Bug Fixes (5)

Core Replicator (3)

• 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
  Issue: CT-2284
• 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.
  Issue: CT-2269
• 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
  Issue: CT-2266

Heterogeneous Replication (2)

• Fixed an issue when using the convertstringfrommysql Filter in heterogeneous deployments, that could show an error while processing an INSERT event after the PrimaryKey Filter added key specifications to it.
  Issue: CT-2260
• Fixes a bug in heterogeneous deployments that prevented CHAR and BINARY data types replicating correctly
  Issue: CT-2258