Version End of Life. Not Yet Set
Release 6.1.14 contains a numebr of bug fixes and improvements in the Connectors, and improved handling of systemd integration, additionally XA transaction support is now available.
Improvements, new features and functionality
Tungsten Connector upgrades are now performed with minimal downtime thanks to graceful-shutdown which is now also used when systemd services are installed.
systemd definition file has been updated to prevent unwanted
systemd-driven control of Tungsten components. 2 new settings have been added to definition files:
RemainAfterExit=yes so that systemd won't interfere when the binary is restarted after upgrade
GuessMainPID=no so that the PID can change without confusion inside systemd status
Note that Tungsten has its own service manager (Tanuki service wrapper), systemd is only used for system startup launch of Tungsten components.
After upgrade, the systemd status output might show
"Active: active (exited)".
This is expected since systemd doesn't know the new process to monitor after upgrade
Added tpm support for tuning
maxDelayInterval, used to tune parallel apply.
This sets the max delay interval to 2 minutes
A new command-line tool tungsten_show_processlist has been added. This is a read-only script which will show the output from tungsten show processlist; on all available Connectors.
3 new tpm flags have been added:
These flags can be used to provide a custom systemd configuration that will be used in place of the default, generated one.
This is typically useful when ExecStartPre or ExecStartPost commands are needed
Improved the tpm command's internal logic and introduced a new sub-command, tpm ask.
Improved the check_tungsten_online command:
determine the cluster name by default if none is provided via
always check ls resources even if a dataservice name is provided
add an option to be node-specific, ignoring any status from other nodes
New ddlscan template (
ddl-mysql-staging.vm) available to generate ddl required for
staging tables when deploying the batch applier on a MySQL target.
A new tpm option has been added
This property can be used to pass options directly to the backup binary (Xtrabackup, mariabackup etc). This can be especially useful when the xtrabackup and MySQL versions differ. Generally, MySQL is always ahead of xtrabackup and in some situations xtrabackup will fail if the underlying MySQL patch release does not match the xtrabackup patch release. In this scenario, you could utilise the new option to force xtrabackup to not check the versions, for example:
Multiple options can be passed as a space separated list, for example.
--option1 --option2 --option3
Options passed are specific to the underlying binary and are not validated by Tungsten, therefore you must ensure you only use options that are valid, and check syntax accurately.
A new tpm option has been added
Valid values of either 1 (default) or 2. Setting this value to 2 will change the underlying
innodb_flush_log_at_trx_commit when the node becomes a replica,
resetting it back to 1 if the node is promoted to a primary.
This can improve performance on the apply rates for replicas.
tpm was failing to check application password when single quoted.
--host argument to tpm connector now works properly.
Support for the legacy
--hosts is also included.
Only one hostname may be specified to tpm connector.
The tpm update command now properly parses the
The tungsten_generate_haproxy_for_api and tpm generate-haproxy-for-api command now properly skips sub-services in Composite Active/Active clusters.
The tpm connector --samples command no longer displays the password in any example.
The tpm connector command now works when the application user's password contains double quotes.
The check_tungsten_services -r command no longer takes an extended time to complete when the manager is not running.
With smartscale enabled, when no writes have been issued to the connection, the user session will remain uninitialized. In that situation, we now send reads to replicas.
RO_RELAXED connection is requested and no replica is available to serve
the request, we will now properly reuse the current connection to the primary for executing the request.