VMware recommends that you upgrade to the latest patch available for your current minor, and then upgrade to the latest patch available for the next minor.

For product versions and upgrade paths, see Upgrade Planner.

Because VMware uses the Percona Distribution for MySQL, expect a time lag between Oracle releasing a MySQL patch and VMware releasing VMware SQL with MySQL for Tanzu Application Service containing that patch.

v3.3.0

Release Date: May 23, 2024

Important 3.1.x is the last version of VMware SQL with MySQL for Tanzu Application Service that supports MySQL 5.7. VMware Tanzu for MySQL 3.2.0 and later only support MySQL 8.0. If you are upgrading from an earlier release of VMware Tanzu for MySQL, you must reconfigure any plans previously configured with "MySQL Default Version" of 5.7 to specify 8.0. For more information about upgrading VMware Tanzu for MySQL, see Upgrading VMware SQL with MySQL for Tanzu Application Service.

Changes

This release includes the following changes:

  • Backups and restores use less persistent disk space thanks to a new streaming format (xbstream) and more efficient compression (zstd).
  • Users can restore into a non-empty database.
  • The bootstrap errand self-selects a high-availability cluster instance node on which to run, and no longer requires the --instance flag.

Performance Improvements

With the introduction of a more efficient compression algorithm, backup performance has substantially improved.

Benchmark tests were performed using a publicly available dataset sample of around 150 GiB, using a range of compute configurations (2 core / 2GB, 4 core / 16GB, 8 core / 64GB). Under those parameters, upgrading to version 3.3.0 of VMware SQL with MySQL for Tanzu Application Service resulted in approximately 8X faster backups, and 13% smaller backup artifacts when compared against version 3.2.1. alt-text=MySQL v3.3 improvements, approximately 8 times faster backup, 13% smaller artifact

Important

These estimates are based on a limited set of testing, against an arbitrary dataset using hardware that is representative of a few, but not inclusive of all, use cases and workloads. Real performance will be unique to your specific use case and application.

Breaking Changes

This release includes the following breaking changes:

  • MySQL v5.7 is no longer supported.

    Existing service plans that used a “MySQL Default Version” of “5.7” must be updated. Any service instance created with one of these plans will be updated to MySQL 8.0 when the instance is upgraded. For more information about upgrading VMware Tanzu for MySQL, see Upgrading VMware SQL with MySQL for Tanzu Application Service.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell 1.445*
Percona Server 8.0.36-28
Percona XtraDB cluster 8.0.36-28
Percona XtraBackup 8.0.35-30
adbr-release 0.107.0*
bpm-release 1.2.19*
cf-cli-release 1.63.0*
cf-service-gateway-release 151.0.0*
count-cores-indicator-release 2.0.0
dedicated-mysql-release 0.269.0*
dedicated-mysql-adapter-release 0.467.0*
loggregator-agent-release 7.7.7*
mysql-data-backup-restore-release 3.8.0*
mysql-monitoring-release 10.15.0*
on-demand-service-broker-release 0.46.0*
pxc-release 1.0.28*
routing-release 0.297.0*
service-metrics-release 2.0.37*

* Components marked with an asterisk have been updated

check-circle-line exclamation-circle-line close-line
Scroll to top icon