Previously, MySQL Installer ran mysql_upgrade as a secondary step when a server upgrade operation was performed. Now that mysql_upgrade is deprecated, MySQL Installer performs the schema upgrade directly when the server upgrade is executed (see Important server upgrade conditions).
MySQL Installer now supports an easy-to-use configuration setup for production InnoDB clusters on Microsoft Windows, in addition to continued support for sandbox InnoDB clusters. Separate configuration operations enable the creation or expansion of clusters without the use of complex commands or specialized scripts.
For the deployment of a production cluster, MySQL Installer must run on each host inside a local network to install and configure the required server instances in the cluster (see High Availability).
An error in the product manifest prevented the configuration of MySQL 8.0 and 5.7 server instances from finishing successfully. The server instance was installed properly, but it was not configured. (Bug #29611546)
An existing MySQL 5.7 sandbox InnoDB cluster could not be recreated after an upgrade was performed on the base server instance (used to configure the cluster). (Bug #29410843)
A disclaimer was added to the sandbox-configuration process stating that recreating the sandbox cluster will delete the existing data within the cluster. (Bug #29371916)
An error was generated during the reconfigure operation when a server instance, configured as a sandbox InnoDB cluster using the
mysql_native_passwordauthentication plugin initially, was reconfigured as a standalone server using the
mysql_native_passwordauthentication plugin. (Bug #29299204)