Skip to main content
Tungsten Clustering

Tungsten Clustering 8.0.0

Build: 308
Release Date: 12 Sept 2025

Release 8.0.0 is the first major v8 release and contains a wide range of bug fixes, and improvements.

Additionally, this release marks the first release that will be required for Tungsten Operator and the subsequent deployment of Tungsten Clustering within a Kubernetes environment.

Build 8.0.0-305 was initially released on 28 Apr 2025, and re-released as 8.0.0-308 on 12 Sept 2025

Known issue: replication service misconfiguration
There is a known issue in this release that will result in a misconfiguration of the replication services for both new installations and upgrades, under the following conditions:
  • Composite Active/Active topology, AND
  • Your hostnames contain a dash symbol (-) and/or a mix of UPPER and lower case characters.
All other topologies are unaffected. If the above applies to your installation please use v8.0.2. For any questions or concerns, or if you feel you may already be impacted by this, please contact Continuent Support.

Deprecation Notices (1)

The following features/tools have been deprecated from this release and will be removed in future releases. Any self written scripts that utilise these features should be updated.

Command-line Tools (1)

  • tungsten_health_check and tungsten_provision_thl have been deprecated and will be removed in a future release.
    Issue: CT-2509

Behavior Changes (17)

The following changes 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:

Installation and Deployment (4)

Command-line Tools (9)

  • The tpm cert info command now provides better error messages when a specifiedtypeSpec file does not exist.
    Issue: CT-2530

  • The tpm ask command now returns the appropriate values for keys: stagingdir,stagingpath, staginghost and staginguser.

    Additionally, the tpm ask staging command will return a JSON structure with all values. All values are the same as the output of the tpm query-staging command, just presented differently for easier machine usage.

    Issue: CT-2510
  • A new cli argument has been added (--apiver 8) to allow the tapi command to use APIv8. By default, tapi will continue to use APIv2 against v8 installations, using the--apiver 8 option is experimental and should be used with care. Full APIv8 functionality will be included in tapi in a future release.
    Issue: CT-2456
  • The tpm command now allows hyphens in dataservice names.
    Issue: CT-2453
  • Removed sigtrap module dependency from tungsten_find_orphaned.
    Issue: CT-2451
  • The tungsten_send_diag command has been updated with new security keys and the ability to accept security keys on the CLI.
    Issue: CT-2438
  • New shortcut options are availabe with tprovision
    • --primary and --create-primary as an additional alias for -c
    • -C, --mysqlclone as aliases for -m mysqlclone
    • -D, --mysqldump as aliases for -m mysqldump
    • -R, --rsync as aliases for -m rsync
    • -X, --xtrabackup as aliases for -m xtrabackup
    Issue: CT-2311
  • When provisioning a replica using mysqldump, the database will be set to offline mode until loading is complete to prevent accidental writes during the load.
    Issue: CT-2305
  • Additional validation has been added to tprovision when parallel apply is in use.
    Issue: CT-2275

Connector (1)

Security (1)

  • As of version 7.2.0 onwards, when providing custom keystores, the alias of the mysql certificate must be provided as java-mysql-alias=xxx and must have the same name in both tungsten_keystore andtungsten_connector_keystore.
    Issue: CT-2598

Core Clustering (2)

  • Added protection against misconfigured applications or loadbalancers connecting repeatably to the Manager<>Connector port (11999). Such uncontrolled traffic would affect manager performance over time
    Issue: CT-2411

  • Manager and Replicator now get higher CPU priority (-9 nice value) through systemd configuration file. When not using systemd, we advised to use thesudo renice <pid> command to avoid monitoring and processing pauses during high CPU usage periods.

    Note that this command has to be run as a privileged user, which is why the command cannot be part of the regular manager and replicator scripts

    Issue: CT-2330

Known Issue (3)

The following issues are known within this release but not considered critical, nor impact operation. They will be addressed in a subsequent patch release.

Connector (1)

  • Connector bridge fails to route connections to data source ports other than 13306.

    This is fixed in v8.0.1 and it is advised to NOT use v8.0.0 if your MySQL port is configured to anything other than 13306.

    Issue: CT-2609

