Tungsten Clustering 8.0.2
Behavior Changes (2)
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)
tpm validatenow verifies localhost is defined in/etc/hostsIssue: CT-2564
Command-line Tools (1)
- 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
Improvements, new features and functionality (4)
Installation and Deployment (1)
New feature:
tungsten.inibackup and history.When enabled with the
tpmflagtungsten-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 the
tpmflagtungsten-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 new
tpmconfiguration 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 (2)
- 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
Platform Specific Deployments (1)
- This release is now certified with the following OS releases:
- RHEL 10
- Rocky Linux 10
- Oracle Linux 10
Issue: CT-2642
Bug Fixes (8)
Installation and Deployment (3)
The use of the - character in datasource service names is now properly handled.
In versions 7.x of tungsten, the - character, internally, was converted to an _. From v8 onwards the - character is maintained, however this led to an issue where
tpmwould fail during an upgrade as it was unable to correctly identify the service names.If you use the - in your servicenames and you are currently running v7.x, you will need to replace the - with an _ in your
/etc/tungsten/tungsten.inifile and upgrade directly to v8.0.2. If you wish to maintain the - please contact Continuent Support who will assist in the upgrade process.Issue: CT-2640- Fixed an issue where mixed case letters in hostnames combined with a Composite Active/Active topology, would cause the replicators to reconfigure against the wrong tracking schema.Issue: CT-2638
- Fixed an issue where - (hyphens) in hostnames combined with a Composite Active/Active topology, would cause the replicators to reconfigure against the wrong tracking schema.Issue: CT-2632
Command-line Tools (1)
- The
tprovisioncommand now correctly honors the mountpoint override flag when not using methodrsync.Issue: CT-2651
Connector (3)
- Fixed issue introduced by CT-2511 (dual certificate support) where the keystore was reloaded at every new connection.Issue: CT-2652
- Connector configuration files to execute Tungsten-specific
show slave statusrequest now get the right schema to select from.Issue: CT-2639 - Fixed an issue in the Drizzle driver that could cause memory errors when handling large string parameters.Issue: CT-2627
Manager (1)
- If a cluster was idle for more than 15 minutes and a failure occured, the failover would fail to complete.Issue: CT-2637