Release Notes

Note: In v2.9 and later, MySQL for VMware Tanzu is named VMware Tanzu SQL with MySQL for VMs.

Page last updated:

VMware recommends that you upgrade to the latest version of your current minor line, then upgrade to the latest available version of the new minor line. For example, if you use an older v2.8.x version, upgrade to the latest v2.8.x version before upgrading to the latest v2.9.x version.

For product versions and upgrade paths, see Upgrade Planner.

v2.9.2

Release Date: November 6, 2020

Breaking Change: If you store automated backups in an S3-compatible bucket that requires a path-style URL to address the bucket, then select Force path style access to bucket before upgrading.

This is necessary because the default style for addressing S3-compatible buckets changed between v2.8.x, v2.9.0, and v2.9.1:
• In v2.9.1 and later, the default bucket address style is virtual hosted.
• In v2.9.0, the default bucket address style is path.
• In v2.8.x, the bucket address style is detected automatically.

For how to select Force path style access to bucket, see Upgrading VMware Tanzu SQL with MySQL for VMs.

Features

New features and changes in this release:

  • Multi-Site Replication GA: The Multi-Site Replication feature is officially generally available in this release. There have been no changes to the feature since v2.9.1.
  • Removed Global service instance quota limit: Previously, operators could not set the maximum service instances quota higher than 500 service instances. This upper limit has been removed.
  • Percona Server: Upgraded to v5.7.31-34
  • Percona XtraDB Cluster: Upgraded to v5.7.31-34
    • This Percona XtraDB Cluster version contains a patch for a remote code execution vulnerability, CVE-2020-15180. For more information, see Percona’s blog post.

Known Issues

This release has the following issues:

  • Multi-Site Replication is unsupported for TAS for VMs v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in TAS for VMs v2.6.
  • MySQL Connector/J 8.0.13 and later does not verify TLS connections: If you use MySQL Connector/J 8.0.13 or later with Tanzu SQL for VMs, you must modify the JDBC URL in VCAP_SERVICES to include sslMode=VERIFY_IDENTITY and verifyServerCertificate=true.

    For more information about JDBC URL syntax, see the MySQL documentation. For more information about VCAP_SERVICES, see MySQL Environment Variables.
  • Plan 1 must be active: If you set Plan 1 to Inactive in the VMware Tanzu SQL with MySQL for VMs tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell621.90*
Percona Server5.7.31-34*
Percona XtraDB Cluster5.7.31-34*
Percona XtraBackup2.4.20
mysql-backup-release2.15.0
mysql-monitoring-release9.15.0
pxc-release0.30.0*

* Components marked with an asterisk have been updated

v2.9.1

Release Date: October 29, 2020

Breaking Change: If you store automated backups in an S3-compatible bucket that requires a path-style URL to address the bucket, then select Force path style access to bucket before upgrading.

This is necessary because the default style for addressing S3-compatible buckets changed between v2.8.x, v2.9.0, and v2.9.1:
• In v2.9.1, the default bucket address style is virtual hosted.
• In v2.9.0, the default bucket address style is path.
• In v2.8.x, the bucket address style is detected automatically.

For how to select Force path style access to bucket, see Upgrading VMware Tanzu SQL with MySQL for VMs.

Features

New features and changes in this release:

  • Support for both S3 path-style URLs and virtual hosted-style URLs: Amazon S3 plans to deprecate S3 path-style URLs in favor of virtual hosted-style URLs. However, some S3-compatible buckets from other providers still use path-style URLs. If the S3-compatible bucket that you use for backup storage requires a path-style URL, select Force path style access to bucket in Ops Manager. See Configure Backups in Ops Manager.

    For general information about the deprecation of S3 path-style URLs, see AWS blog posts: Amazon S3 Path Deprecation Plan – The Rest of the Story and the subsequent Update to Amazon S3 Path Deprecation Plan.

  • Support for tuning MySQL full-text search: Developers who want to optimize MySQL’s full-text search to allow for shorter words can set the optimize_for_short_words arbitrary parameter to true. This parameter sets the MySQL innodb_ft_min_token_size server setting to 1. For more information, see Optimize for Short Words in Changing Defaults Using Arbitrary Parameters.

Resolved Issues

This release has the following fixes:

  • Uppercase letters in the service network no longer prevents configuration of Multi-Site Replication: Previously, if you had configured the service network name with uppercase letters in your environment, multi-site replication could not be configured successfully.

  • The cf adbr list-backups command no longer fails to list backups for non-AWS S3-compatible blobstores. For example, the command now supports listing backups in Minio S3-compatible storage.

Known Issues