Core Clustering (1)

  • If your hostname contains a dash symbol (-) and/or a mix of UPPER and lower case characters, AND you are running a Composite Active/Active topology, then upgrading to or installing this release may cause a misconfiguration of the replication services.
    Issue: CT-2632

Security (1)

  • tungsten_mysql_ssl_setup incorrectly generates self-signed CA certificates on RHEL9 Linux flavors.

    This will be fixed in v7.2.0 and v8.0.1

    Issue: CT-2581

Improvements, new features and functionality (25)

Installation and Deployment (1)

Command-line Tools (12)

  • The tpm ask command will now convert values 0 and false toNo and values 1 and true to Yes as human output when given --human or -n cli args.
    Issue: CT-2559
  • The tpm ini command now handles all new tpm options.
    Issue: CT-2543
  • Added missing help text for the cctrl router command.
    Issue: CT-2500
  • The tpm diag command now gathers the output of the tpm ini check -xcommand as the tpmINICheck call.
    Issue: CT-2499
  • The tpm diag command now gathers the output of cctrl system summary
    Issue: CT-2492
  • A new -z option has been added to tprovision which will enable compression when using the rsync method.
    Issue: CT-2489
  • The tpm cert command will now handle public key files. The command tpm cert gen public will create $CONTINUENT_HOME/generated/tungsten_public.jks from the$CONTINUENT_HOME/share/tungsten_keystore.jks file and thetpm cert list public command will show the contents, etc.
    Issue: CT-2434

  • The tpm ask command now supports the -s|--service option for dsrole, dsstate, trrole and trstate keys.

    The option alias for --short is now -S (capitalized), was previously lower-case.

    Example:

    tpm ask dsrole --service alpha
    Issue: CT-2400
  • The new tpm ini command allows for easy creation, checking and administration of the /etc/tungsten/tungsten.ini configuration file.
    Issue: CT-2366
  • When using the -m rsync option with tprovision, the rsync command now includes the oStrictHostKeyChecking=no options.
    Issue: CT-2348
  • The tapi command is now able to provision a Connector database target (both MySQL Server and PostgreSQL) using a JSON payload or command-line arguments. For more information see Command-Line Tools
    Issue: CT-2306

  • The tpm post-process command has a new argument --statemap which processes property=statemap.* entries in the INI defaults section (only) to update the matching entries in the cluster-home/conf/statemap.properties.defaults file.

    Once done, tpm post-process --statemap will exit without invoking the old functionality.

    Issue: CT-1906

Core Replicator (4)

  • The trepctl perf output has been improved when parallel apply is enabled to show granular statistics per channel.
    Issue: CT-2517

  • A new thl apply command is available which provides the ability to pull/push a range of transactions from source THL to a destination. The command can apply the THL either directly into the destination database (MySQL or PostgreSQL) or it can simply write the THL to the filesystem.

    The destination does not need to be running Tungsten Replicator services for this to be used and provides a way of applying data outside of normal Tungsten operations and can be used to extend backup/recovery operations in some scenarios.

    See "The THL apply Command" for more information.

    Issue: CT-2347
  • A new applying field has been added to the output of trepctl reset.
    ...
    applying               : 3 / 0 (92.86%)
    ...
    In the above example, the applier is processing seqno 3 / fragno 0 and already applied 92.86% (this represents a percentage of rows and statements that were already applied). When parallel apply in enabled, there will be one applying field per channel configured, for example the following shows 2 channels:
    ...
    applying.0             :
    applying.1             : 25 / 0 (92.86%)
    ...
    Issue: CT-2315
  • Replicator now recognizes the new MySQL 8.4 show binary log status syntax (as well asshow master status) and will execute the configured replacement request appropriately.
    Issue: CT-2291

Connector (4)

  • Connector now recognizes the new MySQL 8.4 show replica status syntax (As well asshow slave status) and will run replacement configured request appropriately.
    Issue: CT-2401
  • Fixed a bug where connections properly disconnecting with quit command would get an empty database change request.
    Issue: CT-2395
  • Advanced Listeners can now be accessed from the Connector REST API v8.
    Issue: CT-2329
  • Listeners now support the protocol setting to switch between mysql and postgres dialects.
    Issue: CT-2324

Manager (1)

  • Upgrade of Drools libraries to v7.74.1.Final.
    Issue: CT-2206

