We are excited to announce the release of Tungsten Cluster & Tungsten Replicator v7.1.3! This release brings a host of new features, improvements, and bug fixes that enhance the functionality, usability, and stability of our tools. Here’s a comprehensive overview of what’s new and improved in this version.
Behavior Changes
Several changes have been made to Tungsten Cluster & Tungsten Replicator that may impact existing scripts and integration tools. Please review and update any scripts or environments that utilize these tools to ensure compatibility with the new configurations.
For the tpm cert command, it now properly accepts the full file name as a typeSpec and recognizes --basedir and --certsdir as aliases for --dir to specify the target directory for generation. Additionally, it now accepts an absolute path filename as a typeSpec.
The tpm diag command has been updated to check the my_print_defaults command for the MySQL error log value if the direct query SELECT @@GLOBAL.log_error; fails for any reason.
The Connector router module support in the tapi command has been removed. The tapi command now also prints a more understandable URL when specifying the -U option.
The default port in the tpm generate-haproxy-for-api command has been updated to 8201.
Improvements, New Features, and Functionality
This release adds support for Ruby 3.2, ensuring compatibility with the latest Ruby version.
The tpm cert command now has improved help text for clearer guidance.
Two new commands were added. tpm check ini validates all options in a tungsten.ini file before installation, while tpm check ports checks port connectivity for standard Tungsten ports to a specified host.
The tpasswd utility has been enhanced with a new switch -C or --compare.to for password store file comparison to aid in the tpm update process.
In proxy mode, the Tungsten Connector now intercepts kill queries to replace the given thread_id with the underlying database connection thread_id.
Bug Fixes
The tpm update command now properly passes the verbose and debug flags to tpm delete-service.
The tpm report command now correctly displays channel 2 output in Bridge mode.
A regression in tpm cert that prevented BASE_DIR in tungsten.env from being used properly has been fixed. This command now also works correctly with the share/tungsten.env configuration file before installation, and both tpm cert and tpm copy commands now function correctly from the staging directory before Tungsten is installed.
All tpm commands now consistently use the --force and -f arguments.
The zabbix_tungsten_online monitoring tool now properly supports active witnesses.
The check_tungsten_progress command now behaves correctly on witness nodes by exiting with an error message: "CRITICAL: Replicator is not installed on Witness nodes".
Vertica batch applier now properly handles blob containing “\” (backslash) characters.
Conclusion
We are confident that these enhancements and fixes will improve your experience with Tungsten Cluster & Tungsten Replicator. We encourage all users to upgrade to v7.1.3 to take advantage of these new features and improvements.
For a detailed overview of the changes, please visit our official documentation:
Thank you for your continued support and feedback!
Comments
Add new comment