Release 5.2.0 is a new feature release that contains improvements to the trepctl and thl commands for better understanding of replication state, particularly with larger transactions, and provides support for new appliers in the Tungsten Replicator.
Due to an issue with the manager, timeouts, and the time taken to perform a switch when restarting the replicator, upgrades and switches between different versions of Tungsten Clustering could fail. The timings have been adjust to address the issue.
Tungsten Clustering 5.2.0 is a new feature release that contains a combination of new features, specifically new replicator applier targets:
trepctl qsState: alpha Online for 1172.724s, running for 124280.671s Latency: 0.71s from source DB commit time on thl://ubuntuheterosrc:2112/ into target database 7564.198s since last source commit Sequence: 4860 last applied, 0 transactions behind (0-4860 stored) estimate 0.00s before synchronization
The trepctl perf command provides detailed performance information on the operation and status of the replicator and individual stages. This can be useful to identify where any additional latency or performance issues lie:shell>
trepctl perfStatistics since last put online 1360.141s ago Stage | Seqno | Latency | Events | Extraction | Filtering | Applying | Other | Total remote-to-thl | 4860 | 0.475s | 70 | 116713.145s | 0.000s | 2.920s | 0.000s | 116716.065s Avg time per Event | 1667.331s | 0.000s | 0.000s | 0.042s | 1667.372s thl-to-q | 4860 | 0.527s | 3180 | 113842.933s | 0.011s | 2873.039s | 0.102s | 116716.085s Avg time per Event | 35.800s | 0.000s | 0.000s | 0.903s | 36.703s q-to-dbms | 4860 | 0.536s | 3180 | 112989.667s | 0.010s | 3701.035s | 25.554s | 116716.266s Avg time per Event | 35.531s | 0.000s | 0.008s | 1.164s | 36.703s
A new field has been added to the output of trepctl status -name tasks:timeInCurrentEvent : 6571.462
This shows the time that the replictor has been processing the current event. For a long-running event, it helps to indicate that the replicator is still processing the curent event. Note that this is a just a counter for how low the current event has been running. For a replicator that is idle, this will show the time the replicator has spent both processing the original event and waiting to process the new event.
The thl list has been expanded to provide simple and detailed THL size information so that large transactions can be identified. Using the
-sizesdetaildisplays detailed information about the size of the SQL, number of rows, or both for each stored event. For example:shell>
thl list -sizesSEQ# Frag# Tstamp ... 12 0 2017-06-28 13:21:11.0 Event total: 1 chunks 73 bytes in SQL statements 0 rows 13 0 2017-06-28 13:21:10.0 Event total: 1645 chunks 0 bytes in SQL statements 1645 rows 14 0 2017-06-28 13:21:11.0 Event total: 1 chunks 36 bytes in SQL statements 0 rows
For easier navigation and selection of THL events, the thl has had two further command-line options added,
-lastto select the first and last events in the THL. Both also take an optional number that shows the first N or last N events.
A new command, tungsten_send_diag, has been added that provides a simplified method for sending a tpm diag output automatically through to the support team. The new command uploads the diagnostic information directly in Amazon S3 without requiring a separate upload to Zendesk.
A new command, clean_release_directory has been added to the distribution. This command removes old releases from the installation directory that have been created during either upgrades or configuration updates. The command removes all old entries except the current active one, and the last five entries.
The tungsten_provision_slave command could hang during the execution of an external command which could cause the entire process to fail to complete properly.
When a replicator has been configured a cluster slave, the
masterListenUriwould be blank. This was because a pure cluster-slave configuration did not correctly configure the necessary pipelines.
An auto-refresh option has been added to certain commands within trepctl. By adding the
-roption and the number of seconds to either trepctl status, trepctl qs, or trepctl perf commands. For example, trepctl qs -r 5 would refresh the quick status command every 5 seconds.