3.7. Continuent Tungsten 4.0.2 GA (1 October 2015)

Version End of Life. 31 October 2018

Release Notes 4.0.2 is a bugfix release that contains critical fixes and improvements.

Known Issue

The following issues may affect the operation of Continuent Tungsten and should be taken into account when deploying or updating to this release.

  • 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 Directory Locations and Configuration (in [Continuent Tungsten 4.0 Manual]).

    • When using ssh and/or SSL, ensure that the ssh key or certificates are suitably protected. See SSH Configuration (in [Continuent Tungsten 4.0 Manual]).

    • 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 Network Ports (in [Continuent Tungsten 4.0 Manual]).

    • If possible, use authentication and SSL connectivity between hosts to protext your data and authorisation for the tools used in your deployment. See Deploying SSL Secured Replication and Administration (in [Continuent Tungsten 4.0 Manual]) 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.

    Issues: CONT-1343

Improvements, new features and functionality

  • Installation and Deployment

    • The tpm (in [Continuent Tungsten 4.0 Manual]) script can now properly update a master/slave cluster to a composite (SOR) cluster without intervention. Follow the instructions for tpm upgrade (in [Continuent Tungsten 4.0 Manual]) and add the --replace-release option. The extra option is not required if you are upgrading to a new version.

      Issues: CONT-47

    • The tpm (in [Continuent Tungsten 4.0 Manual]) script will display a warning if NTP does not appear to be running.

      Issues: CONT-110

Bug Fixes

  • Installation and Deployment

    • The tpm (in [Continuent Tungsten 4.0 Manual]) script could lock tables trying to inspect information_schema for MyISAM tables. The script will now look for MyISAM files in the datadir if possible.

      Issues: CONT-938

  • Core Replicator

    • The replicator could incorrectly parse binary logs that start with a timestamp on 1/1/1970 and cause errors on systems that use STRICT_TRANS_TABLES.

      Issues: CONT-869

    • The replicator could hang when transitioning from ONLINE (in [Tungsten Clustering (for MySQL) 6.1 Manual]) to OFFLINE:ERROR (in [Tungsten Replicator 6.1 Manual]). This could happen during the first attempt or following multiple repeated attempts.

      Issues: CONT-1055

  • Tungsten Connector

    • The connector would incorrectly connect to a master when processing the BEGIN command on a read-only connection.

      Issues: CONT-895

    • The connector would incorrectly parse statements that begin with use database;....

      Issues: CONT-949

    • The connector might not forward all request errors to the application, which would in this case wait indefinitely for a response.

      Issues: CONT-975

    • The connector could lose track of the cluster policy and cause the application to hang if it doesn't communicate with a manager.

      Issues: CONT-999

    • The mechanism that keeps idle connections active could become hung by long running transactions.

      Issues: CONT-1047

  • Tungsten Manager

    • The connector could temporarily stop processing requests during the upgrade of an SOR deployment or restarting all managers for a dataservice.

      Issues: CONT-1012

    • The failure of multiple slave replicators could result in only one replicator being put back ONLINE (in [Tungsten Clustering (for MySQL) 6.1 Manual]).

      Issues: CONT-1051

Known Issues

The following issues may affect the operation of Continuent Tungsten and should be taken into account when deploying or updating to this release.

  • Core Replicator

    • The replicator can hit a MySQL lock wait timeout when processing large transactions.

      Issues: CONT-1106

    • The replicator can run into OutOfMemory when handling very large Row-Based replication events. This can be avoided by setting --optimize-row-events=false (in [Continuent Tungsten 4.0 Manual]).

      Issues: CONT-1115

  • Tungsten Manager

    • The manager fails to read security.properties during startup. If this occurs, the manager will print a warning in tmsvc.log (in [Continuent Tungsten 4.0 Manual]).

      Issues: CONT-1070