Version End of Life. Not Yet Set
Release 6.1.3 contains a small number of improvements and fixes to common command line tools, and introduces compatibility with MongoDB Atlas.
The following changes have been made to Tungsten 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:
tpm diag has been updated to provide additional feedback detailing the hosts that were gathered during the execution, and also provides examples of how to handle failures
When running on a single host configured via the ini method:shell>
tpm diagCollecting localhost diagnostics. Note: to gather for all hosts please use the "-a" switch and ensure that you have paswordless » ssh access set between the hosts. Collecting diag information on db1..... Diagnostic information written to /home/tungsten/tungsten-diag-2020-02-06-19-34-25.zip
When running on a staging host, or with the
tpm diag [-a|--allhosts]Collecting full cluster diagnostics Note: if ssh access to any of the cluster hosts is denied, use "--local" or "--hosts=<host1,host2,...>" Collecting diag information on db1..... Collecting diag information on db2..... Collecting diag information on db3..... Diagnostic information written to /home/tungsten/tungsten-diag-2020-02-06-19-34-25.zip
tpm has been changed to use
readlink which is commonly installed by default
on most operating systems, however if it is not available, you may be required
to install GNU coreutils to satisfy this dependency
tpm will now work on MacOS/X systems, provided greadlink is installed.
tpm install will no longer report that the linux distribution cannot be determined on SUSE platforms.
Fixes a condition where tpm diag would fail to set the working path correctly, especially on Debian 8 hosts.
tpm diag now checks for OS commands in additional paths (/bin, /sbin, /usr/bin and /usr/sbin)
Fixes an issue introduced in v6.1.2 where the use of the undeployall script would stop services as it removed them from systemctl control
The replicator would fail with
Unknown column '' in 'where clause when
replicating between MySQL 8 hosts where the client application would write data into the
source database host using a different collation to that of the default on the target database.
The replicator would fail due to a mismatch in these collations when querying the
information_schema.columns view to gather metadata ahead of applying to the target