This release has the following issues:

  • Multi-Site Replication is unsupported for TAS for VMs v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in TAS for VMs v2.6.
  • MySQL Connector/J 8.0.13 and later does not verify TLS connections: If you use MySQL Connector/J 8.0.13 or later with Tanzu SQL for VMs, you must modify the JDBC URL in VCAP_SERVICES to include sslMode=VERIFY_IDENTITY and verifyServerCertificate=true.

    For more information about JDBC URL syntax, see the MySQL documentation. For more information about VCAP_SERVICES, see MySQL Environment Variables.
  • Plan 1 must be active: If you set Plan 1 to Inactive in the VMware Tanzu SQL with MySQL for VMs tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell621.85*
Percona Server5.7.30–33
Percona XtraDB Cluster5.7.30–31.43
Percona XtraBackup2.4.20
mysql-backup-release2.15.0
mysql-monitoring-release9.15.0
pxc-release0.29.0*

* Components marked with an asterisk have been updated

v2.9.0

Release Date: September 14, 2020

Breaking Changes

Breaking changes in this release:

  • Location of backup artifact: Backups are no longer stored in a subdirectory in the storage destination. Instead, they are stored at the root-level.

  • Removed fields from tile configuration: The following properties have been removed from the tile configuration. Remove them from any automation that configures the tile.

    • .properties.backups_selector.s3.enable_email_alerts
    • .properties.backups_selector.scp.enable_email_alerts
    • .properties.backups_selector.gcs.enable_email_alerts
    • .properties.backups_selector.azure.enable_email_alerts
    • .properties.backups_selector.s3.path
    • .properties.backups_selector.azure.path
  • Cron expressions for automated backups are validated: If your cron schedule is invalid in v2.8, the upgrade to v2.9 fails. For information about cron schedules for automated backups, see Configuring Automated Backups.

Features

New features and changes in this release:

  • Improved backup and restore workflow: Operators and developers can use the ApplicationDataBackupRestore (adbr) plugin with the Cloud Foundry Command Line Interface (cf CLI) to back up and restore service instances. For more information, see Backing Up and Restoring VMware Tanzu SQL with MySQL for VMs and Manually Restoring from Backup.

  • VMware strongly recommends that if operators offer an HA cluster plan, they also offer a Multi‑Site Replication plan. To restore an HA cluster service instance from backup, developers need access to a Multi‑Site Replication plan. For more information, see Restore a Service Instance in Backing Up and Restoring VMware Tanzu SQL with MySQL for VMs and Configure Service Plans.

  • A developer can change the backup schedule for an individual service instance using an arbitrary parameter: For more information, see Backup Schedule.

  • Each backup artifact has a unique encryption key: Each backup of any MySQL service instance now uses a unique encryption key.

  • SCP backups use SFTP: When Secure copy protocol (SCP) is configured as the external storage to upload backups, it now relies on SSH File Transfer Protocol (SFTP).

  • All service instances are provisioned with a DNS alias: This DNS alias is used as the hostname in new service keys. Old service keys, which use the DNS address for the hostname, continue to work.

  • The legacy workflow to enable TLS on a service instance has been removed: In the legacy workflow, which was deprecated after MySQL for PCF v2.4, developers had to run cf update-service to enable TLS on each service instance. This workflow is no longer needed because MySQL connectors can use the DNS alias to connect to the service instance over TLS.

Known Issues

This release has the following issues:

  • The cf adbr list-backups command fails to list backups saved in non-AWS S3-compatible blobstores. For example, the command shows an error message if the backups are in Minio S3-compatible storage.
  • Uppercase letters in the service network name blocks Multi-Site Replication setup: BOSH DNS can only resolve lowercase letters. Because the service network name is only used to reference the network configuration in BOSH, change the network name to lowercase letters.
  • Multi-Site Replication is unsupported for TAS for VMs v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in TAS for VMs v2.6.
  • MySQL Connector/J 8.0.13 and later does not verify TLS connections: If you use MySQL Connector/J 8.0.13 or later with Tanzu SQL for VMs, you must modify the JDBC URL in VCAP_SERVICES to include sslMode=VERIFY_IDENTITY and verifyServerCertificate=true.

    For more information about JDBC URL syntax, see the MySQL documentation. For more information about VCAP_SERVICES, see MySQL Environment Variables.
  • Plan 1 must be active: If you set Plan 1 to Inactive in the VMware Tanzu SQL with MySQL for VMs tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell621.78*
Percona Server5.7.30–33
Percona XtraDB Cluster5.7.30–31.43
Percona XtraBackup2.4.20
mysql-backup-release2.15.0
mysql-monitoring-release9.15.0
pxc-release0.28.0

* Components marked with an asterisk have been updated

View Release Notes for Another Version

To view the release notes for another product version, select the version from dropdown at the top of this page.