Version End of Life. Not Yet Set
Release 6.1.14 contains a number of bugs fixes and improvements to the Batch loader for MySQL. In addition, support for XA transactions is now available.
Added tpm support for tuning
maxDelayInterval, used to tune parallel apply.
This sets the max delay interval to 2 minutes
This flag 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 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
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.
When using the MySQL Batch Applier, you can now choose to drop all deletes by specifying the following tpm property:
This is disabled (false) by default.
This is disabled by default, but can be enabled and configured by using the following two new properties:
In addition, if your tables contain Foreign Keys, you can choose to disable them during the data loading process using the following property: