3.10. Continuent Tungsten 2.2.0 NYR (Not Yet Released)

This is a recommended release for all customers as it contains important updates and improvements to the stability of the manager component, specifically with respect to stalls and memory usage that would cause manager failures.

Behavior Changes

The following changes have been made to Continuent Tungsten 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:

  • Within composite clusters, TCP/IP port 7 connectivity is now required between managers on each site to confirm availability.

Bug Fixes

  • Installation and Deployment

    • To ensure that the correct number of the managers and witnesses are configured within the system, tpm has been updated to check and identify potential issues with the configuration. The installation and checks operate as follows:

      • If there are an even number of members in the cluster (i.e. provided to --members option):

        • If witnesses are provided through --witnesses, continue normally.

        • If witnesses are not provided through --witnesses, an error is thrown and installation stops.

      • If there are an odd number of members in the cluster (i.e. provided to --members option):

        • If witnesses are provided through --witnesses, a warning is raised and the witness declaration is ignored.

        • If witnesses are not provided through --witnesses, installation continues as normal.

      The number of members is calculated as follows:

      • Explicitly through the --members option.

      • Implied, when --active-witnesses=false, then the list of hosts declared in --master and --slaves.

      • Implied, when --active-witnesses=true, then the list of hosts declared in --master and --slaves and --witnesses.

      Issues: TUC-2105

    • If ping traffic was denied during installation, then installation could hang while the ping check was performed. A timeout has now been added to ensure that the operation completes successfully.

      Issues: TUC-2107

  • Backup and Restore

    • When using xtrabackup 2.2.x, backups would fail if the innodb_log_file_size option within my.cnf was not specified. tpm has been updated to check the value and existence of this option during installation and to provide a warning if it is not set, or set to the default.

      Issues: TUC-2224

  • Tungsten Connector

    • The connector will now re-connect to a MySQL server in the event that an opened connection is found closed between two requests (generally following a wait_timeout expiration).

      Issues: TUC-2163

    • When initially starting up, the connector would open a connection to the configured master to retreive configuration information, but the connection would never be closed, leading to open unused connections.

      Issues: TUC-2166

    • The cluster status output by the tungsten cluster status within a multi-site cluster would fail to display the correct states of different data sources when an entire data service was offline.

      Issues: TUC-2185

    • When the connector has been configured into read-only mode, for example using --application-readonly-port=9999, the connector would mistakenly route statements starting set autocommit=0 to the master, instead of being routed to a slave.

      Issues: TUC-2198

    • When operating in bridge mode, the connector would retain the client connection when the server had closed the connection. The connector has been updated to close all client connections when the corresponding server connection is closed.

      Issues: TUC-2231

  • Tungsten Manager

    • The manager could enter a situation where after switching a relay on one physical service, remote site relay is incorrectly reconfigured to point at the new relay. This has been corrected so that reconfiguration no longer occurs in this situation.

      Issues: TUC-2164

    • Recovery from a composite cluster failover could create a composite split-brain situation.

      Issues: TUC-2178

    • A statement of record (SOR) cluster would be unable to recover a failed dataservice.

      Issues: TUC-2194

    • A composite datasource would not go into failsafe mode if all the managers within the cluster were stopped.

      Issues: TUC-2206

    • If a composite datasource becomes isolated due to a network partition, the failed datasource would not go into failsafe mode correctly.

      Issues: TUC-2207

    • If a witness became isolated from the rest of the cluster, the rules would not exclude the failed witness and this could lead to memory exhaustion.

      Issues: TUC-2214

  • Documentation

    • The descriptions and definitions of the archive and standby roles has been clarified in the documentation.

      For more information, see Understanding Datasource Roles (in [Tungsten Clustering (for MySQL) 6.1 Manual]).

    • The documentation for the recovery of a multi-site multi-master installation has been updated to provide more information when covering.

      Issues: TUC-2175

      For more information, see Resetting a single dataservice (in [Tungsten Clustering (for MySQL) 6.1 Manual]).