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.
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
This sets the max delay interval to 2 minutes
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
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
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.
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.
Only one hostname may be specified to tpm connector.
This will prevent the following case: in Composite Active/Active topologies, a given connection starts to write data to a site. The site fails, connection gets reconnected the other site and resumes writing. However the data written to the 1st site has not reached the 2nd site, thus data will not be consistent.
Default is to reject reconnections that follow a write operation (
RW_STRICT connection or SmartScale after a write) and to allow
reconnection after a read operation (
RO_RELAXED or SmartScale after a read)
It is still possible to get the previous behavior (reconnecting transparently connections cross-site) by specifying both
--connector-allow-cross-site-reconnectsForWrites=true, at your own risk