A new utility script has been added to the release, tungsten_post_process, which assists with the graceful maintenance of the static cross-site replicator configuration files on disk.

Issues: CT-761

For more information, see The tungsten_post_process Command.

Two new utility scripts have been added to the release to help with setting the Replicator position:

- tungsten_find_position, which assists with locating information in the THL based on the provided MySQL binary log event position and outputs a dsctl set command as output.

- tungsten_find_seqno, which assists with locating information in the THL based on the provided sequence number and outputs a dsctl set command as output.

Issues: CT-934

A new, beta-quality command has been included called prov-sl.sh which is intended to eventually replace the current tungsten_provision_slave script.

Currently, prov-sl.sh supports provisioning Replicas using mysqldump and xtrabackup tools, and is MySQL 8-compatible. 

The prov-sl.sh command is written in Bash, has less dependencies compared to the current version and is meant to fix a number of issues with the current version.

Backups are streamed from source to target so that an intermediate write to disk is not performed, resulting in faster provisioning times.

Logs are written to $CONTINUENT_ROOT/service_logs/prov-sl.log (i.e. /opt/continuent/service_logs/prov-sl.log).

For example, provision a Replica from [source db] using mysqldump (default):

shell> prov-sl.sh -s {source db}

As another example, use xtrabackup for the backup method, with 10 parallel threads (default is 4), and ssh is listening on port 2222:

shell> prov-sl.sh -s {source db} -n xtrabackup -t 10 -p 2222

Issues: CT-614, CT-723, CT-809, CT-855, CT-963

Upgraded the Drizzle driver to support MySQL 8 authentication protocols (SHA256, caching_sha2).

Issues: CT-914, CT-931, CT-966

The Tungsten Stack now supports the new MySQL 8.0 authentication plugins. Both sha256_password and caching_sha2_password (the new default) are supported by the Replicator, Manager and Connector.

More info on these authentication plugins can be found here: https://dev.mysql.com/doc/refman/8.0/en/sha256-pluggable-authentication.html

The Drizzle driver has been updated to support these new authentication methods, and the MySQL Connector/J 8 is also supported.

In order to be fully transparent with the new defaults, when connected to a MySQL 8+ data source, the Connector will advertise caching_sha2_password as the default plugin.

With earlier versions of MySQL (pre-8.0), the previous default mysql_native_password is used by default and advertised to the client applications.

In order to override the default behavior, a new Connector property option for tpm, property=defaultAuthPlugin={autodetect|caching_sha2_password|mysql_native_password}, and is set to autodetect by default.

Note that if property=defaultAuthPlugin is set to caching_sha2_password, the sha256_password authentication is automatically also supported.

Issues: CT-771

When logging is set to debug or trace, the Connector will print individual queries. In the past, advanced logging limited the display size of requests to 256 characters to prevent overwhelming the logs in terms of both space and filesystem I/O.

Some customers need to display more than that, so it is now possible to adjust the size of the statements displayed in debug or trace logging modes. This is handled by a new Connector property option for tpm, property=statement.display.size.in.kb=NNN, which is defined as the maximum query length to display in Kbytes, and now defaults to 1KB.

For example, if the raw query size is 4KB, then a setting of 1KB would simply display the first 1024 bytes of the query and truncate/discard the rest from a logging perspective.

For more information about configuring debug and trace logging, please visit Generating Advanced Diagnostic Information.

Issues: CT-990

When executing mysqldump, all Tungsten tools no longer use the --add-drop-database flag as it will prevent MySQL 8+ from restoring the dump.

Issues: CT-935

Fixed a bug where tpm diag would generate an empty zip file if the hostnames contain hyphens (-) or periods (.)

Issues: CT-1032

Added support for missing charset GB18030 to correct WARN extractor.mysql.MysqlBinlog Unknown charset errors.

Issues: CT-915, CT-932

Now properly extracting the Geometry datatype.

Issues: CT-997

OLD BEHAVIOR: If the Primary data source was not accessible when the Connector started (i.e. connection refused, etc.), the connector would still fully initialize, leading to a running Connector without an accessible data source. This has the side effects of having default configuration values for both wait_timeout and server_version instead of properly auto-detected values based on the MySQL server settings.

NEW BEHAVIOR: The Connector will now wait indefinitely for a Primary to become available before finishing startup.

Issues: CT-930

Introduced a new tpm flag allowing for tuning Connector thread stack size, which can be required in particular cases where large requests are sent as text to a connector configured for automated read/write splitting (smartscale and direct reads).

The setting is commented out by default, leaving the JVM use its own default, generally 1024.

Setting tpm option connector-thread-stack-size={value in kb} will override this value.

Issues: CT-973