Documentation (1)

  • API documentation has been updated to reflect changes to many of the endpoints, including updated examples of expected inputs and outputs.
    Issue: CT-2339

API (2)

  • The api/v8/manager/control/service/<service>/datasource/<datasource>/shun call now checks if the datasource exists before shun. It returns an error if does not exist.
    Issue: CT-2447
  • Added /api/v8/manager/quorum REST API endpoint
    Issue: CT-2281

Bug Fixes (53)

Installation and Deployment (3)

  • tpm flags datasource-log-directory and repl-direct-datasource-log-directory will now use the value of each other as a default if only one is specified
    Issue: CT-2425
  • The tpm update command no longer displays the message"common::diffPasswordsDotStore: No custom source passwords.store file defined - SKIPPING"
    Issue: CT-2406
  • Hyphens are now allowed in service names by tpm.
    Issue: CT-2367

Command-line Tools (29)

  • The tpm cert info command now properly handles all available typeSpecs.
    Issue: CT-2532
  • The tpm policy command now selects the correct service to act upon in Composite clusters.
    Issue: CT-2525
  • The tpm cert aliases --running command now properly handles thetls_passwordstore and jmx_passwordstore typeSpecs.
    Issue: CT-2512
  • Fixes an issue where dsctl set with the -reset option could show warnings when run several times in a row, as shown:

    WARNING: Could not execute query DROP TABLE `tungsten_alpha`.`heartbeat`  : Unknown table 'tungsten_alpha.heartbeat'
    Issue: CT-2502
  • router invalid completion arguments have been removed.
    Issue: CT-2501
  • The tungsten_send_diag command now handles curl and aws s3 errors separately and displays the proper message back.
    Issue: CT-2488
  • The cctrl system summary command now works correctly to display useful information regarding the host on which the command is executed.
    Issue: CT-2486
  • During a tpm uninstall, when skipping data services not managed locally, tpmwill now print a notice rather than a warning, since this is the expected behavior.
    Issue: CT-2479
  • The tpm ask version and tpm ask versions commands now display values.
    Issue: CT-2475
  • tprovision will now correctly handle, and support, SELinux if enabled.
    Issue: CT-2473
  • The cctrl ls command now correctly displays relative applied latency based on the use-relative-latency settings in the INI.
    Issue: CT-2472
  • Fixed an issue where the database could potentially get locked in certain cases when using thersync method with tprovision
    Issue: CT-2470
  • executable-prefix is now applied to the deployall and undeployall script names. For example, whenexecutable-prefix=mm, deployall would be named mm_deployall.
    Issue: CT-2467
  • The tpm keep command is now properly called by tpm uninstall, and a regression in a call to the mysql cli has been fixed as well.
    Issue: CT-2462
  • The tpm update command now properly identifies and removes services with mixed-case service names.
    Issue: CT-2426
  • tpm now properly detects MariaDB default settings.
    Issue: CT-2424
  • The tapi command now accepts non-standard ports on the command line, and also properly accepts a user/password pair on the CLI.
    Issue: CT-2420
  • The tungsten_get_status command now passes the correct number of arguments to theprintf function in various places, preventing "Redundant argument" warnings.
    Issue: CT-2407
  • The tpm delete-service and tpm update commands now correctly removeComposite Active/Active cross-site subservices from cctrl
    Issue: CT-2404
  • The tpm diag command now gathers:
    • tungsten-replicator/log/replicator-api.log
    • tungsten-connector/log/connector-api.log
    • tungsten-manager/log/manager-api.log
    Issue: CT-2397
  • The tapi command now creates proper URL's for these standard endpoints when-C, -M or -R are specified along with one of the following strings: ping, tungstenVersion, createAdminUser,deleteAdminUser, listAdminUsers, rmiSecurity or user.
    Issue: CT-2391
  • The tpm check ports and tpm check ports -c commands are now able to handle replicator-only nodes. By default, it will automatically try to discover the node type, and you may manually specify the node type with-r|--replicator or -c|--cluster.
    Issue: CT-2356
  • The tpm diag command no longer displays a NOTICE for missing optional files.
    Issue: CT-2355
  • The tpm report command now uses the correct API endpoint for Channel 3, Communications from the Connector to the Manager.
    Issue: CT-2354
  • tprovision was incorrectly setting to the MySQL datadir to tungsten group ownership.
    Issue: CT-2322
  • The tpm diag command now properly gathers the uptime command.
    Issue: CT-2319
  • tprovision now supports provisioning from a cluster to stand-alone replicator host
    Issues: CT-2199, CT-2483
  • In certain instances, when provisioning from a primary using tprovision, the remote replication service would not get reset.
    Issue: CT-2138
  • cctrl now validates input correctly for the set policy command
    Issue: CT-678

