Skip to main content
Tungsten Clustering

Tungsten Clustering 6.1.2

Build: 94
Release Date: 20 Jan 2020
End of Life Date: 15 Aug 2024
Product End of Life

This release is past End of Life.

Behavior Changes (3)

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:

Behavior Changes (2)

  • The Passive Witness functionality is now officially DEPRECATED and will be REMOVED in version 6.2
    Issue: CT-653
  • Certified the Tungsten product suite with Java 11. A small set of minor issues have been found and fixed (CT-1091, CT-1076) along with this certification. The code is now compiled with Java compiler v11 while keeping Java 8 compatibility. Java 9 and 10 have been tested and validated but certification and support will only cover Long Term releases.
    Known Issue
    With Java 11, command line tools are slower. There is no impact on the overall clustering or replication performance but this can affect manual operations using CLI tools such as cctrl andtrepctl
    Issue: CT-1052

Installation and Deployment (1)

  • In cluster deployments with witness nodes, if the MySQL servers had been configured to listen on any port other than the standard 3306, the tpm command would default to the wrong port number. When witness hosts are in use, the tpm command will no longer "guess" the data source port automatically by running my_print_defaults. It is now mandatory to specify the MySQL data server port explicitly usingdatasource-port=[mysql_listen_port] or one of its aliases
    Issue: CT-1071

Improvements, new features and functionality (7)

Command-line Tools (4)

  • The tpm command was originally written in Ruby. This improvement converts tpmto Perl over time, starting with the tpm shell wrapper and refactoring each sub-command one-by-one. For this release, we have redone the diag, mysql and connector sub-commands. This also wraps the update sub-command to provide the CT-1093 clustering fix.
    Issue: CT-1048
  • This version includes an update to the new BETA tool to provision Replicas, and Primaries in a Composite Active/Active topology. This release fully supports provisioning of nodes in a Composite Active/Active Topology. It can be invoked by running prov-sl.sh or tps.pl. This tool will replace tungsten_provision_slave in a future release.
    Issue: CT-1070
  • Added the tpm policy subcommand to allow easy get and set cluster policy operations instead of using cctrl. For more information, please see "The tpm policy Command"
    Issue: CT-1106
  • The new changes made to the tpm command, require that the zip package be installed on all DB hosts
    Issue: CT-1111

Core Replicator (2)

  • A new JavaScript filter dropddl.js has been added to allow selective removal of specific object DDL from THL.
    Issue: CT-1092
  • A new Replicator role, thl-server, has been added. This new feature allows your Replica replicators to still pull generated THL from a Primary even when the Primary replicator has stopped extracting from the binlogs. If used in Tungsten Cluster, this feature must only be enabled when the cluster is in MAINTENANCE mode.
    Issue: CT-58

Manager (1)

  • The new default datasources sort order is alphabetical when using the cctrl ls command. Additionally, the sort order of the datasources list is now configurable. The behavior is controlled by the tpm configuration property cctrl.sort.datasources.alphabetically which has a default value of true (meaning alpha sort). If set to false, the sort is ordered by datasource role, so the Primary or relay will appear first, followed by the Replicas. For example, use the following in the INI file for role-based sorting:
    property=cctrl.sort.datasources.alphabetically=false
    Issue: CT-1018

Bug Fixes (22)

Behavior Changes (1)

  • Corrected resource leak when loading Java keystores
    Issue: CT-1091

Installation and Deployment (1)

