Skip to content

@morgo morgo released this Nov 5, 2019 · 2 commits to release-4.0 since this release

Important Changes

  • Vitess 4.0 no longer supports Statement-Based Replication. Users upgrading will need to switch to Row-Based Replication.
  • V2 Routing is now deprecated and will be removed in a future release. This was an undocumented API that was never officially supported.
  • The default topology server has switched to etcd. ZooKeeper and Consul remain fully supported.
  • Support for InfluxDB as a monitoring backend has been removed. Prometheus is recommended in place.
  • VReplication support is experimental. We are satisfied with the stability and test coverage of this feature but may make changes to the command-line interface based on feedback received. These changes will not follow the Vitess deprecation policy.
  • Prepared statements support is experimental. Support for prepared statements was merged later in the development cycle, and anticipate that there may still be undiscovered edge-cases.
  • The internal representation of topology has been altered between Vitess 3.0 and 4.0. For the most part, it is backward and forwards compatible. The only caveat is to not upgrade to 4.0 while performing horizontal/vertical resharding.
  • The internal Vitess tables VReplication, local_metadata and shard_metadata tables have been modified to support multiple databases in the same mysql instance. This schema change is expected to be forwards and backwards compatible with Vitess 3.0.
  • Support for VStream is experimental. We invite feedback from users before stabilizing this feature in an upcoming release.
  • The included MySQL configuration files bundled with Vitess have been improved. This may lead to cases where a MySQL server started with Vitess 3.0 will not start in Vitess 4.0. Please see the error log for the MySQL server for details.
  • The configuration flags timeout, replication_timeout, gcs_backup_storage_project and lock_timeout have been deprecated and will be removed in the next release of Vitess.
  • The reparenting process has been significantly improved in Vitess 4.0. It is important that you follow the recommended upgrade order for components so that reparents work properly while components are on mixed versions.

Bugs Fixed

Functionality Added or Changed

Build Environment Changes

Assets 6
You can’t perform that action at this time.