Version End of Life. Not Yet Set
Release 7.0.2 will contain a number of bug fies and improvements.
The following changes have been made to Tungsten Cluster and may affect existing scripts and integration tools. Any scripts or environment which make use of these tools should check and update for the new configuration:
repl_svc_extractor_multi_frag_service_detectionis now turned ON by default. Event shards are determined at extraction time. With fragmented events, the shard cannot be determined by only reading the first fragment, but needs to check the last fragment as well. With this setting turned OFF, there is no issue with pipelines that don't need it, i.e. no parallel apply downstream replicas. However, as this is done at extract time, THL contains this information, and adding or changing a replica using parallel apply could introduce issues.
It can be disabled if you see a performance overhead but this should be done with caution. For Aurora<>Aurora Active/Active deployments it is essential that this property be left ON.
-c option is now available with some trepctl commands that can be used in conjunction
-r option to indicate the number of times to refresh before automatically terminating.
For example, the following command:
trepctl perf -r 3 -c 10
Will refresh the output every 3 seconds, 10 times.
The tungsten_merge_logs command now supports the
--before TIMESTAMP and
--after TIMESTAMP filters
Also, tpm ask now supports direct calls to coordinator,
The tungsten_generate_haproxy_for_api and tpm generate-haproxy-for-api commands
now support using connector hosts in the backend definitions via
-c, and extra backend flags to the
backend hosts lines using
The tungsten_generate_haproxy_for_api and tpm generate-haproxy-for-api
commands no longer call the
Perl Data::Dumper module.
The tungsten_reset_manager command now supports the ability to simply print out the path or paths to be cleared,
one per line via the
The tmonitor command now accepts cli args to specify the ports and will auto-configure the ports if they have been changed via the Tungsten configuration.
The tpm command calls to
glob have been improved to be more strict and compliant.
The tpm ask command has five new variables available:
dsstate for the current datasource,
trstate for the current replicator, and
nodeinfo which displays all 4 of the new variables.
A new standalone status script has been added called tungsten_get_status that shows the datasources and replicators for all nodes in all services along with seqno and latency.
This will pause the given stage for 100 seconds.:
trepctl pause -stage thl-to-q -time 100
This will pause the stage indefinitely (or until restart, etc) Add -y to avoid the prompt message whether you are sure.
trepctl pause -stage thl-to-q
For the previous 2 commands, running a pause command again will override the previous command.
This will resume the suspended stage (Note that if the stage is not paused, this will have no effect):
trepctl resume -stage thl-to-q
Please note this pause does not survive a replicator restart or a service offline/online.
Per-service tuning of the replicator thl directory is now possible for multi-service replicator-only installs as well as for clustering. The given value should be the base directory, to which tungsten will add the service name. For example, the following entry in the tungsten.ini:
[alpha] ... ... thl-directory=/drv1/thl ...
Would result in the THL being placed in /drv1/thl/alpha
Update of thl directory is only available when tpm is called from the staging installation directory, NOT from the running directory.
The connector graceful-stop command now supports systemd service manager properly. The connector stop command now takes an optional argument that will make it a graceful stop. If connector stop is run without the parameter, it will stop the connector immediately. If a positive number of seconds is passed, it will wait, at most, this timeout for connections to disconnect (refusing new connections), after which it will force close all connections and shutdown the connector. connector graceful-stop behavior is unchanged: without the parameter, the connector will wait "forever" for connections to disconnect. A positive timeout in seconds can be passed to sever connections after the given delay
Added a new option to TPM
manager-replicator-offline-timeout=<timeout_in_sec> that configures the timeout for
the manager to wait until the replicator goes offline. When parallel applier is in use the default timeout was too low, so it’s now
user configurable so that it can be adjusted to suit different topologies. If not supplied, the default is 180 (3 minutes). This
value should be sufficent in most use cases.
The tungsten_skip_seqno command no longer fails when
-i is specified, and now properly filters using
--filter when there is a long error message.
The tpm command now allows any case for section entries (i.e. [alpha_FROM_beta]) in the INI files.
The tpm diag command now gathers the
mysql.log file when SSL is enabled in the server.
Fixes an issue that prevented dsctl from connecting to MySQL if SSL was enabled.
The tpm mysql command will now gracefully handle being run on a non-database node.
Fixes an issue that would prevent a service from going offline at a specified time (trepctl online -until-time) when parallel apply is enabled. This is a rework of CT-1243.
Fixed a possible issue when recovering an old primary as a replica after failover when parallel apply is enabled, that could lead the replica to be unable to come online and require a reprovisioning of this replica.
Fixed an issue where filtered events would trigger a useless update to the service trep_commit_seqno table while it is overwritten anyway once the last statement of the applied event is done, just prior to committing the whole block.