Oracle 5.0, Reference Manual

Page: 1551 / 3232

MySQL Cluster Installation and Upgrades
1531
information on a variety of clustering options and configuration, the result of following the guidelines
and procedures outlined here should be a usable MySQL Cluster which meets the minimum
requirements for availability and safeguarding of data.
This section covers hardware and software requirements; networking issues; installation of MySQL
Cluster; 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:
Node IP Address
Management node (
mgmd
) 192.168.0.10
SQL node (
mysqld
) 192.168.0.20
Data node "A" (
ndbd
) 192.168.0.30
Data node "B" (
ndbd
) 192.168.0.40
This may be made clearer by the following diagram:
Network addressing. In the interest of simplicity (and reliability), this How-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 the
hosts
file (typically
/
etc/hosts
for Linux and other Unix-like operating systems, or your operating system's equivalent) for
providing a means to do host lookup if such is available.
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 names
ndb1
and
ndb2
, both in the
cluster
network domain. Red Hat Linux (including some