A new -c option is now available with some trepctl commands that can be used in conjunction with the -r option to indicate the number of times to refresh before automatically terminating. For example, the following command:

shell> trepctl perf -r 3 -c 10

Will refresh the output every 3 seconds, 10 times.

Issues: CT-679

The trepctl status will now show the last known applied seqno and latency.

This information is stored on disk at regular intervals (10s minimum) so as not to overload the replicator, therefore the value can be shown as slightly old dependant on when the status command was issued.

By default, this feature is disabled. It can be enabled by setting the following parameter in the configuration :

svc-applier-last-applied-write-interval=20

This will write current position to disk every 20 seconds. This information is also exported by the Prometheus exporter.

If the service is online, it will display the current value (the same as appliedLastSeqno and appliedLatency)

shell> trepctl status 
Processing status command... 
NAME VALUE 
---- ----- 
appliedLastEventId : mysql-bin.000017:0000000151329854;70 
appliedLastSeqno : 999 
appliedLatency : 347707.0 
... 
lastKnownAppliedLatency: 347707.0 
lastKnownAppliedSeqno : 999 
...

Issues: CT-1823

The tungsten_merge_logs command now supports the --before TIMESTAMP and --after TIMESTAMP filters

Issues: CT-1869

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.

Issues: CT-1919

The tpm command calls to glob have been improved to be more strict and compliant.

Issues: CT-1940

The tpm ask stages and tpm ask allstages commands have been added to display the Replicator stages for the current node (stages) and the stages for each role (allstages).

Issues: CT-1943

The tpm ask command has five new variables available: dsrole & dsstate for the current datasource, and trrole & trstate for the current replicator, and nodeinfo which displays all 4 of the new variables.

Issues: CT-1944

The tpm report command now prints the hostname and listener ports where available when using the --extra|-x option or the new --ports option.

Issues: CT-1969

A new dsctl option has been added to the thl command, and a new -event option added to thl list

Full details and examples of these new options can be found here

Issues: CT-2012

Added a new feature that enables pausing a replicator stage for some amount of time.

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

Issues: CT-1912

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

Issues: CT-1927

A new replicator role (thl-applier) has been added to allow a replicator service to apply its locally available THL, without pulling from a remote host

Issues: CT-1936

Added a way to configure the maximum number of rows that can be grouped together when applying row based events for multiple insert or delete statements.

For these properties to be in effect, you must ensure that optimize-row-events=true is either explicitly set in your configuration, or not present (since it will be enabled by default)

For example, the following settings will limit the number of inserted or deleted rows applied at once to 10:

optimize-row-events-limit-insert-rows=10 
optimize-row-events-limit-delete-rows=10

The default values if not specified will be 50 for inserts and 100 for deletes. Note that for deletes to be optimized, the affected table MUST have a single column PK.

Issues: CT-1980

A new log file has been added for the REST API, it is as follows:

Issues: CT-1983

ddlscan, dsctl and tungsten_send_diag are now added to the aliases.sh script.

Issues: CT-813

Fixes issues where fixed properties and filters passed to tpm in service stanzas were not being configured correctly

Issues: CT-1463

No longer using Tanuki wrapper functionality to print jvm version, which was creating defunct java processes at startup, now using internal code.

Issues: CT-1876

Running tpm update on a standalone Replicator deployment no longer prints an uninitialized value error.

Issues: CT-1807

Fixes an issue that prevented ddlscan from connecting to MySQL if SSL was enabled.

Issues: CT-1808

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.

Issues: CT-1877

The tpm command now allows any case for section entries (i.e. [alpha_FROM_beta]) in the INI files.

Issues: CT-1879

The tpm diag command now passes when the nodename defined in the tungsten.ini is the shortname, and DNS returns the FQDN.

Issues: CT-1908

The tpm diag command now gathers the mysql.log file when SSL is enabled in the server.

Issues: CT-1920

The tpm command checks for the existence of the mysql command-line client when installing/upgrading. The process will no longer abort with an error on non-MySQL targets such as heterogeneous replicator appliers, or Active-Witness hosts.

Issues: CT-1924, CT-2018

Fixes an issue that prevented dsctl from connecting to MySQL if SSL was enabled.

Issues: CT-1928

The tpm mysql command will now gracefully handle being run on a non-database node.

Issues: CT-1946

The tpm mysql command no longer aborts with an access denied error on CentOS 6.

Issues: CT-1977

Both TungstenAPI and tpasswd now properly update .passwords.store.orig backup file so that proper manipulation of passwords won't trigger tpm update failure

Issues: CT-1981

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.

Issues: CT-1684

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.

Issues: CT-1890

Fixes an issue that prevented geometry datatypes with SRID from being replicated.

Issues: CT-1904

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.

Issues: CT-1931

Fixed an issue where the replicator would hang after applying a DROP TABLE event, that originally failed on the primary, but got logged into the binlog.

Issues: CT-1973

Fixed a parsing issue that would prevent the replicator from correctly detecting a CREATE TABLE statement with START TRANSACTION

Issues: CT-1987

Fixed an issue in the applier to ensure it is not committing too often with a multi-service replicator (active/active for example, more specifically with AWS Aurora, or an unprivileged MySQL, backend).

Issues: CT-2004

Fixed an issue where the dropsqlmodes filter would fail to remove invalid sql modes from a multi-statement event

Issues: CT-1993