Tungsten Clustering 6.1.18
This release is past End of Life.
Behavior Changes (4)
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:
Command-line Tools (2)
- The
tungsten_find_orphanedcommand now places the log file in$CONTINUENT_ROOT/service_logs/, not/tmp/Issue: CT-1866 - The
check_tungsten.shscript has been deprecated and no longer maintained. It will be removed in the next patch release and users should use the newertmonitorcommands.Issue: CT-1038
Backup and Restore (1)
From v8 of xtrabackup, the
--stream=taroption was removed, meaning that backups could fail if using the newer release of the Percona toolsIn this release, the backups will now create the backup and then manually compress it
WarningThis change will increase the required disk space for backups to allow the post-backup compression to complete.Issue: CT-1346
Manager (1)
- A failsafe shunned cluster (Caused by a network split) will be auto recovered after the network connection is re-established.Issue: CT-241
Improvements, new features and functionality (8)
Command-line Tools (5)
- The
tungsten_reset_managercommand now supports the ability to simply print out the path or paths to be cleared, one per line via the-lor--listarguments.Issue: CT-1917 - The
tpm ask isBridgeandtpm ask isCoordinatorcommands have been back-ported to v6.Issue: CT-1916 - The
tungsten_generate_haproxy_for_apiandtpm generate-haproxy-for-apicommands no longer call thePerl Data::Dumpermodule.Issue: CT-1915 - The
tungsten_generate_haproxy_for_apiandtpm generate-haproxy-for-apicommands now support using connector hosts in the backend definitions via-c, and extra backend flags to the backend hosts lines using-f.Issue: CT-1909 - Issue: CT-1869
Core Replicator (2)
- The
thl listcommand now displays an approximate field size in bytes for row-based replication.Issue: CT-1847 Added a new feature that enables pausing a replicator stage for some amount of time.
This will pause the given stage for 100 seconds:
trepctl pause -stage thl-to-q -time 100This will pause the stage indefinitely (or until restart, etc) Add -y to avoid the prompt message whether you are sure.
trepctl pause -stage thl-to-qFor the previous 2 commands, running a pause command again will override the previous command.
This will resume the suspended stage (Note that if the stage is not paused, this will have no effect):
trepctl resume -stage thl-to-qNotePlease note this pause does not survive a replicator restart or a service offline/online.Issue: CT-1912
Manager (1)
- Added a new option to TPM
manager-replicator-offline-timeout=[timeout_in_sec]that configures the timeout for the manager to wait until the replicator goes offline. When parallel applier is in use the default timeout was too low, so it’s now user configurable so that it can be adjusted to suit different topologies. If not supplied, the default is 180 (3 minutes). This value should be sufficent in most use cases.Issue: CT-1892
Bug Fixes (14)
Installation and Deployment (1)
- Fixes issues where fixed properties and filters passed to tpm in service stanzas were not being configured correctlyIssue: CT-1463
Command-line Tools (5)
undeployallscript would not properly uninstallsystemdservices on some distributions including amazon linux.Issue: CT-1845replicator start offlinewould not properly pass the offline argument to systemd scripts when installed throughdeployall.Issue: CT-1836- The
tpm diagcommand now behaves properly when the MySQL server is logging to STDERR.Issue: CT-1935 - The
tpm diagcommand now gathers the mysql.log file when SSL is enabled in the serverIssue: CT-1933 - The
tpm diagcommand now passes when the nodename defined in thetungsten.iniis the shortname, and DNS returns the FQDN.Issue: CT-1908
Backup and Restore (4)
- Incremental backups can now be restored more than once.Issue: CT-1850
- Restore will now succeed even if only one incremental backup has been created.Issue: CT-1842
- During the backup/restore process the MySQL certificates are kept intact.Issue: CT-1841
- Fixed an issue where an xtrabackup generated by the replicator would fail to be restored using
trepctl restorecommand.Issue: CT-1575
Core Replicator (4)
- Fixed an issue where filtered events would trigger a useless update to the service trep_commit_seqno table while it is overwritten anyway once the last statement of the applied event is done, just prior to committing the whole block.Issue: CT-1931
- Fixes an issue that prevented geometry datatypes with SRID from being replicated.Issue: CT-1904
- Fixed a possible issue when recovering an old primary as a replica after failover when parallel apply is enabled, that could lead the replica to be unable to come online and require a reprovisioning of this replica.Issue: CT-1890
- Fixes an issue that would prevent a service from going offline at a specified time (
trepctl online -until-time) when parallel apply is enabled. This is a rework of CT-1243.Issue: CT-1684