A.1. Tungsten Replicator 8.0.1 GA (6 Oct 2025)

Version End of Life. Not Yet Set

Release 8.0.1 contains a number of bug fixes and improvements.

Behavior Changes

The following changes have been made to Tungsten Replicator 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:

  • Installation and Deployment

    • tpm validate now verifies localhost is defined in /etc/hosts

      Issues: CT-2564

    • tpm now only reads /etc/tungsten/tungsten.ini (no longer looking in $HOME directory and /etc/tungsten.ini)

      For a different path, different filename or multiple files, use the --ini supplying a comma-separated list

      Issues: CT-2612

  • Command-line Tools

    • The tprovision command no longer requires the external tool tungsten_get_mysql_datadir.

      Additionally, the tool has been significantly re-factored for greater stability, performance and functionality.

      Issues: CT-2597

Improvements, new features and functionality

  • Command-line Tools

    • New Feature: tpm ini upgrade --ini {fullpath} will display all changes to the specified INI file that would be performed by the tpm update commands during a version upgrade. Adding the --write argument would apply the changes to the specified file as well.

      Issues: CT-2601

    • New tpm flag --add-ssl now allows to force generate certificates when doing an upgrade. This allows configurations with security disabled to be upgraded to 8.0.1 AND switched to using SSL/TLS communications at the same time. Example:

      shell> tools/tpm update --replace-release --add-ssl

      Issues: CT-2619

  • Monitoring

    • Additional prometheus metrics have been added to the Replicator:

      • tungsten_replicator_service_online_duration_seconds gauge show duration in seconds since the replicator was put online.

      • tungsten_replicator_task_total counter shows statistics by service, stage and task as shown in the following example:

        tungsten_replicator_task_total{service="alpha",stage="q-to-dbms",task_id="1",stat="extract_time",} 250.015

        In this case, this is the extract time spent by the task #1 of the q-to-dbms stage of the alpha service. This is similar to the new trepctl perf output.

      Issues: CT-2514

  • Platform Specific Deployments

    • LTS MariaDB 11.4 is now certified.

      Issues: CT-2337

Bug Fixes

  • Command-line Tools

    • Corrected debug outputs in the Perl tpm framework.

      Issues: CT-2497

    • The tapi command now handles various payload outputs properly.

      Issues: CT-2553

    • The tpm purge-thl command now works properly when run against environments where there are multiple THL files, but the lowest seqno returned exists in the very first THL file.

      Issues: CT-2561

    • The tapi command no longer issues an error when the quantity of command-line arguments is larger than expected.

      Issues: CT-2580

    • The tungsten_send_diag now uses AWS Signature Version 4 to upload files.

      Issues: CT-2589

    • The tpm ini check command now handles a variety of edge cases.

      Issues: CT-2613

    • The tpm cert gen command now works during version upgrades when a security configuration file may not have existed before (passwords.store).

      Issues: CT-2618

  • Backup and Restore

    • Fixed an issue with backups that would fail on hosts whose name contains a '-' (hyphen)

      Issues: CT-2600

    • Fixed an edge case issue with xtrabackup running against the primary node and MySQL 8+.

      Note

      Generally we do not recommend taking backups from primary nodes, and instead backups should be taken from replicas.

      Issues: CT-2602

  • Core Replicator

    • Fixed an issue where timestamp columns would not match between source and target when using the privileged-slave=false property to replicate from a source database using MIXED binlog mode.

      Issues: CT-2594

    • With recent SELinux changes, MySQL might be unable to read from /tmp.

      This directory is used when applying a LOAD DATA INFILE command that was logged using Statement Based Replication (warning : this is considered as unsafe by MySQL).

      In order to avoid any issues, a new setting has been added to indicate a directory to use : svc-applier-ldi-temp-dir=/tmp/mysqltmp

      In this case, mysqltmp is a new subdirectory that should be set with the following permissions and SELinux context

      mkdir -p /tmp/mysqltmp 
      sudo chown -R mysql: /tmp/mysqltmp 
      sudo chmod -R g+r /tmp/mysqltmp 
      sudo semanage fcontext -a -t mysqld_db_t '/tmp/mysqltmp(/.*)?' 
      sudo restorecon -Rv /tmp/mysqltmp

      Another improvement was also added to force the use of LOCAL when applying a LOAD DATA INFILE command that was logged using SBR. This is useful when applying to a remote MySQL host. To enable, set the value of the svc-applier-ldi-use-local=true (default : false)

      Issues: CT-2603

  • Security

    • tungsten_mysql_ssl_setup now properly generates v3 self signed CA certificates for openssl 3 found in RHEL9 Linux flavors.

      Issues: CT-2581

  • API

    • Fixed an issue with log4j2 library embedded in tungsten-api jar which could trigger a warning in log files.

      Issues: CT-2604