Command-line Tools (6)

  • When performing an update of a cluster withtpm, the cluster would be switched toMAINTENANCE but would remain in this policy after the update. The original policy is now retained during the update.
    Issues: CT-595, CT-1093
  • The deployall script was only able to install init.d system startup scripts. In this release, the script will now detect the initialization system in use (systemd or initd) and prefer systemd when both are available. **For systemd configurations only:** For continuity of service reasons, the deployall script does NOT restart individual components when called, it will only install systemd scripts. This implies that, right after a call todeployall and before host restart, the system will stay in a mixed mode where systemd scripts are in place but components were started without systemd, so won’t be controllable by it. In order to align the configuration, you will need to run
    shell> component stop sysd
    shell> sudo systemctl start tcomponent
    For example:
    shell> connector stop sysd
    shell> sudo systemctl start tconnector
    Issue: CT-853
  • When issuing tpm connector --samples, the output displayed clear text passwords. In this release the passwords are obfuscated.
    Issue: CT-1021
  • Continuent Tungsten Clustering now uses the xtrabackup command instead of the deprecated innobackupex to create and restore backups. A new check was added to TPM for validating different xtrabackup versions along with MySQL version compatibility. The oldest supported version of xtrabackup is v2.3
    Issue: CT-1074
  • Fixed error message to indicate the need to specify a service on Composite Active/Active clusters for thetungsten_find_position and tungsten_find_seqno commands.
    Issue: CT-1098
  • The tpm command no longer reports warnings about existing system triggers with MySQL 8+
    Issue: CT-1099

Core Replicator (4)

  • When configuring SSL for the Connector only, the Replicator would fail to start due to the Replicator also looking for the SSL configuration.
    Issue: CT-956
  • The following warnings would appear in the replicator log due to GTID events not being handled.
    WARN extractor.mysql.LogEvent Skipping unrecognized binlog event type 33, 34 or 35)
    The WARN message will no longer appear, however GTID Events are still not handled in this release, but will be fully extracted in a future release.
    Issue: CT-1114
  • If a JSON field contained a single quote, the replicator would break during the apply stage whilst running the generated SQL into MySQL. Single quotes will now be properly escaped to solve this issue
    Issue: CT-983
  • Under rare circumstances (network packet loss or MySQL Server hang), the replicator would also hang until restarted. This issue has been fixed by using specific network timeouts in both the replicator and in the Drizzle jdbc driver connection logic
    Issue: CT-1034

Connector (2)

  • Fixed an issue where some applications might fail to connect to the Connector with MariaDB 10+ Previously, when using MariaDB 10+, the Connector would be confused by the 10 and will think it is a MySQL 8+ server. By default, the Connector will offer to connect with caching_sha2_password. If the application does not know how to switch authentication plugins, it would fail with a message similar to the following:
    The server requested authentication method unknown to the client [caching_sha2_password]
    The previous work-around was to specify the authentication plugin using the tpm command:
    --property=defaultAuthPlugin=mysql_native_password
    Issue: CT-1033
  • Improved Tungsten Connector bridge mode performance when transferring small amounts of data.
    Issue: CT-1081

Manager (8)

  • When using the cctrl command interactively, the cluster topology TAB completion was showing invalid options. Invalid options have been removed.
    Issue: CT-979
  • Fixed an issue where long-duration operations like failover and switch would create false positives about network partitioning after completion.
    Issue: CT-1023
  • Fixed the cctrl command so that the '[SSL]' indicator in the `ls` output is displayed. This is a Version 5 feature that was lost in v6.0.0, now restored.
    Issue: CT-1061
  • Fixed the cctrl command datasource restore which was failing inComposite Active/Active cluster deployments with: <errortext>ERROR: MORE THAN ONE PRIMARY DATA SOURCE FOUND</errortext>.
    Issue: CT-1062
  • Continuent Tungsten Clustering now only checks for a running MySQL server when the backup method is 'mysqldump' in cctrl. Background: Running datasource restore inside cctrlwould fail when the MySQL server was not running. Only the 'mysqldump' method requires a running MySQL server. The 'xtrabackup-full' and 'xtrabackup-incremental' methods will work even if MySQL is stopped.
    Issue: CT-1077
  • tungsten_find_orphaned was displaying an incorrect error message if a service name wasn't supplied correctly.
    Issue: CT-1079
  • tungsten_find_orphaned would error with 'Argument "" isn't numeric in addition'.
    Issue: CT-1080
  • Fixed an issue where Composite clusters with only a single site would come up as SHUNNED after install.
    Issue: CT-1101