|
|
| Applications |
| Mailing Lists |
| Miscellaneous |
| Operating Systems |
| Programming |
svn commit - mysqldoc@docsrva: r7624 - in trunk: refman-4.1 refman-5.0 refman-5.1
From: <jon(at)mysql.com>
Date: Fri Aug 31 2007 - 10:08:30 EDT
[ndbd(NDB)] 1 node(s)
+ <formalpara>
+
<programlisting>
shell> <userinput>rpm -Uhv MySQL-server-¤t-version;-0.glibc23.i386.rpm</userinput> </programlisting>
+
<programlisting>
shell> <userinput>mkdir /var/lib/mysql-cluster</userinput> shell> <userinput>cd /var/lib/mysql-cluster</userinput>
[ndbd(NDB)] 1 node(s)
Date: Fri Aug 31 2007 - 10:08:30 EDT
Author: jstephens
Date: 2007-08-31 16:08:26 +0200 (Fri, 31 Aug 2007)
New Revision: 7624
Log:
Get rid of "fake" markup in 5.1 Cluster chapter.
Sync wording, paragraphination (hey, it's a word - I said so!), etc., between 4.1/5.0/5.1 versions.
Modified:
trunk/refman-4.1/mysql-cluster.xml trunk/refman-5.0/mysql-cluster.xml trunk/refman-5.1/mysql-cluster.xml
Modified: trunk/refman-4.1/mysql-cluster.xml
- trunk/refman-4.1/mysql-cluster.xml 2007-08-31 12:32:34 UTC (rev 7623) +++ trunk/refman-4.1/mysql-cluster.xml 2007-08-31 14:08:26 UTC (rev 7624) Changed blocks: 9, Lines Added: 17, Lines Deleted: 15; 4280 bytes
@@ -1120,10 +1120,11 @@
Each MySQL Cluster host computer running data or SQL nodes must
have installed on it a MySQL-max binary. For management nodes,
it is not necessary to install the MySQL server binary, but you
- do have to install the MGM server daemon and client binaries
- (ndb_mgmd and ndb_mgm ,
- respectively). This section covers the steps necessary to
- install the correct binaries for each type of Cluster node.
+ do have to install the MGM server daemon
+ (ndb_mgmd ). It is also a good idea to install
+ the management client (ndb_mgm ) on the
+ management server host. This section covers the steps necessary
+ to install the correct binaries for each type of Cluster node.
@@ -1909,7 +1910,7 @@
<programlisting>
-CREATE TABLE <replaceable>tbl_name</replaceable> ( ... ) ENGINE=NDBCLUSTER;
+CREATE TABLE <replaceable>tbl_name</replaceable> (<replaceable>column_definitions</replaceable>) ENGINE=NDBCLUSTER;
</programlisting>
<para>
@@ -2306,7 +2307,7 @@
</para>
<programlisting>
-shell> <userinput>mysqld &</userinput>
+shell> <userinput>mysqld_safe &</userinput>
</programlisting>
</listitem>
@@ -2567,7 +2568,7 @@
need to specify the path of the ndb_mgmd
and ndbd servers explicitly. (Normally,
these will be found in
- /usr/local/mysql/bin .
+ /usr/local/mysql/bin .)
@@ -3913,11 +3914,14 @@
because it is stored in a 32KB page with 128 byte page
overhead (see below). There is also a small amount wasted
per page due to the fact that each record is stored in
- only one page. The maximum record size is currently 8052
- bytes.
+ only one page.
+ The maximum record size is currently 8052 bytes.
+
+
+
The memory space defined by DataMemory
is also used to store ordered indexes, which use about 10
bytes per record. Each table row is represented in the
@@ -5193,7 +5197,7 @@
example, in the case of a data node containing several
gigabytes of data, a period as long as 10−15 minutes
(that is, 600000 to 1000000 milliseconds) might be
- required to to perform a node restart.
+ required to perform a node restart.
@@ -5465,7 +5469,7 @@
control the write speed, this parameter specifies how many
pages per 100 milliseconds are to be written. In this
context, a page
is defined as 8KB. This
- parameter is specified in units of 80KB per second, so ,
+ parameter is specified in units of 80KB per second, so
setting
NoOfDiskPagesToDiskAfterRestartTUP to a
value of 20 entails writing 1.6MB in
@@ -5812,8 +5816,7 @@
- LogLevelStartup (MySQL Cluster configuration
- parameter)LogLevelStartup
@@ -5832,8 +5835,7 @@
- LogLevelShutdown (MySQL Cluster configuration
- parameter)LogLevelShutdown
Modified: trunk/refman-5.0/mysql-cluster.xml
- trunk/refman-5.0/mysql-cluster.xml 2007-08-31 12:32:34 UTC (rev 7623) +++ trunk/refman-5.0/mysql-cluster.xml 2007-08-31 14:08:26 UTC (rev 7624) Changed blocks: 19, Lines Added: 70, Lines Deleted: 36; 9921 bytes
@@ -1113,12 +1113,13 @@
Each MySQL Cluster host computer running data or SQL nodes must
- have installed on it a MySQL-max binary. For management nodes,
- it is not necessary to install the MySQL server binary, but you
- do have to install the MGM server daemon and client binaries
- (ndb_mgmd and ndb_mgm ,
- respectively). This section covers the steps necessary to
- install the correct binaries for each type of Cluster node.
+ have installed on it a MySQL server binary. For management
+ nodes, it is not necessary to install the MySQL server binary,
+ but you do have to install the MGM server daemon
+ (ndb_mgmd ). It is also a good idea to install
+ the management client (ndb_mgm ) on the
+ management server host. This section covers the steps necessary
+ to install the correct binaries for each type of Cluster node.
@@ -1902,7 +1903,7 @@
<programlisting>
-CREATE TABLE <replaceable>tbl_name</replaceable> ( ... ) ENGINE=NDBCLUSTER;
+CREATE TABLE <replaceable>tbl_name</replaceable> (<replaceable>column_definitions</replaceable>) ENGINE=NDBCLUSTER;
</programlisting>
<para>
@@ -2062,8 +2063,8 @@
databases. (See world database and
its tables have been created on one data node, you need to issue
- the CREATE SCHEMA world statement (beginning
- with MySQL 5.0.2, you may use CREATE SCHEMA
+ the CREATE DATABASE world statement
+ (beginning with MySQL 5.0.2, you may use CREATE SCHEMA
world instead), followed by FLUSH
TABLES on each SQL node in the cluster. This causes
the node to recognize the database and read its table
@@ -2301,7 +2302,7 @@
<programlisting>
-shell> <userinput>mysqld &</userinput>
+shell> <userinput>mysqld_safe &</userinput>
</programlisting>
</listitem>
@@ -2561,7 +2562,7 @@
need to specify the path of the ndb_mgmd
and ndbd servers explicitly. (Normally,
these will be found in
- /usr/local/mysql/bin .
+ /usr/local/mysql/bin .)
@@ -2666,7 +2667,7 @@
<programlisting>
-NDB> <userinput>SHOW</userinput>
+ndb_mgm> <userinput>SHOW</userinput>
Cluster Configuration
[ndbd(NDB)] 1 node(s)
@@ -3885,11 +3886,14 @@
because it is stored in a 32KB page with 128 byte page
overhead (see below). There is also a small amount wasted
per page due to the fact that each record is stored in
- only one page. The maximum record size is currently 8052
- bytes.
+ only one page.
+ The maximum record size is currently 8052 bytes.
+
+
+
The memory space defined by DataMemory
is also used to store ordered indexes, which use about 10
bytes per record. Each table row is represented in the
@@ -4967,9 +4971,9 @@
Beginning with MySQL 5.0.36, this parameter takes one of
- the integer values
- 0 ,1 , or
- 2 , which act as follows:
+ the integer values 0 ,
+ 1 , or 2 , which act
+ as follows:
@@ -5211,7 +5215,7 @@
example, in the case of a data node containing several
gigabytes of data, a period as long as 10−15 minutes
(that is, 600000 to 1000000 milliseconds) might be
- required to to perform a node restart.
+ required to perform a node restart.
@@ -5483,7 +5487,7 @@
control the write speed, this parameter specifies how many
pages per 100 milliseconds are to be written. In this
context, a page
is defined as 8KB. This
- parameter is specified in units of 80KB per second, so ,
+ parameter is specified in units of 80KB per second, so
setting
NoOfDiskPagesToDiskAfterRestartTUP to a
value of 20 entails writing 1.6MB in
@@ -5830,8 +5834,7 @@
- LogLevelStartup (MySQL Cluster configuration
- parameter)LogLevelStartup
@@ -5850,8 +5853,7 @@
- LogLevelShutdown (MySQL Cluster configuration
- parameter)LogLevelShutdown
@@ -5972,6 +5974,26 @@
+ LogLevelCongestion
+
+
+ LogLevelCongestion
+
+
+
+ The reporting level for events generated by congestion.
+ These errors do not cause node failure but are still
+ considered worth reporting.
+
+
+
+ The default level is 0.
+
+
+
+
+
LogLevelInfo
@@ -7408,6 +7430,14 @@
IN
+ LogLevelCongestion integer
+ 0
+ 0
+ 15
+ N
+
+
LogLevelConnection integer
0
@@ -9181,10 +9211,14 @@
ndbd generates a set of log files which
are placed in the directory specified by
DataDir in the
- config.ini configuration file. These
- log files are listed below. Note that
- node_id represents the node's
- unique identifier. For example,
+ config.ini configuration file.
+
+
+
+ These log files are listed below.
+ node_id is the node's unique
+ identifier. Note that node_id
+ represents the node's unique identifier. For example,
ndb_2_error.log is the error log
generated by the data node whose node ID is
2 .
@@ -17134,7 +17168,7 @@
It is now time to install the package in the proper place. In
this example we will place the installation in
/opt/DIS . You most likely need to run the
- following as the system root user.)
+ following as the system root user.
<programlisting>
@@ -17377,7 +17411,7 @@
<formalpara>
- <title>Testing the Setup</title> + <title>Testing the setup</title>
To ensure that SCI sockets are actually being used, you can
@@ -17425,7 +17459,7 @@
<formalpara>
- <title>Starting the Cluster</title> + <title>Starting the cluster</title>
The next step in the process is to start MySQL Cluster. To
@@ -18954,12 +18988,12 @@
DDL operations
- DDL operations are not node failure safe. If a node
- fails while trying to peform one of these (such as
- CREATE TABLE or ALTER
- TABLE ), the data dictionary is locked and no
- further DDL statements can be executed without
- restarting the cluster.
+ DDL operations (such as CREATE
+ TABLE or ALTER TABLE ) are
+ not safe from data node failures. If a data node fails
+ while trying to peform one of these, the data
+ dictionary is locked and no further DDL statements can
+ be executed without restarting the cluster.
Modified: trunk/refman-5.1/mysql-cluster.xml
- trunk/refman-5.1/mysql-cluster.xml 2007-08-31 12:32:34 UTC (rev 7623) +++ trunk/refman-5.1/mysql-cluster.xml 2007-08-31 14:08:26 UTC (rev 7624) Changed blocks: 96, Lines Added: 1690, Lines Deleted: 1251; 144133 bytes
@@ -38,12 +38,18 @@
MySQL Cluster is a high-availability, high-redundancy version of
MySQL adapted for the distributed computing environment. It uses the
NDB Cluster storage engine to enable running
- several MySQL servers in a cluster. For MySQL ¤t-series; this
- storage engine is available in binary releases and in RPMs
- compatible with most modern Linux distributions. (RPMs are not
- available for &mccge-series;.)
+ several MySQL servers in a cluster. This storage engine is available + in MySQL ¤t-series; binary releases and in RPMs compatible + with most modern Linux distributions.
</para>
+</indexterm>+ ++ Binary releases and RPMs are not available for &mccge-series;, + which must be built from source. + +MySQL Cluster available platforms
@@ -87,66 +93,56 @@
information sources
- <para>
- <emphasis role="bold">Additional resources</emphasis>
- </para> + <formalpara>
- <itemizedlist> + <title>Additional resources</title>
- <listitem>
- <para>
- Answers to some commonly asked questions about Cluster may be
- found in the <xref linkend="faqs-mysql-cluster"/>.
- </para>
- </listitem> + <para> + More information may be found in the following places:
- <listitem>
- <para>
- The MySQL Cluster mailing list:
- <ulink url="http://lists.mysql.com/cluster"/>.
- </para>
- </listitem> + <itemizedlist>
- <listitem>
- <para>
- The MySQL Cluster Forum:
- <ulink url="&base-url-forum-list;?25"/>.
- </para>
- </listitem> + <listitem> + <para> + Answers to some commonly asked questions about Cluster may + be found in the <xref linkend="faqs-mysql-cluster"/>. + </para> + </listitem>
- <listitem>
- <para>
- Many MySQL Cluster users and some of the MySQL Cluster
- developers blog about their experiences with Cluster, and make
- feeds of these available through
- <ulink url="http://www.planetmysql.org/">PlanetMySQL</ulink>.
- </para>
- </listitem> + <listitem> + <para> + The MySQL Cluster mailing list: + <ulink url="http://lists.mysql.com/cluster"/>. + </para> + </listitem>
- <listitem>
- <para>
- If you are new to MySQL Cluster, you may find our Developer Zone
- article
- <ulink url="http://dev.mysql.com/tech-resources/articles/mysql-cluster-for-two-servers.html">
- How to set up a MySQL Cluster for two servers</ulink> to be
- helpful.
- </para>
- </listitem> + <listitem> + <para> + The MySQL Cluster Forum: + <ulink url="&base-url-forum-list;?25"/>. + </para> + </listitem>
- </itemizedlist> + <listitem> + <para> + Many MySQL Cluster users and some of the MySQL Cluster + developers blog about their experiences with Cluster, and + make feeds of these available through + <ulink url="http://www.planetmysql.org/">PlanetMySQL</ulink>. + </para> + </listitem>
- <formalpara role="mnmas-kb"> + <listitem> + <para> + If you are new to MySQL Cluster, you may find our Developer + Zone article + <ulink url="http://dev.mysql.com/tech-resources/articles/mysql-cluster-for-two-servers.html"> + How to set up a MySQL Cluster for two servers</ulink> to be + helpful. + </para> + </listitem>
- <title>MySQL Enterprise</title> -
- <para>
- MySQL Enterprise subscribers will find numerous articles about
- MySQL Cluster at
- <ulink url="https://kb.mysql.com/search.php?cat=search&category=33">
- MySQL Cluster Articles</ulink>. Access to the MySQL Knowledge Base
- collection of articles is one of the advantages of subscribing to
- MySQL Enterprise. For more information see
- <ulink url="&base-url-enterprise;advisors.html"/>. + </itemizedlist> </para>
</formalpara>
@@ -325,14 +321,15 @@
node .
-
- Note : In many contexts, the
- term node
is used to indicate a computer, but
- when discussing MySQL Cluster it means a
- process . It is possible to run any number
- of nodes on a single computer, for which we use the term
- cluster host .
-
+
+
+ In many contexts, the term node
is used to
+ indicate a computer, but when discussing MySQL Cluster it
+ means a process . It is possible to run
+ any number of nodes on a single computer, for which we use the
+ term cluster host .
+
+
(However, it should be noted MySQL does not currently support
@@ -400,14 +397,16 @@
</itemizedlist>
- <para>
- <emphasis role="bold">Important</emphasis>: It is not realistic
- to expect to employ a three-node setup in a production
- environment. Such a configuration provides no redundancy; in
- order to benefit from MySQL Cluster's high-availability
- features, you must use multiple data and SQL nodes. The use of
- multiple management nodes is also highly recommended.
- </para> + <important> + <para> + It is not realistic to expect to employ a three-node setup in + a production environment. Such a configuration provides no + redundancy; in order to benefit from MySQL Cluster's + high-availability features, you must use multiple data and SQL + nodes. The use of multiple management nodes is also highly + recommended. + </para> + </important>
For a brief introduction to the relationships between nodes,
@@ -443,24 +442,35 @@
-
- Standard MySQL clients :
- These are no different for MySQL Cluster than they are for
- standard (non-Cluster) MySQL. In other words, MySQL Cluster
- can be accessed from existing MySQL applications written in
- PHP, Perl, C, C++, Java, Python, Ruby, and so on.
-
+
+
+ Standard MySQL clients
+
+
+ These are no different for MySQL Cluster than they are for
+ standard (non-Cluster) MySQL. In other words, MySQL
+ Cluster can be accessed from existing MySQL applications
+ written in PHP, Perl, C, C++, Java, Python, Ruby, and so
+ on.
+
+
+
-
- Management clients : These
- clients connect to the management server and provide
- commands for starting and stopping nodes gracefully,
- starting and stopping message tracing (debug versions only),
- showing node versions and status, starting and stopping
- backups, and so on.
-
+
+
+ Management clients
+
+
+ These clients connect to the management server and provide
+ commands for starting and stopping nodes gracefully,
+ starting and stopping message tracing (debug versions
+ only), showing node versions and status, starting and
+ stopping backups, and so on.
+
+
+
@@ -520,14 +530,19 @@
-
- (Data) Node : An
- ndbd process, which stores a
- replica —that is, a copy of the
- partition (see below) assigned to the
- node group of which the node is a member.
-
+
+ (Data) Node
+
+
+ An ndbd process, which stores a
+ replica —that is, a copy of
+ the partition (see below) assigned
+ to the node group of which the node is a member.
+
+
+
+
Each data node should be located on a separate computer.
While it is also possible to host multiple
@@ -547,28 +562,41 @@
-
- Node Group : A node group
- consists of one or more nodes, and stores partitions, or
- sets of replicas (see next item).
-
+
-
- Note : Currently, all node
- groups in a cluster must have the same number of nodes.
-
+ Node Group
+
+
+ A node group consists of one or more nodes, and stores
+ partitions, or sets of replicas
+ (see next item).
+
+
+
+
+
+
+ All node groups in a cluster must have the same number of
+ nodes.
+
+
-
- Partition : This is a
- portion of the data stored by the cluster. There are as many
- cluster partitions as nodes participating in the cluster.
- Each node is responsible for keeping at least one copy of
- any partitions assigned to it (that is, at least one
- replica) available to the cluster.
-
+
+ Partition
+
+
+ This is a portion of the data stored by the cluster. There
+ are as many cluster partitions as nodes participating in
+ the cluster. Each node is responsible for keeping at least
+ one copy of any partitions assigned to it (that is, at
+ least one replica) available to the cluster.
+
+
+
+
A replica belongs entirely to a single node; a node can (and
usually does) store several replicas.
@@ -576,13 +604,18 @@
-
- Replica : This is a copy of
- a cluster partition. Each node in a node group stores a
- replica. Also sometimes known as a partition
- replica . The number of replicas is equal to the
- number of nodes per node group.
-
+
+
+ Replica
+
+
+ This is a copy of a cluster partition. Each node in a node
+ group stores a replica. Also sometimes known as a
+ partition replica . The number of
+ replicas is equal to the number of nodes per node group.
+
+
+
@@ -1496,14 +1529,16 @@
sample database; and performing queries.
-
- Basic Assumptions
- </para>
+ <formalpara>
- <para>
- This How-To makes the following assumptions:
- </para> + <title>Basic assumptions</title>
++ This How-To makes the following assumptions: + + + +
@@ -1767,33 +1802,45 @@
- - +Security : Communications - between Cluster nodes are not encrypted or shielded in any - way. The only means of protecting transmissions within a - MySQL Cluster is to run your Cluster on a protected network. - If you intend to use MySQL Cluster for Web applications, the - cluster should definitely reside behind your firewall and - not in your network's De-Militarized Zone - (http://compnetworking.about.com/cs/networksecurity/g/bldef_dmz.htm">DMZ ) - or elsewhere. -+ + Security + ++ Communications between Cluster nodes are not encrypted or + shielded in any way. The only means of protecting + transmissions within a MySQL Cluster is to run your + Cluster on a protected network. If you intend to use MySQL + Cluster for Web applications, the cluster should + definitely reside behind your firewall and not in your + network's De-Militarized Zone + ( + +http://compnetworking.about.com/cs/networksecurity/g/bldef_dmz.htm">DMZ ) + or elsewhere. +- - +Efficiency : Setting up a - MySQL Cluster on a private or protected network allows the - cluster to make exclusive use of bandwidth between cluster - hosts. Using a separate switch for your MySQL Cluster not - only helps protect against unauthorized access to Cluster - data, it also ensures that Cluster nodes are shielded from - interference caused by transmissions between other computers - on the network. For enhanced reliability, you can use dual - switches and dual cards to remove the network as a single - point of failure; many device drivers support failover for - such communication links. -+ + Efficiency + ++ Setting up a MySQL Cluster on a private or protected + network allows the cluster to make exclusive use of + bandwidth between cluster hosts. Using a separate switch + for your MySQL Cluster not only helps protect against + unauthorized access to Cluster data, it also ensures that + Cluster nodes are shielded from interference caused by + transmissions between other computers on the network. For + enhanced reliability, you can use dual switches and dual + cards to remove the network as a single point of failure; + many device drivers support failover for such + communication links. + + +
@@ -1936,11 +1983,13 @@
&mccge-warning-end-cluster; -- +Note : After completing the - installation, do not yet start any of the binaries. We show you - how to do so following the configuration of all nodes. -+ + After completing the installation, do not yet start any of the + binaries. We show you how to do so following the configuration + of all nodes. + +Data and SQL Node Installation —
@@ -2070,19 +2119,20 @@
&mccge-warning-unsupported-begin; -- +SQL Node Installation — RPM - Files -- - On each machine to be used for hosting a cluster SQL node, - install the MySQL 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 - AB web site: - +SQL node installation — RPM files ++ On each machine to be used for hosting a cluster SQL node, + install the MySQL 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 AB web site: + + +
+
<programlisting>
shell> <userinput>rpm -Uhv MySQL-server-¤t-version;-0.glibc23.i386.rpm</userinput> </programlisting>
@@ -2345,30 +2395,33 @@
A
, data node B
, and the SQL node.
-
- Important : Once you have
- started a mysqld process with the
- ndbcluster and
- ndb-connectstring parameters in the
- [MYSQLD] section of the
- my.cnf file as shown previously, you cannot
- execute any CREATE TABLE or ALTER
- TABLE statements without having actually started the
- cluster. Otherwise, these statements will fail with an error.
- This is by design .
-
+
+
+ Once you have started a mysqld process with
+ the ndbcluster and
+ ndb-connectstring parameters in the
+ [MYSQLD] in the my.cnf
+ file as shown previously, you cannot execute any
+ CREATE TABLE or ALTER
+ TABLE statements without having actually started the
+ cluster. Otherwise, these statements will fail with an error.
+ This is by design .
+
+
-
- Configuring the Management Node
-
+
-
- The first step in configuring the MGM node is to create the
- directory in which the configuration file can be found and then
- to create the file itself. For example (running as
- root ):
-
+ Configuring the management node
+
+ The first step in configuring the MGM node is to create the
+ directory in which the configuration file can be found and
+ then to create the file itself. For example (running as
+ root ):
+
+
+
+
<programlisting>
shell> <userinput>mkdir /var/lib/mysql-cluster</userinput> shell> <userinput>cd /var/lib/mysql-cluster</userinput>
@@ -2423,12 +2476,13 @@
# purposes such as running ndb_restore)
</programlisting>
- <para>
- (<emphasis role="bold">Note</emphasis>: The
- <literal>world</literal> database can be downloaded from
- <ulink url="&base-url-docs;"/>, where it can be found listed
- under <quote>Examples</quote>.)
- </para> + <note> + <para> + The <literal>world</literal> database can be downloaded from + <ulink url="&base-url-docs;"/>, where it can be found listed + under <quote>Examples</quote>. + </para> + </note>
After all the configuration files have been created and these
@@ -2447,12 +2501,14 @@
-
- Note : The default port for
- Cluster management nodes is 1186; the default port for data
- nodes is 2202. However, the cluster can automatically allocate
- ports for data nodes from those that are already free.
-
+
+
+ The default port for Cluster management nodes is 1186; the
+ default port for data nodes is 2202. However, the cluster can
+ automatically allocate ports for data nodes from those that
+ are already free.
+
+
@@ -2560,13 +2616,14 @@
id=4 (Version: ¤t-version;)
</programlisting>
- <para>
- <emphasis role="bold">Note</emphasis>: The SQL node is
- referenced here as <literal>[mysqld(API)]</literal>. This is
- perfectly normal, and reflects the fact that the
- <command>mysqld</command> process is acting as a cluster API
- node.
- </para> + <note> + <para> + The SQL node is referenced here as + <literal>[mysqld(API)]</literal>. This is perfectly normal, + and reflects the fact that the <command>mysqld</command> + process is acting as a cluster API node. + </para> + </note>
You should now be ready to work with databases, tables, and data
@@ -2634,11 +2691,16 @@
have a primary key. If no primary key is defined by the user
when a table is created, the NDB Cluster
storage engine automatically generates a hidden one.
- (Note : This hidden key
- takes up space just as does any other table index. It is not
- uncommon to encounter problems due to insufficient memory
- for accommodating these automatically created indexes.)
+
+
+
+ This hidden key takes up space just as does any other
+ table index. It is not uncommon to encounter problems due
+ to insufficient memory for accommodating these
+ automatically created indexes.)
+
+
@@ -2769,10 +2831,11 @@
databases. (See world database and
its tables have been created on one data node, you need to issue
- the CREATE SCHEMA world statement on all
- other SQL nodes attached to the cluster. However, once this has
- been done, all of the SQL nodes can see
the
- tables without any further action being required.
+ the CREATE DATABASE world statement (or you
+ may use CREATE SCHEMA world instead),
+ followed by FLUSH TABLES on each SQL node in
+ the cluster. This causes the node to recognize the database and
+ read its table definitions.
@@ -2949,7 +3012,7 @@
To shut down the cluster, enter the following command in a shell
- on the machine hosting the MGM node:
+ on the machine hosting the management node:
<programlisting>
@@ -3295,13 +3358,15 @@
server at localhost on port 1186.
-
- Note : If you have installed
- MySQL from a binary tarball, you will need to specify the path
- of the ndb_mgmd and ndbd
- servers explicitly. (Normally, these will be found in
- /usr/local/mysql/bin .)
-
+
+
+ If you have installed MySQL from a binary tarball, you will
+ need to specify the path of the ndb_mgmd
+ and ndbd servers explicitly. (Normally,
+ these will be found in
+ /usr/local/mysql/bin .)
+
+
Finally, change location to the MySQL data directory (usually
@@ -3404,7 +3469,7 @@
<programlisting>
-NDB> <userinput>SHOW</userinput>
+ndb_mgm> <userinput>SHOW</userinput>
Cluster Configuration
[ndbd(NDB)] 1 node(s)
@@ -3561,18 +3626,20 @@
ndb-connectstring=ndb_mgmd.mysql.com:1186
</programlisting>
- <para>
- <emphasis role="bold">Important</emphasis>: Once you have
- started a <command>mysqld</command> process with the
- <literal>ndbcluster</literal> and
- <literal>ndb-connectstring</literal> parameters in the
- <literal>[MYSQLD]</literal> in the <filename>my.cnf</filename>
- file as shown previously, you cannot execute any
- <literal>CREATE TABLE</literal> or <literal>ALTER
- TABLE</literal> statements without having actually started the
- cluster. Otherwise, these statements will fail with an error.
- <emphasis>This is by design</emphasis>.
- </para> + <important> + <para> + Once you have started a <command>mysqld</command> process + with the <literal>ndbcluster</literal> and + <literal>ndb-connectstring</literal> parameters in the + <literal>[MYSQLD]</literal> in the + <filename>my.cnf</filename> file as shown previously, you + cannot execute any <literal>CREATE TABLE</literal> or + <literal>ALTER TABLE</literal> statements without having + actually started the cluster. Otherwise, these statements + will fail with an error. <emphasis>This is by + design</emphasis>. + </para> + </important>
You may also use a separate [mysql_cluster]
@@ -3994,12 +4061,17 @@
[MGM] can be used as an alias; the two
section names are equivalent. All parameters in the following
list are optional and assume their default values if omitted.
- Note : If neither the
- ExecuteOnComputer nor the
- HostName parameter is present, the default
- value localhost will be assumed for both.
+
+
+ If neither the ExecuteOnComputer nor the
+ HostName parameter is present, the
+ default value localhost will be assumed
+ for both.
+
+
+
@@ -4116,11 +4188,12 @@
or local7 .
-
- Note : Not every
- facility is necessarily supported by every operating
- system.
-
+
+
+ Not every facility is necessarily supported by every
+ operating system.
+
+
<programlisting>
SYSLOG:facility=syslog
@@ -4359,16 +4432,18 @@
Parameter names and values are currently case-sensitive.
-
- Identifying Data Nodes
-
+
-
- The Id value (that is, the data node
- identifier) can be allocated on the command line when the node
- is started or in the configuration file.
-
+ Identifying data nodes
+
+ The Id value (that is, the data node
+ identifier) can be allocated on the command line when the
+ node is started or in the configuration file.
+
+
+
+
@@ -4514,16 +4589,18 @@
value is 4.
-
- Important : The value for
- this parameter must divide evenly into the number of data
- nodes in the cluster. For example, if there are two data
- nodes, then NoOfReplicas must be equal
- to either 1 or 2, since 2/3 and 2/4 both yield fractional
- values; if there are four data nodes, then
- NoOfReplicas must be equal to 1, 2, or
- 4.
-
+
+
+ The value for this parameter must divide evenly into the
+ number of data nodes in the cluster. For example, if
+ there are two data nodes, then
+ NoOfReplicas must be equal to either
+ 1 or 2, since 2/3 and 2/4 both yield fractional values;
+ if there are four data nodes, then
+ NoOfReplicas must be equal to 1, 2,
+ or 4.
+
+
@@ -4555,11 +4632,15 @@
created for metadata, REDO logs, UNDO logs (for Disk Data
tables) and data files are placed. The default is the
directory specified by DataDir .
- Note : This directory must
- exist before the ndbd process is
- initiated.
+
+
+ This directory must exist before the
+ ndbd process is initiated.
+
+
+
The recommended directory hierarchy for MySQL Cluster
includes /var/lib/mysql-cluster ,
@@ -4928,22 +5009,24 @@
actually deleted until the transaction is committed.
-
- Transaction Parameters
-
+
-
- The next three [NDBD] parameters that we
- discuss are important because they affect the number of
- parallel transactions and the sizes of transactions that can
- be handled by the system.
- MaxNoOfConcurrentTransactions sets the
- number of parallel transactions possible in a node.
- MaxNoOfConcurrentOperations sets the number
- of records that can be in update phase or locked
- simultaneously.
-
+ Transaction parameters
+
+ The next three [NDBD] parameters that we
+ discuss are important because they affect the number of
+ parallel transactions and the sizes of transactions that can
+ be handled by the system.
+ MaxNoOfConcurrentTransactions sets the
+ number of parallel transactions possible in a node.
+ MaxNoOfConcurrentOperations sets the
+ number of records that can be in update phase or locked
+ simultaneously.
+
+
+
+
Both of these parameters (especially
MaxNoOfConcurrentOperations ) are likely
@@ -5114,18 +5197,20 @@
</itemizedlist>
- <para id="mysql-cluster-transaction-temporary-storage">
- <emphasis role="bold">Transaction Temporary Storage</emphasis>
- </para> + <formalpara>
- <para>
- The next set of <literal>[NDBD]</literal> parameters is used
- to determine temporary storage when executing a statement that
- is part of a Cluster transaction. All records are released
- when the statement is completed and the cluster is waiting for
- the commit or rollback.
- </para> + <title>Transaction temporary storage</title>
++ The next set of + + +[NDBD] parameters is used + to determine temporary storage when executing a statement + that is part of a Cluster transaction. All records are + released when the statement is completed and the cluster is + waiting for the commit or rollback. +The default values for these parameters are adequate for most situations. However, users with a need to support transactions
@@ -5239,13 +5324,11 @@
</itemizedlist>
- <para id="mysql-cluster-scans-and-buffering">
- <emphasis role="bold">Scans and Buffering</emphasis>
- </para> + <formalpara>
- <itemizedlist> + <title>Scans and buffering</title>
- <para> + <para id="mysql-cluster-scans-and-buffering"> There are additional <literal>[NDBD]</literal> parameters in the <literal>Dblqh</literal> module (in <filename>ndb/src/kernel/blocks/Dblqh/Dblqh.hpp</filename>)