During the initial
setup, choose any predetermined setup type, except
Server only
, to install the latest GA version
of the tools. Use the Custom
setup type to
install an individual tool or specific version. If MySQL Installer is
installed on the host already, use the Add
operation to select and install tools from the MySQL Installer dashboard.
MySQL Installer provides a configuration wizard that can bootstrap an installed instance of MySQL Router 8.0 to direct traffic between MySQL applications and an InnoDB Cluster. When configured, MySQL Router runs as a local Windows service.
You are prompted to configure MySQL Router after the initial installation and when you reconfigure an installed router explicitly. In contrast, the upgrade operation does not require or prompt you to configure the upgraded product.
To configure MySQL Router, do the following:
Set up InnoDB Cluster.
Using MySQL Installer, download and install the MySQL Router application. After the installation finishes, the configuration wizard prompts you for information. Select the Configure MySQL Router for InnoDB Cluster check box to begin the configuration and provide the following configuration values:
Hostname: Host name of the primary (seed) server in the InnoDB Cluster (
localhost
by default).Port: The port number of the primary (seed) server in the InnoDB Cluster (
3306
by default).Management User: An administrative user with root-level privileges.
Password: The password for the management user.
Classic MySQL protocol connections to InnoDB Cluster
Read/Write: Set the first base port number to one that is unused (between 80 and 65532) and the wizard will select the remaining ports for you.
The figure that follows shows an example of the MySQL Router configuration page, with the first base port number specified as 6446 and the remaining ports set by the wizard to 6447, 6448, and 6449.
Click MySQL Installer dashboard.
and then to apply the configuration. Click to close MySQL Installer or return to the
After configuring MySQL Router, the root account exists in the
user table as root@localhost
(local) only,
instead of root@%
(remote). Regardless of
where the router and client are located, even if both are
located on the same host as the seed server, any connection
that passes through the router is viewed by server as being
remote, not local. As a result, a connection made to the
server using the local host (see the example that follows),
does not authenticate.
$> \c root@localhost:6446