Tungsten Replicator 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.

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

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 (13)

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 (2)

• The rest-api-admin-user and rest-api-admin-password TPM properties are now required during a default installation or when explicitly setting the various manager-rest-api=true,connector-rest-api=true, replicator-rest-api=true orrest-apis=true properties.
  Issue: CT-2409
• All Tungsten Components now use log4j version 2.
  Issues: CT-1410, CT-1412

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

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 (1)

• 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 (1)

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

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 (13)

Command-line Tools (7)

• 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
• The tpm diag command now gathers the output of the tpm ini check -xcommand as the tpmINICheck call.
  Issue: CT-2499
• 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
• When using the -m rsync option with tprovision, the rsync command now includes the oStrictHostKeyChecking=no options.
  Issue: CT-2348

Core Replicator (5)

• 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
• Introduced a new cloud-install tpm flag that will skip checks for hostname entry in /etc/hosts, allowing smoother installations against cloud based sources or targets such as Amazon Aurora or Google Cloud SQL.
  Issue: CT-2317

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

Bug Fixes (29)

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 (22)

• The tpm cert info command now properly handles all available typeSpecs.
  Issue: CT-2532
• 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
• The tungsten_send_diag command now handles curl and aws s3 errors separately and displays the proper message back.
  Issue: CT-2488
• 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
• 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 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
• 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
• The tpm uninstall command now properly calls the tpm keep command for standalone Tungsten Replicator deployments.
  Issue: CT-2436
• The tpm diag command now correctly connects to an off-host database when run under standalone Tungsten Replicator.
  Issue: CT-2402
• The tpm diag command now gathers:

  • tungsten-replicator/log/replicator-api.log
  Issue: CT-2397
• The tpm update command now properly deletes services when run in a standalone Tungsten Replicator deployment.
  Issue: CT-2383

Core Replicator (2)

• 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

MongoDB Replication (1)

• The replicator now reads the TLS certificate for Mongo Atlas connectivity from the correct keystore (tungsten_truststore.ts)
  Issue: CT-2227

API (1)

• Fixed an issue where a component (replicator/connector) stopped through through the API would wrongly indicate "unable to stop".
  Issue: CT-2515