Core Replicator (3)

  • Fixed an issue where a cluster could display a wrong latency after MySQL and the replicator were stopped and restarted. This would only show under no load conditions.
    Issue: CT-2485
  • The replicator will now properly rollback an XA transaction in case of failure.
    Issue: CT-2410
  • Fixed an issue that would wrongly flag a SQL statement starting with a #comment as bidi_unsafe
    Issue: CT-2405

Connector (7)

  • Connector bridge mode would fail to route connections to data source ports other than 13306.
    Issue: CT-2609
  • The trepctl backup command would fail using xtrabackup.
    Issue: CT-2600
  • Closed a window where the Connector might let writes go to the old primary during a switch with networking issues.
    Issue: CT-2556
  • The tpm delete-service command now sets MAINTENANCE mode before operations, then sets back to AUTOMATIC if it wasAUTOMATIC to start with.
    Issue: CT-2555
  • In active/active setups, no longer using global data service for show slave latency connector intercept.
    Issue: CT-2554
  • Fixed an issue with PHP and caching_sha2_password when using proxy mode: the protocol part "fast path" was not handled properly by the connector, php would hang after reading an unexpected packet. Workaround for this issue (for earlier tungsten versions) is to set property=defaultAuthPlugin=mysql_native_passwordwithin /etc/tungsten/tungsten.ini.
    Issue: CT-2471
  • Fixed an exception when a user.map @default entry would not contain the expected username, password and dataservice parameters.
    Issue: CT-2368

Manager (7)

  • The cctrl commands to set routers into the online and offline state were not functioning. This only affected manual execution of these commands from cctrl and did not affect other operations like switch, failover etc. This issue has been resolved.
    Issue: CT-2526
  • Fixed a race condition that aborted if an error happened when setting MySQL to read-only or read-write. Now the command retries until the MySQL is left in the desired state.
    Issue: CT-2452
  • Fixed a manager state machine unhandled case when receiving a view update while joining the cluster.
    Issue: CT-2449

  • A datasource can now be removed from the manager configuration (including disk) when in MAINTENANCE mode.

    Info
    If the Replicator and Database are still online on the removed host, and the cluster returned to AUTOMATIC mode, the datasource will be recreated. Ensure at least one of the components are also stopped to prevent this.
    Issue: CT-2372
  • There were cases where the state of a connector (router) was shown as UNKNOWN. The issue was resolved by either reporting the reason that the state is unknown i.e. a read timed out etc. or the connector will simply not be shown since it has been disconnected from all managers i.e. either is not running or not reachable due to a network issue.
    Issue: CT-2338

  • Under the conditions of a network outage between a primary site and a relay site, where a failover or switch operation was performed on the primary site, the relay replicator on the relay site was not being correctly updated at the time of the failover/switch.

    This issue has been resolved by detecting whether or not the relay replicator is correctly configured to replicate from the primary datasource on the primary site and, if not, reconfigures the replicator accordingly.

    Issue: CT-2225
  • Improved performance in manager client connection processing. The fix optimizes queue traversal time when searching for or deleting sessions, enhancing the handling of client (specifically manager or cctrl) connections.
    Issue: CT-2201

API (4)

  • Fixed an issue where a component (replicator/connector) stopped through through the API would wrongly indicate "unable to stop".
    Issue: CT-2515
  • The manager REST API /api/v8/manager/cluster/status now correctly displays the connector active/total number of connections.
    Issue: CT-2423
  • Fixed a bug when the /manager/cluster/status REST API call returned unknown for the replicator state.
    Issue: CT-2353
  • Fixed REST API ping method in a composite cluster.
    Issue: CT-2270