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:
This is done by running the following command:
servicenamesetdynamic -property replicator.autoRecoveryMaxAttempts -value
The service must be offline before changing the property
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
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