Continuent Tungsten 4.0 is a major release which is designed to provide integration between Continuent Tungsten 4.0 and Tungsten Replicator 4.0. Providing MySQL clustering support, while providing replication for MySQL, Oracle, and out to datawarehouses such as HP Vertica, Amazon Redshift and Hadoop.
For more information on replicating data out of a cluster, see Section 3.4, “Replicating Data Out of an Existing Cluster”.
The following issues may affect the operation of Continuent Tungsten and should be taken into account when deploying or updating to this release.
When using read-only connectors, and making use of explicit transactions (i.e. with autocommit disabled), queries may be routed to the master, rather than a slave.
For security purposes you should ensure that you secure the following areas of your deployment:
Ensure that you create a unique installation and deployment user, such as tungsten, and set the correct file permissions on installed directories. See Section B.2.3, “Directory Locations and Configuration”.
When using ssh and/or SSL, ensure that the ssh key or certificates are suitably protected. See Section B.2.2.2, “SSH Configuration”.
Use a firewall, such as iptables to protect the network ports that you need to use. The best solution is to ensure that only known hosts can connect to the required ports for Continuent Tungsten. For more information on the network ports required for Continuent Tungsten operation, see Section B.2.2.1, “Network Ports”.
If possible, use authentication and SSL connectivity between hosts to protext your data and authorisation for the tools used in your deployment. See Section 2.7, “Deploying SSL Secured Replication and Administration” for more information.
Under certain circumstances, the rsync process can randomly fail during the installation/ deployment process when using the staging method of deployment. The error code returned by rsync may be 12 or 23.
The error is transient and non-specific and deployment should be retried.
tpm now correctly checks the functionality of the 'echo' protocol to validate 'echo'.
Force a new directory under /opt/continuent/releases during tpm update if components are being added/removed.
Add manager status command to cctrl.
Update tpm to force the replication timezone to GMT.
Attempting concurrent operations in cctrl generates an exception.
Using the recover command does a gratuitous change of policy.