2.19. Tungsten Clustering 4.0.0 Not yet released (Not yet released)

Improvements, new features and functionality

  • Command-line Tools

    • The dsctl (in [Continuent Tungsten 4.0 Manual]) command has been added. This enables easy getting, setting, and resetting of the current replication status information stored in the datasource.

      Issues: CONT-34

    • The tpm (in [Continuent Tungsten 4.0 Manual]) command has been updated to correctly configure clusters and replicators to support replication from a cluster directly to a datawarehouse.

      Issues: CONT-51

Bug Fixes

  • Installation and Deployment

    • During an update or upgrade configuration when components are being added or removed, older configuration could remain, leading to services and components being configured even though the service or component had been removed.

      Issues: CONT-155

    • The validation of values supplied to tpm (in [Continuent Tungsten 4.0 Manual]) for the --thl-log-retention (in [Continuent Tungsten 4.0 Manual]) has been updated. The option now requires a single letter suffix values (the first letter of day, hour, minute, seconds) to specify the quantifier for the value. The default value is 5d.

      Issues: CONT-177

    • The validation of values supplied to tpm (in [Continuent Tungsten 4.0 Manual]) for the --svc-applier-block-commit-interval (in [Continuent Tungsten 4.0 Manual]) has been updated. The option now accepts single letter suffix values (the first letter of day, hour, minute, seconds) to specify the quantifier for the value. Values iver 1000 or greater are assumed to be in seconds. The default value is 15s if batch-enabled (in [Continuent Tungsten 4.0 Manual]) is true, or 0 otherwise.

      Issues: CONT-181

    • tpm (in [Continuent Tungsten 4.0 Manual]) has been updated to confirm that row-based replication has been enabled when a heterogeneous cluster has been configured.

      Issues: CONT-193

  • Command-line Tools

    • The tungsten_set_position (in [Continuent Tungsten 4.0 Manual]) command would fail when executed between dataservices if the service names were different.

      Issues: CONT-24

    • Managers are now started in serial per dataservice, rather than started serially globally.

      Issues: CONT-27

  • Core Replicator

    • A RENAME TABLE operation within MySQL would not cause the metadata caches during replication. This could lead to invalid metadata being used during processing and filtering.

      Issues: CONT-158

  • Tungsten Connector

    • The requirement for Oracle MySQL Connector/J to be used as the MySQL JDBC connector has been removed. The JDBC interface now uses the Drizzle driver by default.

      Issues: CONT-48

  • Tungsten Manager

    • The built-in Drools library has been updated to resolve an issue with memory consumption.

      Issues: CONT-28

    • The network connectivity checks using either the echo or ping protocols have been updated, and additional checks are now performed by the tpm (in [Continuent Tungsten 4.0 Manual]) command during installation to ensure that one or other of the methods is available, configuring the apprioriate method during installation. If neither method is confirmed to work, installation will now fail with a warning.

      Issues: CONT-53, CONT-90

    • Concurrent operations within cctrl (in [Continuent Tungsten 4.0 Manual]) could generate an exception.

      Issues: CONT-165

    • Within a composite dataservice, failover would not be triggered if the master site was isolated from the relay.

      Issues: CONT-188