MySQL Cluster Hardware, Software, and Networking Requirements
1520
In this example, where the cluster consists of two node groups of two nodes each, any combination of
at least one node in node group 0 and at least one node in node group 1 is sufficient to keep the cluster
“alive” (indicated by arrows in the diagram). However, if both nodes from either node group fail, the
remaining two nodes are not sufficient (shown by the arrows marked out with an X); in either case, the
cluster has lost an entire partition and so can no longer provide access to a complete set of all cluster
data.
17.1.3. MySQL Cluster Hardware, Software, and Networking Requirements
One of the strengths of MySQL Cluster is that it can be run on commodity hardware and has no
unusual requirements in this regard, other than for large amounts of RAM, due to the fact that all live
data storage is done in memory. (It is possible to reduce this requirement using Disk Data tables, which
are implemented in MySQL 5.1; however, we do not intend to backport this feature to MySQL 5.0.)
Naturally, multiple and faster CPUs will enhance performance. Memory requirements for other MySQL
Cluster processes are relatively small.
The software requirements for MySQL Cluster are also modest. Host operating systems do not require
any unusual modules, services, applications, or configuration to support MySQL Cluster. For supported
operating systems, a standard installation should be sufficient. The MySQL software requirements
are simple: all that is needed is a production release of MySQL 5.0 to have Cluster support. It is not
necessary to compile MySQL yourself merely to be able to use MySQL Cluster. We assume that you
are using the server binary appropriate to your platform, available from the MySQL Cluster software
downloads page at
http://dev.mysql.com/downloads/cluster/
.
For communication between nodes, MySQL Cluster supports TCP/IP networking in any standard
topology, and the minimum expected for each host is a standard 100 Mbps Ethernet card, plus
a switch, hub, or router to provide network connectivity for the cluster as a whole. We strongly
recommend that a MySQL Cluster be run on its own subnet which is not shared with machines not
forming part of the cluster for the following reasons:
• Security.
Communications between MySQL Cluster nodes are not encrypted or shielded in
any way. The only means of protecting transmissions within a MySQL Cluster is to run the cluster
on a protected network. If you intend to use MySQL Cluster for Web applications, the cluster
Содержание 5.0
Страница 1: ...MySQL 5 0 Reference Manual ...
Страница 18: ...xviii ...
Страница 60: ...40 ...
Страница 396: ...376 ...
Страница 578: ...558 ...
Страница 636: ...616 ...
Страница 844: ...824 ...
Страница 1234: ...1214 ...
Страница 1426: ...MySQL Proxy Scripting 1406 The following diagram shows an overview of the classes exposed by MySQL Proxy ...
Страница 1427: ...MySQL Proxy Scripting 1407 ...
Страница 1734: ...1714 ...
Страница 1752: ...1732 ...
Страница 1783: ...Configuring Connector ODBC 1763 ...
Страница 1793: ...Connector ODBC Examples 1773 ...
Страница 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Страница 1842: ...Connector Net Installation 1822 5 Once the installation has been completed click Finish to exit the installer ...
Страница 1864: ...Connector Net Visual Studio Integration 1844 Figure 20 24 Debug Stepping Figure 20 25 Function Stepping 1 of 2 ...
Страница 2850: ...2830 ...
Страница 2854: ...2834 ...
Страница 2928: ...2908 ...
Страница 3000: ...2980 ...
Страница 3122: ...3102 ...
Страница 3126: ...3106 ...
Страница 3174: ...3154 ...
Страница 3232: ...3212 ...