Version End of Life. 7 June 2019
This is a bugfix release.
tpm (in [Tungsten Clustering for MySQL 5.3 Manual]) now outputs a note and recommendation for performing backups of your cluster when installation has been completed.
A new Nagios compatible check script has been added to the release, check_tungsten_policy (in [Tungsten Clustering for MySQL 5.3 Manual]), which returns the currently active policy mode.
For more information, see The check_tungsten_policy Command (in [Tungsten Clustering for MySQL 5.3 Manual]).
tpm (in [Tungsten Clustering for MySQL 5.3 Manual]) would fail during installation if the current directory was not writable by the current user.
When performing a tpm update (in [Tungsten Clustering for MySQL 5.3 Manual]) in a cluster with an active witness, the host with the witness will not be restarted correctly resulting in the witness being down on that host.
Using tpm connector (in [Tungsten Clustering for MySQL 5.3 Manual]) at the command-line would
fail if the core MySQL configuration file (i.e.
/etc/my.cnf) did not exist.
Issues: CT-673, CT-691
During a relay failover within a composite or multi-site mukti-mastero deployment, if the communications had also failed between sites when the failover occured the manager would be unable to determine the correct master of the remote site.
In a deployment, single cluster or composite multimaster where there is either the potential for high-latency across sites, or high latency within a site due to high loads on the connectors, the manager could mis-identify this high latency as a failure. This would trigger a quorum validation. These would be reported as network hangs, even though the result of the quorum check would be valid.
To address this, the processing of router notifications processed by the connector and all other operations have been separated. This reduces the change of a heartbeat gap between hosts and therefore the connectors are available to the managers even under high loads or latency.
Release 5.3.3 is a bug fix release.
The output from thl list (in [Tungsten Replicator 5.3 Manual]) now includes the name of the file for the correspnding THL event. For example:SEQ# = 0 / FRAG# = 0 (last frag) - FILE = thl.data.0000000001 - TIME = 2018-08-29 12:40:57.0 - EPOCH# = 0 - EVENTID = mysql-bin.000050:0000000000000508;-1 - SOURCEID = demo-c11 - METADATA = [mysql_server_id=5;dbms_type=mysql;tz_aware=true;is_metadata=true;service=alpha;shard=tungsten_alpha;heartbeat=MASTER_ONLINE] - TYPE = com.continuent.tungsten.replicator.event.ReplDBMSEvent - OPTIONS = [foreign_key_checks = 1, unique_checks = 1, time_zone = '+00:00', ##charset = US-ASCII]
When running tpm diag (in [Tungsten Replicator 5.3 Manual]), the operation would fail if the
/etc/mysqldirectory does not exist.