Movatterモバイル変換

This section describes the basics for planning, installing, configuring, and running an NDB Cluster. Whereas the examples inSection 25.4, “Configuration of NDB Cluster” provide more in-depth information on a variety of clustering options and configuration, the result of following the guidelines and procedures outlined here should be a usable NDB Cluster which meets theminimum requirements for availability and safeguarding of data.

For information about upgrading or downgrading an NDB Cluster between release versions, seeSection 25.3.7, “Upgrading and Downgrading NDB Cluster”.

This section covers hardware and software requirements; networking issues; installation of NDB Cluster; basic configuration issues; starting, stopping, and restarting the cluster; loading of a sample database; and performing queries.

Assumptions.  The following sections make a number of assumptions regarding the cluster's physical and network configuration. These assumptions are discussed in the next few paragraphs.

Cluster nodes and host computers.  The cluster consists of four nodes, each on a separate host computer, and each with a fixed network address on a typical Ethernet network as shown here:

This setup is also shown in the following diagram:

Figure 25.4 NDB Cluster Multi-Computer Setup

Network addressing.  In the interest of simplicity (and reliability), thisHow-To uses only numeric IP addresses. However, if DNS resolution is available on your network, it is possible to use host names in lieu of IP addresses in configuring Cluster. Alternatively, you can use thehosts file (typically/etc/hosts for Linux and other Unix-like operating systems,C:\WINDOWS\system32\drivers\etc\hosts on Windows, or your operating system's equivalent) for providing a means to do host lookup if such is available.

As of NDB 8.0.22,NDB supports IPv6 for connections between all NDB Cluster nodes.

A known issue on Linux platforms when running NDB 8.0.22 and later was that the operating system kernel was required to provide IPv6 support, even when no IPv6 addresses were in use. This issue is fixed in NDB 8.0.34 and later (Bug #33324817, Bug #33870642).

If you are using an affected version and wish to disable support for IPv6 on the system (because you do not plan to use any IPv6 addresses for NDB Cluster nodes), do so after booting the system, like this:

$> sysctl -w net.ipv6.conf.all.disable_ipv6=1$> sysctl -w net.ipv6.conf.default.disable_ipv6=1

(Alternatively, you can add the corresponding lines to/etc/sysctl.conf.) In NDB Cluster 8.0.34 and later, the preceding is not necessary, and you can simply disable IPv6 support in the Linux kernel if you do not want or need it.

In NDB 8.0.21 and earlier releases, all network addresses used for connections to or from data and management nodes must use or be resolvable using IPv4, including addresses used by SQL nodes to contact the other nodes.

Potential hosts file issues.  A common problem when trying to use host names for Cluster nodes arises because of the way in which some operating systems (including some Linux distributions) set up the system's own host name in the/etc/hosts during installation. Consider two machines with the host namesndb1 andndb2, both in thecluster network domain. Red Hat Linux (including some derivatives such as CentOS and Fedora) places the following entries in these machines'/etc/hosts files:

#  ndb1 /etc/hosts:127.0.0.1   ndb1.cluster ndb1 localhost.localdomain localhost

#  ndb2 /etc/hosts:127.0.0.1   ndb2.cluster ndb2 localhost.localdomain localhost

SUSE Linux (including OpenSUSE) places these entries in the machines'/etc/hosts files:

#  ndb1 /etc/hosts:127.0.0.1       localhost127.0.0.2       ndb1.cluster ndb1

#  ndb2 /etc/hosts:127.0.0.1       localhost127.0.0.2       ndb2.cluster ndb2

In both instances,ndb1 routesndb1.cluster to a loopback IP address, but gets a public IP address from DNS forndb2.cluster, whilendb2 routesndb2.cluster to a loopback address and obtains a public address forndb1.cluster. The result is that each data node connects to the management server, but cannot tell when any other data nodes have connected, and so the data nodes appear to hang while starting.

Host computer type.  Each host computer in our installation scenario is an Intel-based desktop PC running a supported operating system installed to disk in a standard configuration, and running no unnecessary services. The core operating system with standard TCP/IP networking capabilities should be sufficient. Also for the sake of simplicity, we also assume that the file systems on all hosts are set up identically. In the event that they are not, you should adapt these instructions accordingly.

Network hardware.  Standard 100 Mbps or 1 gigabit Ethernet cards are installed on each machine, along with the proper drivers for the cards, and that all four hosts are connected through a standard-issue Ethernet networking appliance such as a switch. (All machines should use network cards with the same throughput. That is, all four machines in the cluster should have 100 Mbps cardsor all four machines should have 1 Gbps cards.) NDB Cluster works in a 100 Mbps network; however, gigabit Ethernet provides better performance.

Sample data.  We use theworld database which is available for download from the MySQL website (seehttps://dev.mysql.com/doc/index-other.html). We assume that each machine has sufficient memory for running the operating system, required NDB Cluster processes, and (on the data nodes) storing the database.

For general information about installing MySQL, seeChapter 2,Installing MySQL. For information about installation of NDB Cluster on Linux and other Unix-like operating systems, seeSection 25.3.1, “Installation of NDB Cluster on Linux”. For information about installation of NDB Cluster on Windows operating systems, seeSection 25.3.2, “Installing NDB Cluster on Windows”.

For general information about NDB Cluster hardware, software, and networking requirements, seeSection 25.2.3, “NDB Cluster Hardware, Software, and Networking Requirements”.