Tungsten Clustering 6.1.21

Build: 13

Release Date: 18 Apr 2023

End of Life Date: 15 Aug 2024

Product End of Life

This release is past End of Life.

Release 6.1.21 contains a number of critical bug fixes and improvements.

Behavior Changes (3)

The following changes 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:

Command-line Tools (3)

• Enabling a custom backup script does not require it to be made the default option anymore, i.e. Settingbackup-method to the custom backup script is not required anymore.
  Issue: CT-2039
• The tungsten_skip_all command (along with alias tungsten_skip_seqno) now shows the full pendingExceptionMessage instead of just pendingError, and the More choice shows the pendingErrorEventId and the pendingError.
  Issue: CT-2030
• No longer using connector graceful-stop together with systemd for upgrades. The underlying change of binary confuses systemd scripts.
  Issue: CT-2113

Known Issue (1)

The following issues are known within this release but not considered critical, nor impact operation. They will be addressed in a subsequent patch release.

Connector (1)

• Note, this bug only affects this release, v6.1.21 Each "SET xxx" statement issued when in proxy mode is being logged. On top of polluting the logs, this extra logging can overwhelm the connector, making it slow to respond and have client threads pile up, up to the point where that could exhaust memory If using Proxy mode, it is advised to NOT install this release, and instead use either version 6.1.20 or 6.1.22
  Issue: CT-2165(ki)

Improvements, new features and functionality (4)

Command-line Tools (2)

• The tpm diag command now captures the output of cluster topology validate
  Issue: CT-2115
• tungsten show processlist could error with a disconnection message listing connections disconnected on the mysql server side.
  Issue: CT-2112

Connector (1)

• Improved smart scale handling of session and global changes so they're all played against connected replica or in case of reconnection. As an example, SET SESSION TRANSACTION READ ONLY will be sent to both primary and replica connections so that a subsequent SELECT @@SESSION.transaction_isolation will return the expected value, even if executed on a replica.
  Issue: CT-1600

Platform Specific Deployments (1)

• ARM 64 bit processor support added (linux aarch64)

  Note

  Note that at time of release, there is currently no xtrabackup binary available for ARM.
  Issues: CT-1619, CT-1620

Bug Fixes (2)

Command-line Tools (2)

• The tpm ask keys command now lists all available keys properly.
  Issue: CT-2041
• The tungsten_get_status command now handles shunned nodes properly.
  Issue: CT-2026