Version End of Life. Not Yet Set
Release 6.1.17 contains a number of minor bug fixes and improvements.
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:
Improvements, new features and functionality
Added the ability to turn auto recovery on or off dynamically, removing the need to run tpm update.
This is done by running the following command:
servicenamesetdynamic -property replicator.autoRecoveryMaxAttempts -value
The service must be offline before changing the property
When services are deployed with systemd and MySQL could not start due to an error, tpm would not be able to later start MySQL
deployall script now properly displays the executable prefix for restarting services, typically mm_treplicator in Multi-Site/Active-Active replicator-only installs, as well as the full path to component binaries
When MySql services where badly installed, some distribution could show a
“not-found” status within systemctl, confusing tpm
The tpm command now communicates properly when there is no INI configuration file or staging-method
deploy.cfg configuration defined.
tungsten_monitor.rb script no longer uses sudo to send emails if the configuration doesn't allow it.
Improves the tpm diag command so that it waits 2 seconds for replicator thread dump to complete.
tpm now properly reports errors upon timeout executing commands. Typically, when a host is down, when upgrading or installing, tpm will now properly report that pinging this host failed.
Due to a change in binlogging behavior from MySQL 5.7 onwards (Including Aurora) when using the standalone Tungsten Replicator to configure bi-directional replication with unprivileged access (ie unable to control binlogging behavior), certain DDL statements failed to be tagged correctly causing them to be re-applied to the originating source database, resulting in replicator errors.
When connecting to a THL server, a client will now connect to the next available host in its THL uri, if the first does not have the sequence number that the client requires. The client will then fail only if none of the hosts from the uri can provide the needed sequence number.
Fixed an issue when using Parallel apply that would show a
NullPointerException in case an event could either not be found or
be corrupted in THL. This will now display a correct message
Missing or corrupted event from storage
Fixed an issue with the batch loader where
with milliseconds would be replicated as .000 instead of the real millisecond value.
Fixed an issue where trepctl was leaving JMX connections opened.
Added more debug information for detecting possible hanging connections while a THL client connects to the THL server. Also, added socket timeout for the connection initialization
Fixed the EnumToString and pkey filters to renew their database connections (every hour by default). This can be changed with the following properties: