Movatterモバイル変換

This section covers the steps necessary to install the correct executables for each type of NDB Cluster node using RPM packages supplied by Oracle.

As an alternative to the method described in this section, Oracle provides MySQL Repositories for NDB Cluster 7.5.6 and later that are compatible with many common Linux distributions. Two repostories, listed here, are available for RPM-based distributions:

RPMs are available for both 32-bit and 64-bit Linux platforms. The filenames for these RPMs use the following pattern:

mysql-cluster-community-data-node-7.5.8-1.el7.x86_64.rpmmysql-cluster-license-component-ver-rev.distro.arch.rpmlicense:= {commercial | community}component: {management-server | data-node | server | client |other—see text}ver:major.minor.releaserev:major[.minor]distro: {el6 | el7 | sles12}arch: {i686 | x86_64}

license indicates whether the RPM is part of a Commercial or Community release of NDB Cluster. In the remainder of this section, we assume for the examples that you are installing a Community release.

Possible values forcomponent, with descriptions, can be found in the following table:

A single bundle (.tar file) of all NDB Cluster RPMs for a given platform and architecture is also available. The name of this file follows the pattern shown here:

mysql-cluster-license-ver-rev.distro.arch.rpm-bundle.tar

You can extract the individual RPM files from this file usingtar or your preferred tool for extracting archives.

The components required to install the three major types of NDB Cluster nodes are given in the following list:

In addition, theclient RPM should be installed to provide thendb_mgm management client on at least one management node. You may also wish to install it on SQL nodes, to havemysql and other MySQL client programs available on these. We discuss installation of nodes by type later in this section.

ver represents the three-partNDB storage engine version number in 7.6.x format, shown as7.6.35 in the examples.rev provides the RPM revision number inmajor.minor format. In the examples shown in this section, we use1.1 for this value.

Thedistro (Linux distribution) is one ofrhel5 (Oracle Linux 5, Red Hat Enterprise Linux 4 and 5),el6 (Oracle Linux 6, Red Hat Enterprise Linux 6),el7 (Oracle Linux 7, Red Hat Enterprise Linux 7), orsles12 (SUSE Enterprise Linux 12). For the examples in this section, we assume that the host runs Oracle Linux 7, Red Hat Enterprise Linux 7, or the equivalent (el7).

arch isi686 for 32-bit RPMs andx86_64 for 64-bit versions. In the examples shown here, we assume a 64-bit platform.

The NDB Cluster version number in the RPM file names (shown here as7.6.35) can vary according to the version which you are actually using.It is very important that all of the Cluster RPMs to be installed have the same version number. The architecture should also be appropriate to the machine on which the RPM is to be installed; in particular, you should keep in mind that 64-bit RPMs (x86_64) cannot be used with 32-bit operating systems (usei686 for the latter).

Data nodes.  On a computer that is to host an NDB Cluster data node it is necessary to install only thedata-node RPM. To do so, copy this RPM to the data node host, and run the following command as the system root user, replacing the name shown for the RPM as necessary to match that of the RPM downloaded from the MySQL website:

$> rpm -Uhv mysql-cluster-community-data-node-7.6.35-1.el7.x86_64.rpm

This installs thendbd andndbmtd data node binaries in/usr/sbin. Either of these can be used to run a data node process on this host.

SQL nodes.  Copy theserver andcommon RPMs to each machine to be used for hosting an NDB Cluster SQL node (server requirescommon). Install theserver RPM by executing the following command as the system root user, replacing the name shown for the RPM as necessary to match the name of the RPM downloaded from the MySQL website:

$> rpm -Uhv mysql-cluster-community-server-7.6.35-1.el7.x86_64.rpm

This installs the MySQL server binary (mysqld), withNDB storage engine support, in the/usr/sbin directory. It also installs all needed MySQL Server support files and useful MySQL server programs, including themysql.server andmysqld_safe startup scripts (in/usr/share/mysql and/usr/bin, respectively). The RPM installer should take care of general configuration issues (such as creating themysql user and group, if needed) automatically.

To administer the SQL node (MySQL server), you should also install theclient RPM, as shown here:

$> rpm -Uhv mysql-cluster-community-client-7.6.35-1.el7.x86_64.rpm

This installs themysql client and other MySQL client programs, such asmysqladmin andmysqldump, to/usr/bin.

Management nodes.  To install the NDB Cluster management server, it is necessary only to use themanagement-server RPM. Copy this RPM to the computer intended to host the management node, and then install it by running the following command as the system root user (replace the name shown for the RPM as necessary to match that of themanagement-server RPM downloaded from the MySQL website):

$> rpm -Uhv mysql-cluster-community-management-server-7.6.35-1.el7.x86_64.rpm

This RPM installs the management server binaryndb_mgmd in the/usr/sbin directory. While this is the only program actually required for running a management node, it is also a good idea to have thendb_mgm NDB Cluster management client available as well. You can obtain this program, as well as otherNDB client programs such asndb_desc andndb_config, by installing theclient RPM as described previously.

SeeSection 2.5.5, “Installing MySQL on Linux Using RPM Packages from Oracle”, for general information about installing MySQL using RPMs supplied by Oracle.

After installing from RPM, you still need to configure the cluster; seeSection 21.3.3, “Initial Configuration of NDB Cluster”, for the relevant information.

SeeSection 2.5.5, “Installing MySQL on Linux Using RPM Packages from Oracle”, for general information about installing MySQL using RPMs supplied by Oracle. SeeSection 21.3.3, “Initial Configuration of NDB Cluster”, for information about required post-installation configuration.