Version End of Life. 7 June 2019
This is a bugfix release.
The tpm diag (in [Tungsten Replicator 2.1 Manual]) 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
Copies of all the cluster configuration and
Copies of all the
including directory configurations.
The output from the connector cluster-status (in [Tungsten Clustering for MySQL 5.3 Manual]) command.
The output from all services in multimaster clustering deployments.
Improvements to the clarity of some commands.
The INI files used by tpm (in [Tungsten Replicator 2.1 Manual]) (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.
The first execution of ls (in [Continuent Tungsten 4.0 Manual]) within cctrl (in [Continuent Tungsten 4.0 Manual]) within multimaster clusters could fail to provide the cluster status information at the top (world) level.
Issues: CT-633, CT-634
Release 5.3.2 is a bug fix release.
tpm (in [Tungsten Replicator 2.1 Manual]) 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.
The tungsten_provision_slave (in [Continuent Tungsten 4.0 Manual]) 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
Using trepctl qs (in [Tungsten Replicator 5.2 Manual]) where the sequence number could be larger than an
INTwould cause an error.