Tungsten Replicator 7.2.1
Build: 40
Release Date: 3 Feb 2026
Behavior Changes (3)
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 (1)
Command-line Tools (2)
- The
tprovisioncommand now deletes only binary log files listed in the index if the binary log directory is not the same as the mysql data directory.Issue: CT-2631 - The
tprovisioncommand no longer requires the external tooltungsten_get_mysql_datadir. Additionally, the tool has been significantly re-factored for greater stability, performance and functionality.Issue: CT-2597
Improvements, new features and functionality (6)
Installation and Deployment (1)
- New feature:
tungsten.inibackup and history. When enabled with thetpmflagtungsten-ini-backup(false by default), thetpm updatecommand will create a copy of the current INI file (default:/etc/tungsten/tungsten.ini) as$CONTINUENT_ROOT/history/ini/tungsten.ini.YYYYMMDDhhmmssWhen enabled with thetpmflagtungsten-ini-backup, thetpm installcommand will create the first history file and the history subdir, if needed. A new sub-command,tpm ini diffhas been added to compare the current INI file (default:/etc/tungsten/tungsten.ini) and a history file (default: latest history file found), and can also accept--stamp [YYMMDDhhmmss]to specify which file to diff by timestamp. A new sub-command,tpm ini backuphas been added to manually invoke the same copy that thetpm updatecommand does. Added two newtpmconfiguration flags:tungsten-ini-backup(default: false) : Enable thetungsten.iniautomatic backup feature duringtpm installandtpm update
tungsten-ini-history-dir(default:$CONTINUENT_ROOT/history/ini) : Define the location fortungsten.inibackup/history filesIssue: CT-2635
Command-line Tools (4)
- New feature
tpm copy --examplewill show the manual steps taken bytpm copy --initto copy the cluster certificate files to other nodes.Issue: CT-2636 - A new subcommand
tpm ini defaultshas been added to list anytpmoption that actually has a default value defined in thetools/tpm_options_db.txtfile, along with the default value. Additionally, documentation has been updated to show defaults and options for all properties where applicable.Issue: CT-2634 - New tpm flag
--add-sslnow 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-sslIssue: CT-2619 - 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--writeargument would apply the changes to the specified file as well.Issue: CT-2601
Core Replicator (1)
- The replicator now includes real-time performance monitoring to track and identify slow database operations during replication. The feature provides visibility into transaction, event, and statement execution times with configurable thresholds for alerting. For more information on configuring and using this feature, see "The trepctl perflog Command"Issue: CT-2629
Bug Fixes (9)
Installation and Deployment (1)
- Fixed an installation issue when using MariaDB 10.6 with SSL. Previously, this would have failed to install showing an error message like :Unable to connect to the MySQL server using tungsten@db1:13306 (WITH PASSWORD) (MySQLLoginCheck)Issue: CT-2624
Command-line Tools (3)
- The
tprovisioncommand now correctly honors the mountpoint override flag when not using methodrsync.Issue: CT-2651 - The
tpm cert gencommand now works during version upgrades when a security configuration file may not have existed before (passwords.store).Issue: CT-2618 - The
tungsten_send_diagnow uses AWS Signature Version 4 to upload files.Issue: CT-2589
Backup and Restore (1)
- Fixed an edge case issue with xtrabackup running against the primary node and MySQL 8+.NoteGenerally we do not recommend taking backups from primary nodes, and instead backups should be taken from replicas.Issue: CT-2602
Core Replicator (2)
- With recent SELinux changes, MySQL might be unable to read from
/tmp. This directory is used when applying aLOAD DATA INFILEcommand 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/mysqltmpIn this case, mysqltmp is a new subdirectory that should be set with the following permissions and SELinux contextAnother improvement was also added to force the use of LOCAL when applying amkdir -p /tmp/mysqltmpsudo chown -R mysql: /tmp/mysqltmpsudo chmod -R g+r /tmp/mysqltmpsudo semanage fcontext -a -t mysqld_db_t '/tmp/mysqltmp(/.*)?'sudo restorecon -Rv /tmp/mysqltmpLOAD DATA INFILEcommand that was logged using SBR. This is useful when applying to a remote MySQL host. To enable, set the value of thesvc-applier-ldi-use-local=true(default : false)Issue: CT-2603 - Fixed an issue where timestamp columns would not match between source and target when using the
privileged-slave=falseproperty to replicate from a source database using MIXED binlog mode.Issue: CT-2594
Core Clustering (1)
- Recent Java versions changed a default that now enable endpoint identification in secured RMI calls. As a quick turnaround, this release restores the default of disabling identification in various Tungsten scripts.Issue: CT-2666
Security (1)
- Upgraded jackson libraries to latest version to plug potential security holes.Issue: CT-2655