Now Available: Tungsten v6.1.19 Release

We are pleased to announce that Tungsten Clustering and Tungsten Replicator GA Versions 6.1.19 are now available for customers to download!

This release contains a number of minor bug fixes and improvements, especially for customers utilizing parallel replication. We invite you to read the full list of improvements including changes in behavior in the Tungsten v6.1.19 Release Notes:

• Tungsten Clustering v6.1.19 Release Notes
• Tungsten Replicator v6.1.19 Release Notes

Here are a few highlights:

• Improved tungsten show processlist by running underlying commands in parallel (CT-1569)
• The tpm command calls to glob have been improved to be more strict and compliant (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) (CT-1943)
• The tpm ask command has five new variables available:
  • dsrole and dsstate for the current datasource
  • trrole and trstate for the current replicator
  • 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 (CT-1962)
  • A blog post on the new tungsten_get_status command is available here.
• 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 (CT-1921)
• For cross-site subservices, tpm install and tpm update commands now properly support the –thl-ports option (CT-1953)
• The tpm mysql command will now gracefully handle being run on a non-database node (CT-1946)
• Fixed a replicator issue that would leave a transaction uncommitted longer than necessary (CT-1958)
• Fixed an issue where the shard_id stored in the trep_commit_seqno table would show an incorrect shard after processing a skipped event (an event from another channel) (CT-1967)
• 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 (CT-1973)
• The Connector now auto detects default authentication plugin by retrieving MySQL data source variable default_authentication_plugin rather than just using MySQL server version (CT-1926)

Please reach out to Continuent Support via Zendesk or by emailing if you have any questions!