Version End of Life. 31 October 2018
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.
We recommend Java 7 for all Continuent Tungsten 2.0 installations. Continuent are aware of issues within Java 6 that cause memory leaks which may lead to excessive memory usage within the manager. This can cause the manager to run out of memory and restart, without affecting the operation of the dataservice. These problems do not exist within Java 7.
Tungsten Manager: Improved monitoring fault-tolerance
Under normal operating conditions, the Tungsten Manager on each DB server host will monitor the local Tungsten Replicator and the database server running on that host and relay the monitoring information thus collected to the other Tungsten Managers in the cluster. In previous releases, Continuent Tungsten was even able to continue to monitor database servers even if a manager on a given DB server node was not running.
With this release, this functionality has been generalized to handle the monitoring of both database servers and Tungsten replication such that any time a Tungsten Manager is not running on a given DB server host, the remaining Tungsten Managers in the cluster will take over the monitoring activities for both database servers and Tungsten Replicators until the manager on that host resumes operations. This activity takes place automatically and does not require any special configuration or intervention from an administrator.
The new functionality means that if you have configured Tungsten
to fence replication failures and stops, and you stop all
Tungsten services on a given node, the rest of the cluster will
respond by fencing the associated data source to an
Full recovery of a failed node requires that a Tungsten Manager be running on the node.
Tungsten Connector/Tungsten Manager: Full support for 'relative latency'
Support for the use and display of the
relativeLatency has been expanded and
improved. By default, absolute latency is used by the cluster to
determine the configuration.
When relative latency is used, the difference between the last
commit time and the current time is displayed. This will show an
increasing latency even on long running transactions, or in the
event of a stalled replicator. To enable relative latency, use
option to tpm during configuration.
The following changes to the operation of Continuent Tungsten have been added to this release when the use of relative latency is enabled:
The output of SHOW
SLAVE STATUS has been updated to show the
cctrl will output a new field,
the relative latency value.
The Tungsten Connector will use the value when the
maxAppliedLatency option is used in
the connection string to determine whether to route a
connection to a master or a slave.
For more information, see Section 5.3.1, “Latency or Relative Latency Display”.
Continuent Tungsten can now be configured to effectively isolate data sources for which replication has stopped or exhibits an error condition. See the updated documentation on Section 5.13, “Replicator Fencing” for further information.
For more information, see Section 5.13, “Replicator Fencing”.
The tpm command has been updated to support updated fencing mechanisms.
When performing an update, particularly in environments such as Multi-Site, Multi-Master, the tpm command could fail to update the cluster correctly. This could leave the cluster in a diminished state, or fail to upgrade all the components. The tpm command has been updated as follows:
Issues: TUC-2288, TUC-2292
When changing connector properties, and reloading the configuration, the updated values would not be updated.
When using mysqldump
the connector would fail with an Unsupported
When the option
has been specified, the behavior of the connector for checking
of latency with read/write splitting would not be used, instead
appliedLatency figure would be used
Issues: TUC-2250, TUC-2251
Under some conditions, the manager would shut down the router gateway due to an invalid membership alarm but would not restart the connector. This would cause all new connections to hang indefinitely.