B.3. Continuent Tungsten 2.0.3 GA (1 Aug 2014)
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.
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:
The following issues may affect the operation of Continuent Tungsten
and should be taken into account when deploying or updating to
The default behavior of the manager is to not fence a datasource
for which a replicator has stopped or gone into an error state.
This was implemented to prevent reducing the overall
availability of the deployed service. There are cases and
deployments where clusters should not operate with replicators
in stopped or error states. This could be configure by changing
the following properties to
true according to the
master or slave role requirements:
If they are set to true, the manager should fence the datasource
by setting it to a 'failed' state. When this happens, and the
datasource is a master, failover will occur. If the datasource
is a slave, the datasource will just stay in the failed state
indefinitely or until the replicator is back in the online
state, in which case the datasource will be recovered to online.
At present the setting of these properties are not honored.
Improvements, new features and functionality