Version End of Life. 31 July 2020
This is a bugfix release.
Improvements, new features and functionality
The tpm diag command has been improved to include more information about the environment, including:
The output from the lsof command.
The output from the ps command.
The output from the show full processlist command within mysql.
Copies of all the .properties
configuration files.
Copies of all the cluster configuration and
.properties files.
Copies of all the my.cnf files,
including directory configurations.
The output from the connector cluster-status command.
The output from all services in active/active clustering deployments.
Improvements to the clarity of some commands.
The INI files used by tpm (if using INI installs) are included.
Issues: CT-530, CT-611, CT-615, CT-623
A script used internally by the manager to determine the status
of replication, called
mysql_checker_query.sql, had been
identified as providing bad information under certain complex
circumstances. The effects of the bad script could include out
of memory failures. The script and query has been rewritten.
Issues: CT-457
The first execution of ls within cctrl within active/active clusters could fail to provide the cluster status information at the top (world) level.
Issues: CT-551
An error executing the query checker script would not get identified and trapped properly.
Issues: CT-632
Within a running cluster, managers on different hosts with a composite cluster could show different cluster state information after a switch operation.
Issues: CT-633, CT-634
Tungsten Clustering 5.3.2 Includes the following changes made in Tungsten Replicator 5.3.2
Release 5.3.2 is a bug fix release.
tpm would mistakenly report issues with JSON columns during installation which no longer applies as JSON support for MySQL 5.7 was added in 6.0.0.
Issues: CT-635
The tungsten_provision_slave could hang within different scenarios, including being executed in the background, or part of a background script or cronjob. The script could also fail to restart MySQL correctly
Issues: CT-319, CT-572
When setting optimizeRowEvents back to false (it is enabled by default), the replicator could fail with IndexOutOfBound errors.
Issues: CT-631
Using trepctl qs where the sequence number could be larger than an
INTwould cause an error.Issues: CT-642