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 Cluster 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
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
This will prevent the following case: in Composite Active/Active topologies, a given connection starts to write data to a site. The site fails, connection gets reconnected the other site and resumes writing. However the data written to the 1st site has not reached the 2nd site, thus data will not be consistent.
Default is to reject reconnections that follow a write operation (
RW_STRICT connection or SmartScale after a write) and to allow
reconnection after a read operation (
RO_RELAXED or SmartScale after a read) which translates to
It is still possible to get the previous behavior (reconnecting transparently connections cross-site) by specifying both
--connector-allow-cross-site-reconnects-for-reads=true, at your own risk
This setting can be over-ridden by using the following tpm property
VALUE set to autodetect, this value will mirror the MySQL
connect_timeout system variable. Set to 0 for infinite timeout.