Version End of Life. 30 May 2021
This is a bugfix release.
The following issues may affect the operation of Continuent Tungsten and should be taken into account when deploying or updating to this release.
It was previously impossible to change from a non-SSL installation to an SSL installation using self-generated certificates if an INI style configuration was being used. This can now be achieved by using the following command-line:shell>
tools/tpm update --replace-release --replace-jgroups-certificate --replace-tls-certificate
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 6.0.1 is a bugfix release.
The following changes have been made to Continuent Replicator 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:
The tungsten_set_position (in [Continuent Tungsten 4.0 Manual]) and tungsten_get_position commands have been deprecated and will be removed in the 6.1.0 release. These commands only worked with MySQL datasources. Use the dsctl (in [Continuent Tungsten 4.0 Manual]) command, which works with a much wider range of datasources.
The trepctl services (in [Tungsten Replicator 2.1 Manual]) has been updated to support the auto-refresh option using the
The trepctl (in [Tungsten Replicator 2.1 Manual]) has been updated with a new command, servicetable (in [Tungsten Replicator 6.0 Manual]) command. This outputs the status information for multiple services in a tabular format to make it easier to identify the state for multi-service replicators. For example:shell>
trepctl servicetableProcessing servicetable command... Service | Status | Role | MasterConnectUri | SeqNo | Latency -------------------- | ------------------------------ | ---------- | ------------------------------ | ---------- | ---------- alpha | ONLINE | slave | thl://trfiltera:2112/ | 322 | 0.00 beta | ONLINE | slave | thl://ubuntuheterosrc:2112/ | 12 | 4658.59 Finished servicetable command...
The command also supports the auto-refresh option,
This change is not backwards compatible; when upgrading, you should upgrade slaves first and then the master to ensure compatibility. Once you have extracted data with the GEOMETRY type into THL, the THL will no longer be compatible with any version of the replicator that does not support the GEOMETRY datatype.
When using Net::SSH within tpm (in [Tungsten Replicator 2.1 Manual]), more detailed information about any specific failures or errors is now provided.
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
- Optimizing deletes in row-based replication could delete the wrong rows if the
pkeyhad not been enabled.
The trepctl status (in [Tungsten Replicator 2.1 Manual]) would fail badly if the service name did not exist in the configuration, or if multipl services were configured.
Issues: CT-545, CT-593
When using tpm (in [Tungsten Replicator 2.1 Manual]) with the INI method, the command would search multiple locations for suitable INI files. This could lead to multiple definitions of the same service, which could in turn lead to duplication of the installation process and occasional failures. If multiple INI files are found, a warning is now produced to highlight the potential for failures.
Using trepctl qs (in [Tungsten Replicator 5.2 Manual]) where the sequence number could be larger than an
INTwould cause an error.
The templates for ddlscan (in [Tungsten Replicator 2.1 Manual]) for MySQL to Oracle do not escape field names correctly.
Issues: CT-581, CT-582
It should just show the data format:yyyy-MM-dd-HH
The templates for ddlscan (in [Tungsten Replicator 2.1 Manual]) for Oracle to Redshift failed to handle the
This change is not backwards compatible; when upgrading, you should upgrade slaves first and then the master to ensure compatibility with the metadata.
truncatetext(in [Tungsten Replicator 2.1 Manual]) filter was not configurable within all topologies. The configuration has now been updated so that the filter can be used in MySQL and other database environments.