Author: jstephens
Date: 2007-10-31 12:27:01 +0100 (Wed, 31 Oct 2007)
New Revision: 8426
Log:
Changed configuration file section headings to use lower case.
Modified:
trunk/refman-4.1/mysql-cluster-backup.xml
trunk/refman-4.1/mysql-cluster-configuration.xml
trunk/refman-4.1/mysql-cluster-limitations.xml
trunk/refman-4.1/mysql-cluster-multi-computer.xml
trunk/refman-5.0/mysql-cluster-backup.xml
trunk/refman-5.0/mysql-cluster-configuration.xml
trunk/refman-5.0/mysql-cluster-limitations.xml
trunk/refman-5.0/mysql-cluster-multi-computer.xml
trunk/refman-5.1/mysql-cluster-backup.xml
trunk/refman-5.1/mysql-cluster-ccsg-merge-temp.xml
trunk/refman-5.1/mysql-cluster-configuration.xml
trunk/refman-5.1/mysql-cluster-disk-data.xml
trunk/refman-5.1/mysql-cluster-limitations.xml
trunk/refman-5.1/mysql-cluster-multi-computer.xml
trunk/refman-5.1/mysql-cluster-replication.xml
trunk/refman-5.2/mysql-cluster-backup.xml
trunk/refman-5.2/mysql-cluster-configuration.xml
trunk/refman-5.2/mysql-cluster-disk-data.xml
trunk/refman-5.2/mysql-cluster-limitations.xml
trunk/refman-5.2/mysql-cluster-multi-computer.xml
trunk/refman-5.2/mysql-cluster-replication.xml
trunk/refman-6.0/mysql-cluster-backup.xml
trunk/refman-6.0/mysql-cluster-configuration.xml
trunk/refman-6.0/mysql-cluster-disk-data.xml
trunk/refman-6.0/mysql-cluster-limitations.xml
trunk/refman-6.0/mysql-cluster-multi-computer.xml
trunk/refman-6.0/mysql-cluster-replication.xml
Modified: trunk/refman-4.1/mysql-cluster-backup.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster-backup.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-4.1/mysql-cluster-backup.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 4; 1744 bytes
@@ -592,11 +592,11 @@
utility acts as a cluster API node, and so requires a free
connection <quote>slot</quote> to connect to the cluster
management server. This means that there must be at least one
- <literal>[API]</literal> or <literal>[MYSQLD]</literal>
+ <literal>[api]</literal> or <literal>[mysqld]</literal>
section that can be used by it in the cluster
<filename>config.ini</filename> file. It is a good idea to
- keep at least one empty <literal>[API]</literal> or
- <literal>[MYSQLD]</literal> section in
+ keep at least one empty <literal>[api]</literal> or
+ <literal>[mysqld]</literal> section in
<filename>config.ini</filename> that is not being used for a
MySQL server or other application for this reason (see
<xref linkend="mysql-cluster-api-definition"/>).
@@ -686,7 +686,7 @@
parallel, provided that there is a sufficient number of
cluster connections available. That is, when restoring to
multiple nodes in parallel, you must have an
- <literal>[API]</literal> or <literal>[MYSQLD]</literal>
+ <literal>[api]</literal> or <literal>[mysqld]</literal>
section in the cluster <filename>config.ini</filename> file
available for each concurrent <command>ndb_restore</command>
process. However, the data files must always be applied
Modified: trunk/refman-4.1/mysql-cluster-configuration.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster-configuration.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-4.1/mysql-cluster-configuration.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 47, Lines Added: 81, Lines Deleted: 81; 22520 bytes
@@ -178,23 +178,23 @@
# Note: DB, API, and MGM are aliases for NDBD, MYSQLD, and NDB_MGMD
# respectively. DB and API are deprecated and should not be used in new
# installations.
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas= 1
-[MYSQLD DEFAULT]
-[NDB_MGMD DEFAULT]
-[TCP DEFAULT]
+[mysqld default]
+[NDB_MGMD default]
+[tcp default]
-[NDB_MGMD]
+[ndb_mgmd]
HostName= myhost.example.com
-[NDBD]
+[ndbd]
HostName= myhost.example.com
DataDir= /var/lib/mysql-cluster
-[MYSQLD]
-[MYSQLD]
-[MYSQLD]
+[mysqld]
+[mysqld]
+[mysqld]
</programlisting>
<para>
@@ -509,7 +509,7 @@
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>
+ <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
@@ -568,13 +568,13 @@
Default values are defined for most parameters, and can also be
specified in <filename>config.ini</filename>. To create a
default value section, simply add the word
- <literal>DEFAULT</literal> to the section name. For example, an
- <literal>[NDBD]</literal> section contains parameters that apply
+ <literal>default</literal> to the section name. For example, an
+ <literal>[ndbd]</literal> section contains parameters that apply
to a particular data node, whereas an <literal>[NDBD
- DEFAULT]</literal> section contains parameters that apply to all
+ default]</literal> section contains parameters that apply to all
data nodes. Suppose that all data nodes should use the same data
memory size. To configure them all, create an <literal>[NDBD
- DEFAULT]</literal> section that contains a
+ default]</literal> section that contains a
<literal>DataMemory</literal> line to specify the data memory
size.
</para>
@@ -594,22 +594,22 @@
# The first MySQL Server can be started from any host. The second
# can be started only on the host mysqld_5.mysql.com
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas= 2
DataDir= /var/lib/mysql-cluster
-[NDB_MGMD]
+[ndb_mgmd]
Hostname= ndb_mgmd.mysql.com
DataDir= /var/lib/mysql-cluster
-[NDBD]
+[ndbd]
HostName= ndbd_2.mysql.com
-[NDBD]
+[ndbd]
HostName= ndbd_3.mysql.com
-[MYSQLD]
-[MYSQLD]
+[mysqld]
+[mysqld]
HostName= mysqld_5.mysql.com
</programlisting>
@@ -617,7 +617,7 @@
Each node has its own section in the
<filename>config.ini</filename> file. For example, this cluster
has two data nodes, so the preceding configuration file contains
- two <literal>[NDBD]</literal> sections defining these nodes.
+ two <literal>[ndbd]</literal> sections defining these nodes.
</para>
<note>
@@ -644,7 +644,7 @@
<listitem>
<para>
- <literal>[COMPUTER]</literal>: Defines cluster hosts. This
+ <literal>[computer]</literal>: Defines cluster hosts. This
is not required to configure a viable MySQL Cluster, but be
may used as a convenience when setting up a large cluster.
See <xref linkend="mysql-cluster-computer-definition"/>, for
@@ -654,7 +654,7 @@
<listitem>
<para>
- <literal>[NDBD]</literal>: Defines a cluster data node
+ <literal>[ndbd]</literal>: Defines a cluster data node
(<command>ndbd</command> process). See
<xref linkend="mysql-cluster-ndbd-definition"/>, for
details.
@@ -663,7 +663,7 @@
<listitem>
<para>
- <literal>[MYSQLD]</literal>: Defines the cluster's MySQL
+ <literal>[mysqld]</literal>: Defines the cluster's MySQL
server nodes (also called SQL or API nodes). For a
discussion of SQL node configuration, see
<xref linkend="mysql-cluster-api-definition"/>.
@@ -672,7 +672,7 @@
<listitem>
<para>
- <literal>[MGM]</literal> or <literal>[NDB_MGMD]</literal>:
+ <literal>[mgm]</literal> or <literal>[ndb_mgmd]</literal>:
Defines a cluster management server (MGM) node. For
information concerning the configuration of MGM nodes, see
<xref linkend="mysql-cluster-mgm-definition"/>.
@@ -681,10 +681,10 @@
<listitem>
<para>
- <literal>[TCP]</literal>: Defines a TCP/IP connection
+ <literal>[tcp]</literal>: Defines a TCP/IP connection
between cluster nodes, with TCP/IP being the default
- connection protocol. Normally, <literal>[TCP]</literal> or
- <literal>[TCP DEFAULT]</literal> sections are not required
+ connection protocol. Normally, <literal>[tcp]</literal> or
+ <literal>[tcp default]</literal> sections are not required
to set up a MySQL Cluster, as the cluster handles this
automatically; however, it may be necessary in some
situations to override the defaults provided by the cluster.
@@ -698,7 +698,7 @@
<listitem>
<para>
- <literal>[SHM]</literal>: Defines shared-memory connections
+ <literal>[shm]</literal>: Defines shared-memory connections
between nodes. Prior to MySQL 4.1.9, this type of connection
was available only in binaries that were built using the
<option>--with-ndb-shm</option> option. Beginning with MySQL
@@ -711,7 +711,7 @@
<listitem>
<para>
- <literal>[SCI]</literal>:Defines <firstterm>Scalable
+ <literal>[sci]</literal>:Defines <firstterm>Scalable
Coherent Interface</firstterm> connections between cluster
data nodes. Such connections require software which, while
freely available, is not part of the MySQL Cluster
@@ -724,7 +724,7 @@
</itemizedlist>
<para>
- You can define <literal>DEFAULT</literal> values for each
+ You can define <literal>default</literal> values for each
section. As of MySQL 4.1.5, all parameter names are
case-insensitive, which differs from parameters specified in
<filename>my.cnf</filename> or <filename>my.ini</filename>
@@ -891,7 +891,7 @@
</indexterm>
<para>
- The <literal>[COMPUTER]</literal> section has no real
+ The <literal>[computer]</literal> section has no real
significance other than serving as a way to avoid the need of
defining host names for each node in the system. All parameters
mentioned here are required.
@@ -940,8 +940,8 @@
</indexterm>
<para>
- The <literal>[NDB_MGMD]</literal> section is used to configure
- the behavior of the management server. <literal>[MGM]</literal>
+ The <literal>[ndb_mgmd]</literal> section is used to configure
+ the behavior of the management server. <literal>[mgm]</literal>
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.
@@ -985,7 +985,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers defined in a <literal>[COMPUTER]</literal> section
+ computers defined in a <literal>[computer]</literal> section
of the <filename>config.ini</filename> file.
</para>
</listitem>
@@ -1255,7 +1255,7 @@
</indexterm>
<para>
- The <literal>[NDBD]</literal> and [NDBD DEFAULT] sections are
+ The <literal>[ndbd]</literal> and [ndbddefault] sections are
used to configure the behavior of the cluster's data nodes.
There are many parameters which control buffer sizes, pool
sizes, timeouts, and so forth. The only mandatory parameters
@@ -1268,15 +1268,15 @@
<para>
Either <literal>ExecuteOnComputer</literal> or
<literal>HostName</literal>, which must be defined in the
- local <literal>[NDBD]</literal> section.
+ local <literal>[ndbd]</literal> section.
</para>
</listitem>
<listitem>
<para>
The parameter <literal>NoOfReplicas</literal>, which must be
- defined in the [NDBD DEFAULT] section, as it is common to
- all Cluster data nodes.
+ defined in the [ndbddefault] section, as it is common to all
+ Cluster data nodes.
</para>
</listitem>
@@ -1284,12 +1284,12 @@
<para>
Most data node parameters are set in the <literal>[NDBD
- DEFAULT]</literal> section. Only those parameters explicitly
+ default]</literal> section. Only those parameters explicitly
stated as being able to set local values are allowed to be
- changed in the <literal>[NDBD]</literal> section. Where present,
+ changed in the <literal>[ndbd]</literal> section. Where present,
<literal>HostName</literal>, <literal>Id</literal> and
<literal>ExecuteOnComputer</literal> <emphasis>must</emphasis>
- be defined in the local <literal>[NDBD]</literal> section, and
+ be defined in the local <literal>[ndbd]</literal> section, and
not in any other section of <filename>config.ini</filename>. In
other words, settings for these parameters are specific to one
data node.
@@ -1346,7 +1346,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers defined in a <literal>[COMPUTER]</literal>
+ computers defined in a <literal>[computer]</literal>
section.
</para>
</listitem>
@@ -1401,7 +1401,7 @@
<para>
This global parameter can be set only in the <literal>[NDBD
- DEFAULT]</literal> section, and defines the number of
+ default]</literal> section, and defines the number of
replicas for each table stored in the cluster. This
parameter also specifies the size of node groups. A node
group is a set of nodes all storing the same information.
@@ -1525,7 +1525,7 @@
<para>
<literal>DataMemory</literal> and <literal>IndexMemory</literal>
- are <literal>[NDBD]</literal> parameters specifying the size of
+ are <literal>[ndbd]</literal> parameters specifying the size of
memory segments used to store the actual records and their
indexes. In setting values for these, it is important to
understand how <literal>DataMemory</literal> and
@@ -1713,8 +1713,8 @@
<para>
This parameter determines how much memory is allocated for
strings such as table names, and is specified in an
- <literal>[NDBD]</literal> or <literal>[NDBD
- DEFAULT]</literal> section of the
+ <literal>[ndbd]</literal> or <literal>[NDBD
+ default]</literal> section of the
<filename>config.ini</filename> file. A value between
<literal>0</literal> and <literal>100</literal> inclusive is
interpreted as a percent of the maxmimum default value,
@@ -1844,7 +1844,7 @@
<title>Transaction parameters</title>
<para id="mysql-cluster-transaction-parameters">
- The next three <literal>[NDBD]</literal> parameters that we
+ The next three <literal>[ndbd]</literal> 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.
@@ -2028,7 +2028,7 @@
<title>Transaction temporary storage</title>
<para id="mysql-cluster-transaction-temporary-storage">
- The next set of <literal>[NDBD]</literal> parameters is used
+ 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
@@ -2153,7 +2153,7 @@
<title>Scans and buffering</title>
<para id="mysql-cluster-scans-and-buffering">
- There are additional <literal>[NDBD]</literal> parameters in
+ There are additional <literal>[ndbd]</literal> parameters in
the <literal>Dblqh</literal> module (in
<filename>ndb/src/kernel/blocks/Dblqh/Dblqh.hpp</filename>)
that affect reads and updates. These include
@@ -2279,7 +2279,7 @@
<title>Logging and checkpointing</title>
<para id="mysql-cluster-logging-and-checkpointing">
- These <literal>[NDBD]</literal> parameters control log and
+ These <literal>[ndbd]</literal> parameters control log and
checkpoint behavior.
</para>
@@ -2406,7 +2406,7 @@
<title>Metadata objects</title>
<para id="mysql-cluster-metadata-objects">
- The next set of <literal>[NDBD]</literal> parameters defines
+ The next set of <literal>[ndbd]</literal> parameters defines
pool sizes for metadata objects, used to define the maximum
number of attributes, tables, indexes, and trigger objects
used by indexes, events, and replication between clusters.
@@ -2601,7 +2601,7 @@
<para id="mysql-cluster-boolean-parameters">
The behavior of data nodes is also affected by a set of
- <literal>[NDBD]</literal> parameters taking on boolean values.
+ <literal>[ndbd]</literal> parameters taking on boolean values.
These parameters can each be specified as
<literal>TRUE</literal> by setting them equal to
<literal>1</literal> or <literal>Y</literal>, and as
@@ -2720,7 +2720,7 @@
</para>
<para>
- There are a number of <literal>[NDBD]</literal> parameters
+ There are a number of <literal>[ndbd]</literal> parameters
specifying timeouts and intervals between various actions in
Cluster data nodes. Most of the timeout values are specified in
milliseconds. Any exceptions to this are mentioned where
@@ -3235,7 +3235,7 @@
<title>Buffering and logging</title>
<para id="mysql-cluster-buffering-and-logging">
- Several <literal>[NDBD]</literal> configuration parameters
+ Several <literal>[ndbd]</literal> configuration parameters
corresponding to former compile-time parameters were
introduced in MySQL 4.1.5. These enable the advanced user to
have more control over the resources used by node processes
@@ -3601,7 +3601,7 @@
<title>Backup parameters</title>
<para id="mysql-cluster-backup-parameters">
- The <literal>[NDBD]</literal> parameters discussed in this
+ The <literal>[ndbd]</literal> parameters discussed in this
section define memory buffers set aside for execution of
online backups.
</para>
@@ -3804,7 +3804,7 @@
</indexterm>
<para>
- The <literal>[MYSQLD]</literal> and <literal>[API]</literal>
+ The <literal>[mysqld]</literal> and <literal>[api]</literal>
sections in the <filename>config.ini</filename> file define the
behavior of the MySQL servers (SQL nodes) and other applications
(API nodes) used to access cluster data. None of the parameters
@@ -3813,13 +3813,13 @@
</para>
<para>
- Generally speaking, a <literal>[MYSQLD]</literal> section is
+ Generally speaking, a <literal>[mysqld]</literal> section is
used to indicate a MySQL server providing an SQL interface to
- the cluster, and an <literal>[API]</literal> section is used for
+ the cluster, and an <literal>[api]</literal> section is used for
applications other than <command>mysqld</command> processes
accessing cluster data, but the two designations are actually
synonomous; you can, for instance, list parameters for a MySQL
- server acting as an SQL node in an <literal>[API]</literal>
+ server acting as an SQL node in an <literal>[api]</literal>
section.
</para>
@@ -3853,7 +3853,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers (hosts) defined in a <literal>[COMPUTER]</literal>
+ computers (hosts) defined in a <literal>[computer]</literal>
section of the configuration file.
</para>
</listitem>
@@ -4044,7 +4044,7 @@
node and all MySQL server nodes, and between each data node and
the management server. (For one exception to this rule, see
<xref linkend="mysql-cluster-tcp-definition-direct"/>.)
- <literal>[TCP]</literal> sections in the
+ <literal>[tcp]</literal> sections in the
<filename>config.ini</filename> file explicitly define TCP/IP
connections between nodes in the cluster.
</para>
@@ -4058,10 +4058,10 @@
<important>
<para>
- Any <literal>[TCP]</literal> sections in the
+ Any <literal>[tcp]</literal> sections in the
<filename>config.ini</filename> file should be listed last,
following any other sections in the file. This is not required
- for a <literal>[TCP DEFAULT]</literal> section. This is a
+ for a <literal>[tcp default]</literal> section. This is a
known issue with the way in which the
<filename>config.ini</filename> file is read by the cluster
management server.
@@ -4071,7 +4071,7 @@
<para>
It is also possible to change the default values for these
parameters by setting them in the <literal>[TCP
- DEFAULT]</literal> section.
+ default]</literal> section.
</para>
<itemizedlist>
@@ -4083,7 +4083,7 @@
<para>
To identify a connection between two nodes it is necessary
- to provide their node IDs in the <literal>[TCP]</literal>
+ to provide their node IDs in the <literal>[tcp]</literal>
section of the configuration file. These are the same unique
<literal>Id</literal> values for each of these nodes as
described in <xref linkend="mysql-cluster-api-definition"/>.
@@ -4213,7 +4213,7 @@
<para>
Setting up a cluster using direct connections between data nodes
requires specifying explicitly the crossover IP addresses of the
- data nodes so connected in the <literal>[TCP]</literal> section
+ data nodes so connected in the <literal>[tcp]</literal> section
of the cluster <filename>config.ini</filename> file.
</para>
@@ -4230,26 +4230,26 @@
<programlisting>
# Management Server
-[NDB_MGMD]
+[ndb_mgmd]
Id=1
HostName=172.23.72.20
# SQL Node
-[MYSQLD]
+[mysqld]
Id=2
HostName=172.23.72.21
# Data Nodes
-[NDBD]
+[ndbd]
Id=3
HostName=172.23.72.22
-[NDBD]
+[ndbd]
Id=4
HostName=172.23.72.23
# TCP/IP Connections
-[TCP]
+[tcp]
NodeId1=3
NodeId2=4
HostName1=1.1.0.1
@@ -4306,7 +4306,7 @@
where possible. (In previous versions of MySQL Cluster, shared
memory segments functioned only when the <literal>-max</literal>
binary was built using <option>--with-ndb-shm</option>.)
- <literal>[SHM]</literal> sections in the
+ <literal>[shm]</literal> sections in the
<filename>config.ini</filename> file explicitly define
shared-memory connections between nodes in the cluster. When
explicitly defining shared memory as the connection method, it
@@ -4456,7 +4456,7 @@
</indexterm>
<para>
- <literal>[SCI]</literal> sections in the
+ <literal>[sci]</literal> sections in the
<filename>config.ini</filename> file explicitly define SCI
(Scalable Coherent Interface) connections between cluster nodes.
Using SCI transporters in MySQL Cluster is supported only when
@@ -4782,7 +4782,7 @@
</indexterm>
<indexterm>
- <primary><literal>[NDBD]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[ndbd]</literal> (MySQL Cluster)</primary>
</indexterm>
<indexterm>
@@ -4791,7 +4791,7 @@
<para>
The following table provides information about parameters used
- in the <literal>[NDBD]</literal> or
+ in the <literal>[ndbd]</literal> or
<literal>[NDB_DEFAULT]</literal> sections of a
<filename>config.ini</filename> file for configuring MySQL
Cluster data nodes. For detailed descriptions and other
@@ -5391,16 +5391,16 @@
</indexterm>
<indexterm>
- <primary><literal>[NDB_MGMD]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[ndb_mgmd]</literal> (MySQL Cluster)</primary>
</indexterm>
<indexterm>
- <primary><literal>[MGM]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[mgm]</literal> (MySQL Cluster)</primary>
</indexterm>
<para>
The following table provides information about parameters used
- in the <literal>[NDB_MGMD]</literal> or <literal>[MGM]</literal>
+ in the <literal>[ndb_mgmd]</literal> or <literal>[mgm]</literal>
sections of a <filename>config.ini</filename> file for
configuring MySQL Cluster management nodes. For detailed
descriptions and other additional information about each of
@@ -5541,12 +5541,12 @@
</indexterm>
<indexterm>
- <primary><literal>[API]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[api]</literal> (MySQL Cluster)</primary>
</indexterm>
<para>
The following table provides information about parameters used
- in the <literal>[SQL]</literal> and <literal>[API]</literal>
+ in the <literal>[SQL]</literal> and <literal>[api]</literal>
sections of a <filename>config.ini</filename> file for
configuring MySQL Cluster SQL nodes and API nodes. For detailed
descriptions and other additional information about each of
Modified: trunk/refman-4.1/mysql-cluster-limitations.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster-limitations.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-4.1/mysql-cluster-limitations.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 819 bytes
@@ -1421,7 +1421,7 @@
<emphasis>interfaces</emphasis> (such as Ethernet cards) for
a single data node, but these must be bound to the same
address. This also means that it not possible to use more
- than one <literal>[TCP]</literal> section per connection in
+ than one <literal>[tcp]</literal> section per connection in
the <literal>config.ini</literal> file. See
<xref linkend="mysql-cluster-tcp-definition"/>, for more
information.
Modified: trunk/refman-4.1/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster-multi-computer.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-4.1/mysql-cluster-multi-computer.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 5, Lines Added: 10, Lines Deleted: 10; 3134 bytes
@@ -960,12 +960,12 @@
<programlisting>
# Options for mysqld process:
-[MYSQLD]
+[mysqld]
ndbcluster # run NDB storage engine
ndb-connectstring=192.168.0.10 # location of management server
# Options for ndbd process:
-[MYSQL_CLUSTER]
+[mysql_cluster]
ndb-connectstring=192.168.0.10 # location of management server
</programlisting>
@@ -980,7 +980,7 @@
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>
+ <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
@@ -1015,7 +1015,7 @@
<programlisting>
# Options affecting ndbd processes on all data nodes:
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas=2 # Number of replicas
DataMemory=80M # How much memory to allocate for data storage
IndexMemory=18M # How much memory to allocate for index storage
@@ -1025,7 +1025,7 @@
# this example Cluster setup.
# TCP/IP options:
-[TCP DEFAULT]
+[tcp default]
portnumber=2202 # This the default; however, you can use any
# port that is free for all the hosts in cluster
# Note: It is recommended beginning with MySQL 5.0 that
@@ -1033,23 +1033,23 @@
# the default value to be used instead
# Management process options:
-[NDB_MGMD]
+[ndb_mgmd]
hostname=192.168.0.10 # Hostname or IP address of MGM node
datadir=/var/lib/mysql-cluster # Directory for MGM node log files
# Options for data node "A":
-[NDBD]
- # (one [NDBD] section per data node)
+[ndbd]
+ # (one [ndbd] section per data node)
hostname=192.168.0.30 # Hostname or IP address
datadir=/usr/local/mysql/data # Directory for this data node's data files
# Options for data node "B":
-[NDBD]
+[ndbd]
hostname=192.168.0.40 # Hostname or IP address
datadir=/usr/local/mysql/data # Directory for this data node's data files
# SQL node options:
-[MYSQLD]
+[mysqld]
hostname=192.168.0.20 # Hostname or IP address
# (additional mysqld connections can be
# specified for this node for various
Modified: trunk/refman-5.0/mysql-cluster-backup.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster-backup.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.0/mysql-cluster-backup.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 4; 1744 bytes
@@ -592,11 +592,11 @@
utility acts as a cluster API node, and so requires a free
connection <quote>slot</quote> to connect to the cluster
management server. This means that there must be at least one
- <literal>[API]</literal> or <literal>[MYSQLD]</literal>
+ <literal>[api]</literal> or <literal>[mysqld]</literal>
section that can be used by it in the cluster
<filename>config.ini</filename> file. It is a good idea to
- keep at least one empty <literal>[API]</literal> or
- <literal>[MYSQLD]</literal> section in
+ keep at least one empty <literal>[api]</literal> or
+ <literal>[mysqld]</literal> section in
<filename>config.ini</filename> that is not being used for a
MySQL server or other application for this reason (see
<xref linkend="mysql-cluster-api-definition"/>).
@@ -686,7 +686,7 @@
parallel, provided that there is a sufficient number of
cluster connections available. That is, when restoring to
multiple nodes in parallel, you must have an
- <literal>[API]</literal> or <literal>[MYSQLD]</literal>
+ <literal>[api]</literal> or <literal>[mysqld]</literal>
section in the cluster <filename>config.ini</filename> file
available for each concurrent <command>ndb_restore</command>
process. However, the data files must always be applied
Modified: trunk/refman-5.0/mysql-cluster-configuration.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster-configuration.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.0/mysql-cluster-configuration.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 47, Lines Added: 81, Lines Deleted: 81; 22520 bytes
@@ -178,23 +178,23 @@
# Note: DB, API, and MGM are aliases for NDBD, MYSQLD, and NDB_MGMD
# respectively. DB and API are deprecated and should not be used in new
# installations.
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas= 1
-[MYSQLD DEFAULT]
-[NDB_MGMD DEFAULT]
-[TCP DEFAULT]
+[mysqld default]
+[NDB_MGMD default]
+[tcp default]
-[NDB_MGMD]
+[ndb_mgmd]
HostName= myhost.example.com
-[NDBD]
+[ndbd]
HostName= myhost.example.com
DataDir= /var/lib/mysql-cluster
-[MYSQLD]
-[MYSQLD]
-[MYSQLD]
+[mysqld]
+[mysqld]
+[mysqld]
</programlisting>
<para>
@@ -498,7 +498,7 @@
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>
+ <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
@@ -556,13 +556,13 @@
Default values are defined for most parameters, and can also be
specified in <filename>config.ini</filename>. To create a
default value section, simply add the word
- <literal>DEFAULT</literal> to the section name. For example, an
- <literal>[NDBD]</literal> section contains parameters that apply
+ <literal>default</literal> to the section name. For example, an
+ <literal>[ndbd]</literal> section contains parameters that apply
to a particular data node, whereas an <literal>[NDBD
- DEFAULT]</literal> section contains parameters that apply to all
+ default]</literal> section contains parameters that apply to all
data nodes. Suppose that all data nodes should use the same data
memory size. To configure them all, create an <literal>[NDBD
- DEFAULT]</literal> section that contains a
+ default]</literal> section that contains a
<literal>DataMemory</literal> line to specify the data memory
size.
</para>
@@ -582,22 +582,22 @@
# The first MySQL Server can be started from any host. The second
# can be started only on the host mysqld_5.mysql.com
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas= 2
DataDir= /var/lib/mysql-cluster
-[NDB_MGMD]
+[ndb_mgmd]
Hostname= ndb_mgmd.mysql.com
DataDir= /var/lib/mysql-cluster
-[NDBD]
+[ndbd]
HostName= ndbd_2.mysql.com
-[NDBD]
+[ndbd]
HostName= ndbd_3.mysql.com
-[MYSQLD]
-[MYSQLD]
+[mysqld]
+[mysqld]
HostName= mysqld_5.mysql.com
</programlisting>
@@ -605,7 +605,7 @@
Each node has its own section in the
<filename>config.ini</filename> file. For example, this cluster
has two data nodes, so the preceding configuration file contains
- two <literal>[NDBD]</literal> sections defining these nodes.
+ two <literal>[ndbd]</literal> sections defining these nodes.
</para>
<note>
@@ -632,7 +632,7 @@
<listitem>
<para>
- <literal>[COMPUTER]</literal>: Defines cluster hosts. This
+ <literal>[computer]</literal>: Defines cluster hosts. This
is not required to configure a viable MySQL Cluster, but be
may used as a convenience when setting up a large cluster.
See <xref linkend="mysql-cluster-computer-definition"/>, for
@@ -642,7 +642,7 @@
<listitem>
<para>
- <literal>[NDBD]</literal>: Defines a cluster data node
+ <literal>[ndbd]</literal>: Defines a cluster data node
(<command>ndbd</command> process). See
<xref linkend="mysql-cluster-ndbd-definition"/>, for
details.
@@ -651,7 +651,7 @@
<listitem>
<para>
- <literal>[MYSQLD]</literal>: Defines the cluster's MySQL
+ <literal>[mysqld]</literal>: Defines the cluster's MySQL
server nodes (also called SQL or API nodes). For a
discussion of SQL node configuration, see
<xref linkend="mysql-cluster-api-definition"/>.
@@ -660,7 +660,7 @@
<listitem>
<para>
- <literal>[MGM]</literal> or <literal>[NDB_MGMD]</literal>:
+ <literal>[mgm]</literal> or <literal>[ndb_mgmd]</literal>:
Defines a cluster management server (MGM) node. For
information concerning the configuration of MGM nodes, see
<xref linkend="mysql-cluster-mgm-definition"/>.
@@ -669,10 +669,10 @@
<listitem>
<para>
- <literal>[TCP]</literal>: Defines a TCP/IP connection
+ <literal>[tcp]</literal>: Defines a TCP/IP connection
between cluster nodes, with TCP/IP being the default
- connection protocol. Normally, <literal>[TCP]</literal> or
- <literal>[TCP DEFAULT]</literal> sections are not required
+ connection protocol. Normally, <literal>[tcp]</literal> or
+ <literal>[tcp default]</literal> sections are not required
to set up a MySQL Cluster, as the cluster handles this
automatically; however, it may be necessary in some
situations to override the defaults provided by the cluster.
@@ -686,7 +686,7 @@
<listitem>
<para>
- <literal>[SHM]</literal>: Defines shared-memory connections
+ <literal>[shm]</literal>: Defines shared-memory connections
between nodes. In MySQL ¤t-series;, it is enabled by
default, but should still be considered experimental. For a
discussion of SHM interconnects, see
@@ -696,7 +696,7 @@
<listitem>
<para>
- <literal>[SCI]</literal>:Defines <firstterm>Scalable
+ <literal>[sci]</literal>:Defines <firstterm>Scalable
Coherent Interface</firstterm> connections between cluster
data nodes. Such connections require software which, while
freely available, is not part of the MySQL Cluster
@@ -709,7 +709,7 @@
</itemizedlist>
<para>
- You can define <literal>DEFAULT</literal> values for each
+ You can define <literal>default</literal> values for each
section. All Cluster parameter names are case-insensitive, which
differs from parameters specified in <filename>my.cnf</filename>
or <filename>my.ini</filename> files.
@@ -868,7 +868,7 @@
</indexterm>
<para>
- The <literal>[COMPUTER]</literal> section has no real
+ The <literal>[computer]</literal> section has no real
significance other than serving as a way to avoid the need of
defining host names for each node in the system. All parameters
mentioned here are required.
@@ -917,8 +917,8 @@
</indexterm>
<para>
- The <literal>[NDB_MGMD]</literal> section is used to configure
- the behavior of the management server. <literal>[MGM]</literal>
+ The <literal>[ndb_mgmd]</literal> section is used to configure
+ the behavior of the management server. <literal>[mgm]</literal>
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.
@@ -962,7 +962,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers defined in a <literal>[COMPUTER]</literal> section
+ computers defined in a <literal>[computer]</literal> section
of the <filename>config.ini</filename> file.
</para>
</listitem>
@@ -1232,7 +1232,7 @@
</indexterm>
<para>
- The <literal>[NDBD]</literal> and [NDBD DEFAULT] sections are
+ The <literal>[ndbd]</literal> and [ndbddefault] sections are
used to configure the behavior of the cluster's data nodes.
There are many parameters which control buffer sizes, pool
sizes, timeouts, and so forth. The only mandatory parameters
@@ -1245,15 +1245,15 @@
<para>
Either <literal>ExecuteOnComputer</literal> or
<literal>HostName</literal>, which must be defined in the
- local <literal>[NDBD]</literal> section.
+ local <literal>[ndbd]</literal> section.
</para>
</listitem>
<listitem>
<para>
The parameter <literal>NoOfReplicas</literal>, which must be
- defined in the [NDBD DEFAULT] section, as it is common to
- all Cluster data nodes.
+ defined in the [ndbddefault] section, as it is common to all
+ Cluster data nodes.
</para>
</listitem>
@@ -1261,12 +1261,12 @@
<para>
Most data node parameters are set in the <literal>[NDBD
- DEFAULT]</literal> section. Only those parameters explicitly
+ default]</literal> section. Only those parameters explicitly
stated as being able to set local values are allowed to be
- changed in the <literal>[NDBD]</literal> section. Where present,
+ changed in the <literal>[ndbd]</literal> section. Where present,
<literal>HostName</literal>, <literal>Id</literal> and
<literal>ExecuteOnComputer</literal> <emphasis>must</emphasis>
- be defined in the local <literal>[NDBD]</literal> section, and
+ be defined in the local <literal>[ndbd]</literal> section, and
not in any other section of <filename>config.ini</filename>. In
other words, settings for these parameters are specific to one
data node.
@@ -1323,7 +1323,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers defined in a <literal>[COMPUTER]</literal>
+ computers defined in a <literal>[computer]</literal>
section.
</para>
</listitem>
@@ -1378,7 +1378,7 @@
<para>
This global parameter can be set only in the <literal>[NDBD
- DEFAULT]</literal> section, and defines the number of
+ default]</literal> section, and defines the number of
replicas for each table stored in the cluster. This
parameter also specifies the size of node groups. A node
group is a set of nodes all storing the same information.
@@ -1502,7 +1502,7 @@
<para>
<literal>DataMemory</literal> and <literal>IndexMemory</literal>
- are <literal>[NDBD]</literal> parameters specifying the size of
+ are <literal>[ndbd]</literal> parameters specifying the size of
memory segments used to store the actual records and their
indexes. In setting values for these, it is important to
understand how <literal>DataMemory</literal> and
@@ -1690,8 +1690,8 @@
<para>
This parameter determines how much memory is allocated for
strings such as table names, and is specified in an
- <literal>[NDBD]</literal> or <literal>[NDBD
- DEFAULT]</literal> section of the
+ <literal>[ndbd]</literal> or <literal>[NDBD
+ default]</literal> section of the
<filename>config.ini</filename> file. A value between
<literal>0</literal> and <literal>100</literal> inclusive is
interpreted as a percent of the maxmimum default value,
@@ -1821,7 +1821,7 @@
<title>Transaction parameters</title>
<para id="mysql-cluster-transaction-parameters">
- The next three <literal>[NDBD]</literal> parameters that we
+ The next three <literal>[ndbd]</literal> 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.
@@ -2005,7 +2005,7 @@
<title>Transaction temporary storage</title>
<para id="mysql-cluster-transaction-temporary-storage">
- The next set of <literal>[NDBD]</literal> parameters is used
+ 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
@@ -2130,7 +2130,7 @@
<title>Scans and buffering</title>
<para id="mysql-cluster-scans-and-buffering">
- There are additional <literal>[NDBD]</literal> parameters in
+ There are additional <literal>[ndbd]</literal> parameters in
the <literal>Dblqh</literal> module (in
<filename>ndb/src/kernel/blocks/Dblqh/Dblqh.hpp</filename>)
that affect reads and updates. These include
@@ -2256,7 +2256,7 @@
<title>Logging and checkpointing</title>
<para id="mysql-cluster-logging-and-checkpointing">
- These <literal>[NDBD]</literal> parameters control log and
+ These <literal>[ndbd]</literal> parameters control log and
checkpoint behavior.
</para>
@@ -2383,7 +2383,7 @@
<title>Metadata objects</title>
<para id="mysql-cluster-metadata-objects">
- The next set of <literal>[NDBD]</literal> parameters defines
+ The next set of <literal>[ndbd]</literal> parameters defines
pool sizes for metadata objects, used to define the maximum
number of attributes, tables, indexes, and trigger objects
used by indexes, events, and replication between clusters.
@@ -2577,7 +2577,7 @@
<para id="mysql-cluster-boolean-parameters">
The behavior of data nodes is also affected by a set of
- <literal>[NDBD]</literal> parameters taking on boolean values.
+ <literal>[ndbd]</literal> parameters taking on boolean values.
These parameters can each be specified as
<literal>TRUE</literal> by setting them equal to
<literal>1</literal> or <literal>Y</literal>, and as
@@ -2742,7 +2742,7 @@
</para>
<para>
- There are a number of <literal>[NDBD]</literal> parameters
+ There are a number of <literal>[ndbd]</literal> parameters
specifying timeouts and intervals between various actions in
Cluster data nodes. Most of the timeout values are specified in
milliseconds. Any exceptions to this are mentioned where
@@ -3257,7 +3257,7 @@
<title>Buffering and logging</title>
<para id="mysql-cluster-buffering-and-logging">
- Several <literal>[NDBD]</literal> configuration parameters
+ Several <literal>[ndbd]</literal> configuration parameters
corresponding to former compile-time parameters were
introduced in MySQL 4.1.5. These enable the advanced user to
have more control over the resources used by node processes
@@ -3643,7 +3643,7 @@
<title>Backup parameters</title>
<para id="mysql-cluster-backup-parameters">
- The <literal>[NDBD]</literal> parameters discussed in this
+ The <literal>[ndbd]</literal> parameters discussed in this
section define memory buffers set aside for execution of
online backups.
</para>
@@ -3846,7 +3846,7 @@
</indexterm>
<para>
- The <literal>[MYSQLD]</literal> and <literal>[API]</literal>
+ The <literal>[mysqld]</literal> and <literal>[api]</literal>
sections in the <filename>config.ini</filename> file define the
behavior of the MySQL servers (SQL nodes) and other applications
(API nodes) used to access cluster data. None of the parameters
@@ -3855,13 +3855,13 @@
</para>
<para>
- Generally speaking, a <literal>[MYSQLD]</literal> section is
+ Generally speaking, a <literal>[mysqld]</literal> section is
used to indicate a MySQL server providing an SQL interface to
- the cluster, and an <literal>[API]</literal> section is used for
+ the cluster, and an <literal>[api]</literal> section is used for
applications other than <command>mysqld</command> processes
accessing cluster data, but the two designations are actually
synonomous; you can, for instance, list parameters for a MySQL
- server acting as an SQL node in an <literal>[API]</literal>
+ server acting as an SQL node in an <literal>[api]</literal>
section.
</para>
@@ -3895,7 +3895,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers (hosts) defined in a <literal>[COMPUTER]</literal>
+ computers (hosts) defined in a <literal>[computer]</literal>
section of the configuration file.
</para>
</listitem>
@@ -4086,7 +4086,7 @@
node and all MySQL server nodes, and between each data node and
the management server. (For one exception to this rule, see
<xref linkend="mysql-cluster-tcp-definition-direct"/>.)
- <literal>[TCP]</literal> sections in the
+ <literal>[tcp]</literal> sections in the
<filename>config.ini</filename> file explicitly define TCP/IP
connections between nodes in the cluster.
</para>
@@ -4100,10 +4100,10 @@
<important>
<para>
- Any <literal>[TCP]</literal> sections in the
+ Any <literal>[tcp]</literal> sections in the
<filename>config.ini</filename> file should be listed last,
following any other sections in the file. This is not required
- for a <literal>[TCP DEFAULT]</literal> section. This is a
+ for a <literal>[tcp default]</literal> section. This is a
known issue with the way in which the
<filename>config.ini</filename> file is read by the cluster
management server.
@@ -4113,7 +4113,7 @@
<para>
It is also possible to change the default values for these
parameters by setting them in the <literal>[TCP
- DEFAULT]</literal> section.
+ default]</literal> section.
</para>
<itemizedlist>
@@ -4125,7 +4125,7 @@
<para>
To identify a connection between two nodes it is necessary
- to provide their node IDs in the <literal>[TCP]</literal>
+ to provide their node IDs in the <literal>[tcp]</literal>
section of the configuration file. These are the same unique
<literal>Id</literal> values for each of these nodes as
described in <xref linkend="mysql-cluster-api-definition"/>.
@@ -4255,7 +4255,7 @@
<para>
Setting up a cluster using direct connections between data nodes
requires specifying explicitly the crossover IP addresses of the
- data nodes so connected in the <literal>[TCP]</literal> section
+ data nodes so connected in the <literal>[tcp]</literal> section
of the cluster <filename>config.ini</filename> file.
</para>
@@ -4272,26 +4272,26 @@
<programlisting>
# Management Server
-[NDB_MGMD]
+[ndb_mgmd]
Id=1
HostName=172.23.72.20
# SQL Node
-[MYSQLD]
+[mysqld]
Id=2
HostName=172.23.72.21
# Data Nodes
-[NDBD]
+[ndbd]
Id=3
HostName=172.23.72.22
-[NDBD]
+[ndbd]
Id=4
HostName=172.23.72.23
# TCP/IP Connections
-[TCP]
+[tcp]
NodeId1=3
NodeId2=4
HostName1=1.1.0.1
@@ -4347,7 +4347,7 @@
configure it automatically where possible. (In very early
versions of MySQL Cluster, shared memory segments functioned
only when the server binary was built using
- <option>--with-ndb-shm</option>.) <literal>[SHM]</literal>
+ <option>--with-ndb-shm</option>.) <literal>[shm]</literal>
sections in the <filename>config.ini</filename> file explicitly
define shared-memory connections between nodes in the cluster.
When explicitly defining shared memory as the connection method,
@@ -4498,7 +4498,7 @@
</indexterm>
<para>
- <literal>[SCI]</literal> sections in the
+ <literal>[sci]</literal> sections in the
<filename>config.ini</filename> file explicitly define SCI
(Scalable Coherent Interface) connections between cluster nodes.
Using SCI transporters in MySQL Cluster is supported only when
@@ -4824,7 +4824,7 @@
</indexterm>
<indexterm>
- <primary><literal>[NDBD]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[ndbd]</literal> (MySQL Cluster)</primary>
</indexterm>
<indexterm>
@@ -4833,7 +4833,7 @@
<para>
The following table provides information about parameters used
- in the <literal>[NDBD]</literal> or
+ in the <literal>[ndbd]</literal> or
<literal>[NDB_DEFAULT]</literal> sections of a
<filename>config.ini</filename> file for configuring MySQL
Cluster data nodes. For detailed descriptions and other
@@ -5443,16 +5443,16 @@
</indexterm>
<indexterm>
- <primary><literal>[NDB_MGMD]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[ndb_mgmd]</literal> (MySQL Cluster)</primary>
</indexterm>
<indexterm>
- <primary><literal>[MGM]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[mgm]</literal> (MySQL Cluster)</primary>
</indexterm>
<para>
The following table provides information about parameters used
- in the <literal>[NDB_MGMD]</literal> or <literal>[MGM]</literal>
+ in the <literal>[ndb_mgmd]</literal> or <literal>[mgm]</literal>
sections of a <filename>config.ini</filename> file for
configuring MySQL Cluster management nodes. For detailed
descriptions and other additional information about each of
@@ -5593,12 +5593,12 @@
</indexterm>
<indexterm>
- <primary><literal>[API]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[api]</literal> (MySQL Cluster)</primary>
</indexterm>
<para>
The following table provides information about parameters used
- in the <literal>[SQL]</literal> and <literal>[API]</literal>
+ in the <literal>[SQL]</literal> and <literal>[api]</literal>
sections of a <filename>config.ini</filename> file for
configuring MySQL Cluster SQL nodes and API nodes. For detailed
descriptions and other additional information about each of
Modified: trunk/refman-5.0/mysql-cluster-limitations.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster-limitations.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.0/mysql-cluster-limitations.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 819 bytes
@@ -1339,7 +1339,7 @@
<emphasis>interfaces</emphasis> (such as Ethernet cards) for
a single data node, but these must be bound to the same
address. This also means that it not possible to use more
- than one <literal>[TCP]</literal> section per connection in
+ than one <literal>[tcp]</literal> section per connection in
the <literal>config.ini</literal> file. See
<xref linkend="mysql-cluster-tcp-definition"/>, for more
information.
Modified: trunk/refman-5.0/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster-multi-computer.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.0/mysql-cluster-multi-computer.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 5, Lines Added: 10, Lines Deleted: 10; 3134 bytes
@@ -958,12 +958,12 @@
<programlisting>
# Options for mysqld process:
-[MYSQLD]
+[mysqld]
ndbcluster # run NDB storage engine
ndb-connectstring=192.168.0.10 # location of management server
# Options for ndbd process:
-[MYSQL_CLUSTER]
+[mysql_cluster]
ndb-connectstring=192.168.0.10 # location of management server
</programlisting>
@@ -978,7 +978,7 @@
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>
+ <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
@@ -1013,7 +1013,7 @@
<programlisting>
# Options affecting ndbd processes on all data nodes:
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas=2 # Number of replicas
DataMemory=80M # How much memory to allocate for data storage
IndexMemory=18M # How much memory to allocate for index storage
@@ -1023,7 +1023,7 @@
# this example Cluster setup.
# TCP/IP options:
-[TCP DEFAULT]
+[tcp default]
portnumber=2202 # This the default; however, you can use any
# port that is free for all the hosts in cluster
# Note: It is recommended beginning with MySQL 5.0 that
@@ -1031,23 +1031,23 @@
# the default value to be used instead
# Management process options:
-[NDB_MGMD]
+[ndb_mgmd]
hostname=192.168.0.10 # Hostname or IP address of MGM node
datadir=/var/lib/mysql-cluster # Directory for MGM node log files
# Options for data node "A":
-[NDBD]
- # (one [NDBD] section per data node)
+[ndbd]
+ # (one [ndbd] section per data node)
hostname=192.168.0.30 # Hostname or IP address
datadir=/usr/local/mysql/data # Directory for this data node's data files
# Options for data node "B":
-[NDBD]
+[ndbd]
hostname=192.168.0.40 # Hostname or IP address
datadir=/usr/local/mysql/data # Directory for this data node's data files
# SQL node options:
-[MYSQLD]
+[mysqld]
hostname=192.168.0.20 # Hostname or IP address
# (additional mysqld connections can be
# specified for this node for various
Modified: trunk/refman-5.1/mysql-cluster-backup.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-backup.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.1/mysql-cluster-backup.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 4; 1744 bytes
@@ -592,11 +592,11 @@
utility acts as a cluster API node, and so requires a free
connection <quote>slot</quote> to connect to the cluster
management server. This means that there must be at least one
- <literal>[API]</literal> or <literal>[MYSQLD]</literal>
+ <literal>[api]</literal> or <literal>[mysqld]</literal>
section that can be used by it in the cluster
<filename>config.ini</filename> file. It is a good idea to
- keep at least one empty <literal>[API]</literal> or
- <literal>[MYSQLD]</literal> section in
+ keep at least one empty <literal>[api]</literal> or
+ <literal>[mysqld]</literal> section in
<filename>config.ini</filename> that is not being used for a
MySQL server or other application for this reason (see
<xref linkend="mysql-cluster-api-definition"/>).
@@ -723,7 +723,7 @@
parallel, provided that there is a sufficient number of
cluster connections available. That is, when restoring to
multiple nodes in parallel, you must have an
- <literal>[API]</literal> or <literal>[MYSQLD]</literal>
+ <literal>[api]</literal> or <literal>[mysqld]</literal>
section in the cluster <filename>config.ini</filename> file
available for each concurrent <command>ndb_restore</command>
process. However, the data files must always be applied
Modified: trunk/refman-5.1/mysql-cluster-ccsg-merge-temp.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-ccsg-merge-temp.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.1/mysql-cluster-ccsg-merge-temp.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 59, Lines Added: 103, Lines Deleted: 103; 29304 bytes
@@ -2337,12 +2337,12 @@
<programlisting>
# Options for mysqld process:
-[MYSQLD]
+[mysqld]
ndbcluster # run NDB storage engine
ndb-connectstring=192.168.0.10 # location of management server
# Options for ndbd process:
-[MYSQL_CLUSTER]
+[mysql_cluster]
ndb-connectstring=192.168.0.10 # location of management server
</programlisting>
@@ -2357,7 +2357,7 @@
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> section of the
+ <literal>[mysqld]</literal> section of 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
@@ -2390,7 +2390,7 @@
<programlisting>
# Options affecting ndbd processes on all data nodes:
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas=2 # Number of replicas
DataMemory=80M # How much memory to allocate for data storage
IndexMemory=18M # How much memory to allocate for index storage
@@ -2400,7 +2400,7 @@
# this example Cluster setup.
# TCP/IP options:
-[TCP DEFAULT]
+[tcp default]
portnumber=2202 # This the default; however, you can use any
# port that is free for all the hosts in the cluster
# Note: It is recommended that you do not specify the
@@ -2408,23 +2408,23 @@
# used instead
# Management process options:
-[NDB_MGMD]
+[ndb_mgmd]
hostname=192.168.0.10 # Hostname or IP address of MGM node
datadir=/var/lib/mysql-cluster # Directory for MGM node log files
# Options for data node "A":
-[NDBD]
- # (one [NDBD] section per data node)
+[ndbd]
+ # (one [ndbd] section per data node)
hostname=192.168.0.30 # Hostname or IP address
datadir=/usr/local/mysql/data # Directory for this data node's data files
# Options for data node "B":
-[NDBD]
+[ndbd]
hostname=192.168.0.40 # Hostname or IP address
datadir=/usr/local/mysql/data # Directory for this data node's data files
# SQL node options:
-[MYSQLD]
+[mysqld]
hostname=192.168.0.20 # Hostname or IP address
# (additional mysqld connections can be
# specified for this node for various
@@ -3288,23 +3288,23 @@
# Note: DB, API, and MGM are aliases for NDBD, MYSQLD, and NDB_MGMD
# respectively. DB and API are deprecated and should not be used in new
# installations.
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas= 1
-[MYSQLD DEFAULT]
-[NDB_MGMD DEFAULT]
-[TCP DEFAULT]
+[mysqld default]
+[NDB_MGMD default]
+[tcp default]
-[NDB_MGMD]
+[ndb_mgmd]
HostName= myhost.example.com
-[NDBD]
+[ndbd]
HostName= myhost.example.com
DataDir= /var/lib/mysql-cluster
-[MYSQLD]
-[MYSQLD]
-[MYSQLD]
+[mysqld]
+[mysqld]
+[mysqld]
</programlisting>
<para>
@@ -3634,7 +3634,7 @@
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
+ <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
@@ -3693,13 +3693,13 @@
Default values are defined for most parameters, and can also
be specified in <filename>config.ini</filename>. To create a
default value section, simply add the word
- <literal>DEFAULT</literal> to the section name. For example,
- an <literal>[NDBD]</literal> section contains parameters that
+ <literal>default</literal> to the section name. For example,
+ an <literal>[ndbd]</literal> section contains parameters that
apply to a particular data node, whereas an <literal>[NDBD
- DEFAULT]</literal> section contains parameters that apply to
+ default]</literal> section contains parameters that apply to
all data nodes. Suppose that all data nodes should use the
same data memory size. To configure them all, create an
- <literal>[NDBD DEFAULT]</literal> section that contains a
+ <literal>[ndbddefault]</literal> section that contains a
<literal>DataMemory</literal> line to specify the data memory
size.
</para>
@@ -3719,22 +3719,22 @@
# The first MySQL Server can be started from any host. The second
# can be started only on the host mysqld_5.mysql.com
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas= 2
DataDir= /var/lib/mysql-cluster
-[NDB_MGMD]
+[ndb_mgmd]
Hostname= ndb_mgmd.mysql.com
DataDir= /var/lib/mysql-cluster
-[NDBD]
+[ndbd]
HostName= ndbd_2.mysql.com
-[NDBD]
+[ndbd]
HostName= ndbd_3.mysql.com
-[MYSQLD]
-[MYSQLD]
+[mysqld]
+[mysqld]
HostName= mysqld_5.mysql.com
</programlisting>
@@ -3742,7 +3742,7 @@
Each node has its own section in the
<filename>config.ini</filename> file. For example, this
cluster has two data nodes, so the preceding configuration
- file contains two <literal>[NDBD]</literal> sections defining
+ file contains two <literal>[ndbd]</literal> sections defining
these nodes.
</para>
@@ -3770,7 +3770,7 @@
<listitem>
<para>
- <literal>[COMPUTER]</literal>: Defines cluster hosts. This
+ <literal>[computer]</literal>: Defines cluster hosts. This
is not required to configure a viable MySQL Cluster, but
be may used as a convenience when setting up a large
cluster. See
@@ -3781,7 +3781,7 @@
<listitem>
<para>
- <literal>[NDBD]</literal>: Defines a cluster data node
+ <literal>[ndbd]</literal>: Defines a cluster data node
(<command>ndbd</command> process). See
<xref linkend="mysql-cluster-ndbd-definition"/>, for
details.
@@ -3790,7 +3790,7 @@
<listitem>
<para>
- <literal>[MYSQLD]</literal>: Defines the cluster's MySQL
+ <literal>[mysqld]</literal>: Defines the cluster's MySQL
server nodes (also called SQL or API nodes). For a
discussion of SQL node configuration, see
<xref linkend="mysql-cluster-api-definition"/>.
@@ -3799,7 +3799,7 @@
<listitem>
<para>
- <literal>[MGM]</literal> or <literal>[NDB_MGMD]</literal>:
+ <literal>[mgm]</literal> or <literal>[ndb_mgmd]</literal>:
Defines a cluster management server (MGM) node. For
information concerning the configuration of MGM nodes, see
<xref linkend="mysql-cluster-mgm-definition"/>.
@@ -3808,10 +3808,10 @@
<listitem>
<para>
- <literal>[TCP]</literal>: Defines a TCP/IP connection
+ <literal>[tcp]</literal>: Defines a TCP/IP connection
between cluster nodes, with TCP/IP being the default
- connection protocol. Normally, <literal>[TCP]</literal> or
- <literal>[TCP DEFAULT]</literal> sections are not required
+ connection protocol. Normally, <literal>[tcp]</literal> or
+ <literal>[tcp default]</literal> sections are not required
to set up a MySQL Cluster, as the cluster handles this
automatically; however, it may be necessary in some
situations to override the defaults provided by the
@@ -3826,7 +3826,7 @@
<listitem>
<para>
- <literal>[SHM]</literal>: Defines shared-memory
+ <literal>[shm]</literal>: Defines shared-memory
connections between nodes. In MySQL ¤t-series;, it
is enabled by default, but should still be considered
experimental. For a discussion of SHM interconnects, see
@@ -3836,7 +3836,7 @@
<listitem>
<para>
- <literal>[SCI]</literal>:Defines <firstterm>Scalable
+ <literal>[sci]</literal>:Defines <firstterm>Scalable
Coherent Interface</firstterm> connections between cluster
data nodes. Such connections require software which, while
freely available, is not part of the MySQL Cluster
@@ -3849,7 +3849,7 @@
</itemizedlist>
<para>
- You can define <literal>DEFAULT</literal> values for each
+ You can define <literal>default</literal> values for each
section. All Cluster parameter names are case-insensitive,
which differs from parameters specified in
<filename>my.cnf</filename> or <filename>my.ini</filename>
@@ -4010,7 +4010,7 @@
</indexterm>
<para>
- The <literal>[COMPUTER]</literal> section has no real
+ The <literal>[computer]</literal> section has no real
significance other than serving as a way to avoid the need of
defining host names for each node in the system. All
parameters mentioned here are required.
@@ -4059,9 +4059,9 @@
</indexterm>
<para>
- The <literal>[NDB_MGMD]</literal> section is used to configure
+ The <literal>[ndb_mgmd]</literal> section is used to configure
the behavior of the management server.
- <literal>[MGM]</literal> can be used as an alias; the two
+ <literal>[mgm]</literal> 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.
</para>
@@ -4105,7 +4105,7 @@
<para>
This refers to the <literal>Id</literal> set for one of
- the computers defined in a <literal>[COMPUTER]</literal>
+ the computers defined in a <literal>[computer]</literal>
section of the <filename>config.ini</filename> file.
</para>
</listitem>
@@ -4385,7 +4385,7 @@
</indexterm>
<para>
- The <literal>[NDBD]</literal> and [NDBD DEFAULT] sections are
+ The <literal>[ndbd]</literal> and [ndbddefault] sections are
used to configure the behavior of the cluster's data nodes.
There are many parameters which control buffer sizes, pool
sizes, timeouts, and so forth. The only mandatory parameters
@@ -4398,14 +4398,14 @@
<para>
Either <literal>ExecuteOnComputer</literal> or
<literal>HostName</literal>, which must be defined in the
- local <literal>[NDBD]</literal> section.
+ local <literal>[ndbd]</literal> section.
</para>
</listitem>
<listitem>
<para>
The parameter <literal>NoOfReplicas</literal>, which must
- be defined in the [NDBD DEFAULT] section, as it is common
+ be defined in the [ndbddefault] section, as it is common
to all Cluster data nodes.
</para>
</listitem>
@@ -4414,13 +4414,13 @@
<para>
Most data node parameters are set in the <literal>[NDBD
- DEFAULT]</literal> section. Only those parameters explicitly
+ default]</literal> section. Only those parameters explicitly
stated as being able to set local values are allowed to be
- changed in the <literal>[NDBD]</literal> section. Where
+ changed in the <literal>[ndbd]</literal> section. Where
present, <literal>HostName</literal>, <literal>Id</literal>
and <literal>ExecuteOnComputer</literal>
<emphasis>must</emphasis> be defined in the local
- <literal>[NDBD]</literal> section, and not in any other
+ <literal>[ndbd]</literal> section, and not in any other
section of <filename>config.ini</filename>. In other words,
settings for these parameters are specific to one data node.
</para>
@@ -4475,7 +4475,7 @@
<para>
This refers to the <literal>Id</literal> set for one of
- the computers defined in a <literal>[COMPUTER]</literal>
+ the computers defined in a <literal>[computer]</literal>
section.
</para>
</listitem>
@@ -4554,7 +4554,7 @@
<para>
This global parameter can be set only in the
- <literal>[NDBD DEFAULT]</literal> section, and defines the
+ <literal>[ndbddefault]</literal> section, and defines the
number of replicas for each table stored in the cluster.
This parameter also specifies the size of node groups. A
node group is a set of nodes all storing the same
@@ -4675,7 +4675,7 @@
<para>
<literal>DataMemory</literal> and
- <literal>IndexMemory</literal> are <literal>[NDBD]</literal>
+ <literal>IndexMemory</literal> are <literal>[ndbd]</literal>
parameters specifying the size of memory segments used to
store the actual records and their indexes. In setting values
for these, it is important to understand how
@@ -4874,8 +4874,8 @@
<para>
This parameter determines how much memory is allocated for
strings such as table names, and is specified in an
- <literal>[NDBD]</literal> or <literal>[NDBD
- DEFAULT]</literal> section of the
+ <literal>[ndbd]</literal> or <literal>[NDBD
+ default]</literal> section of the
<filename>config.ini</filename> file. A value between
<literal>0</literal> and <literal>100</literal> inclusive
is interpreted as a percent of the maximum default value,
@@ -5011,7 +5011,7 @@
</para>
<para>
- The next three <literal>[NDBD]</literal> parameters that we
+ The next three <literal>[ndbd]</literal> 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.
@@ -5197,7 +5197,7 @@
</para>
<para>
- The next set of <literal>[NDBD]</literal> parameters is used
+ 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
@@ -5324,7 +5324,7 @@
<itemizedlist>
<para>
- There are additional <literal>[NDBD]</literal> parameters in
+ There are additional <literal>[ndbd]</literal> parameters in
the <literal>Dblqh</literal> module (in
<filename>ndb/src/kernel/blocks/Dblqh/Dblqh.hpp</filename>)
that affect reads and updates. These include
@@ -5475,7 +5475,7 @@
</para>
<para>
- These <literal>[NDBD]</literal> parameters control log and
+ These <literal>[ndbd]</literal> parameters control log and
checkpoint behavior.
</para>
@@ -5643,7 +5643,7 @@
</para>
<para>
- The next set of <literal>[NDBD]</literal> parameters defines
+ The next set of <literal>[ndbd]</literal> parameters defines
pool sizes for metadata objects, used to define the maximum
number of attributes, tables, indexes, and trigger objects
used by indexes, events, and replication between clusters.
@@ -5842,7 +5842,7 @@
<para>
The behavior of data nodes is also affected by a set of
- <literal>[NDBD]</literal> parameters taking on boolean values.
+ <literal>[ndbd]</literal> parameters taking on boolean values.
These parameters can each be specified as
<literal>TRUE</literal> by setting them equal to
<literal>1</literal> or <literal>Y</literal>, and as
@@ -6063,7 +6063,7 @@
</para>
<para>
- There are a number of <literal>[NDBD]</literal> parameters
+ There are a number of <literal>[ndbd]</literal> parameters
specifying timeouts and intervals between various actions in
Cluster data nodes. Most of the timeout values are specified
in milliseconds. Any exceptions to this are mentioned where
@@ -7028,10 +7028,10 @@
<para>
<literal>MemReportFrequency</literal> is not a required
parameter. If used, it can be set for all cluster data
- nodes in the <literal>[NDBD DEFAULT]</literal> section of
+ nodes in the <literal>[ndbddefault]</literal> section of
<filename>config.ini</filename>, and can also be set or
overridden for individual data nodes in the corresponding
- <literal>[NDBD]</literal> sections of the configuration
+ <literal>[ndbd]</literal> sections of the configuration
file. The minimum value — which is also the default
value — is 0, in which case memory reports are
logged only when memory usage reaches certain percentages
@@ -7053,7 +7053,7 @@
</para>
<para>
- The <literal>[NDBD]</literal> parameters discussed in this
+ The <literal>[ndbd]</literal> parameters discussed in this
section define memory buffers set aside for execution of
online backups.
</para>
@@ -7286,7 +7286,7 @@
</indexterm>
<para>
- The <literal>[MYSQLD]</literal> and <literal>[API]</literal>
+ The <literal>[mysqld]</literal> and <literal>[api]</literal>
sections in the <filename>config.ini</filename> file define
the behavior of the MySQL servers (SQL nodes) and other
applications (API nodes) used to access cluster data. None of
@@ -7295,14 +7295,14 @@
</para>
<para>
- Generally speaking, a <literal>[MYSQLD]</literal> section is
+ Generally speaking, a <literal>[mysqld]</literal> section is
used to indicate a MySQL server providing an SQL interface to
- the cluster, and an <literal>[API]</literal> section is used
+ the cluster, and an <literal>[api]</literal> section is used
for applications other than <command>mysqld</command>
processes accessing cluster data, but the two designations are
actually synonomous; you can, for instance, list parameters
for a MySQL server acting as an SQL node in an
- <literal>[API]</literal> section.
+ <literal>[api]</literal> section.
</para>
<itemizedlist>
@@ -7336,7 +7336,7 @@
<para>
This refers to the <literal>Id</literal> set for one of
the computers (hosts) defined in a
- <literal>[COMPUTER]</literal> section of the configuration
+ <literal>[computer]</literal> section of the configuration
file.
</para>
</listitem>
@@ -7522,7 +7522,7 @@
node and all MySQL server nodes, and between each data node
and the management server. (For one exception to this rule,
see <xref linkend="mysql-cluster-tcp-definition-direct"/>.)
- <literal>[TCP]</literal> sections in the
+ <literal>[tcp]</literal> sections in the
<filename>config.ini</filename> file explicitly define TCP/IP
connections between nodes in the cluster.
</para>
@@ -7536,10 +7536,10 @@
<important>
<para>
- Any <literal>[TCP]</literal> sections in the
+ Any <literal>[tcp]</literal> sections in the
<filename>config.ini</filename> file should be listed last,
following any other sections in the file. This is not
- required for a <literal>[TCP DEFAULT]</literal> section.
+ required for a <literal>[tcp default]</literal> section.
This is a known issue with the way in which the
<filename>config.ini</filename> file is read by the cluster
management server.
@@ -7549,7 +7549,7 @@
<para>
It is also possible to change the default values for these
parameters by setting them in the <literal>[TCP
- DEFAULT]</literal> section.
+ default]</literal> section.
</para>
<itemizedlist>
@@ -7561,7 +7561,7 @@
<para>
To identify a connection between two nodes it is necessary
- to provide their node IDs in the <literal>[TCP]</literal>
+ to provide their node IDs in the <literal>[tcp]</literal>
section of the configuration file. These are the same
unique <literal>Id</literal> values for each of these
nodes as described in
@@ -7693,7 +7693,7 @@
Setting up a cluster using direct connections between data
nodes requires specifying explicitly the crossover IP
addresses of the data nodes so connected in the
- <literal>[TCP]</literal> section of the cluster
+ <literal>[tcp]</literal> section of the cluster
<filename>config.ini</filename> file.
</para>
@@ -7710,26 +7710,26 @@
<programlisting>
# Management Server
-[NDB_MGMD]
+[ndb_mgmd]
Id=1
HostName=172.23.72.20
# SQL Node
-[MYSQLD]
+[mysqld]
Id=2
HostName=172.23.72.21
# Data Nodes
-[NDBD]
+[ndbd]
Id=3
HostName=172.23.72.22
-[NDBD]
+[ndbd]
Id=4
HostName=172.23.72.23
# TCP/IP Connections
-[TCP]
+[tcp]
NodeId1=3
NodeId2=4
HostName1=1.1.0.1
@@ -7783,7 +7783,7 @@
<para>
MySQL Cluster attempts to use the shared memory transporter
and configure it automatically where possible.
- <literal>[SHM]</literal> sections in the
+ <literal>[shm]</literal> sections in the
<filename>config.ini</filename> file explicitly define
shared-memory connections between nodes in the cluster. When
explicitly defining shared memory as the connection method, it
@@ -7936,7 +7936,7 @@
</indexterm>
<para>
- <literal>[SCI]</literal> sections in the
+ <literal>[sci]</literal> sections in the
<filename>config.ini</filename> file explicitly define SCI
(Scalable Coherent Interface) connections between cluster
nodes. Using SCI transporters in MySQL Cluster is supported
@@ -8263,7 +8263,7 @@
</indexterm>
<indexterm>
- <primary><literal>[NDBD]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[ndbd]</literal> (MySQL Cluster)</primary>
</indexterm>
<indexterm>
@@ -8272,7 +8272,7 @@
<para>
The following table provides information about parameters used
- in the <literal>[NDBD]</literal> or
+ in the <literal>[ndbd]</literal> or
<literal>[NDB_DEFAULT]</literal> sections of a
<filename>config.ini</filename> file for configuring MySQL
Cluster data nodes. For detailed descriptions and other
@@ -9023,17 +9023,17 @@
</indexterm>
<indexterm>
- <primary><literal>[NDB_MGMD]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[ndb_mgmd]</literal> (MySQL Cluster)</primary>
</indexterm>
<indexterm>
- <primary><literal>[MGM]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[mgm]</literal> (MySQL Cluster)</primary>
</indexterm>
<para>
The following table provides information about parameters used
- in the <literal>[NDB_MGMD]</literal> or
- <literal>[MGM]</literal> sections of a
+ in the <literal>[ndb_mgmd]</literal> or
+ <literal>[mgm]</literal> sections of a
<filename>config.ini</filename> file for configuring MySQL
Cluster management nodes. For detailed descriptions and other
additional information about each of these parameters, see
@@ -9173,12 +9173,12 @@
</indexterm>
<indexterm>
- <primary><literal>[API]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[api]</literal> (MySQL Cluster)</primary>
</indexterm>
<para>
The following table provides information about parameters used
- in the <literal>[SQL]</literal> and <literal>[API]</literal>
+ in the <literal>[SQL]</literal> and <literal>[api]</literal>
sections of a <filename>config.ini</filename> file for
configuring MySQL Cluster SQL nodes and API nodes. For
detailed descriptions and other additional information about
@@ -14889,11 +14889,11 @@
utility acts as a cluster API node, and so requires a free
connection <quote>slot</quote> to connect to the cluster
management server. This means that there must be at least
- one <literal>[API]</literal> or <literal>[MYSQLD]</literal>
+ one <literal>[api]</literal> or <literal>[mysqld]</literal>
section that can be used by it in the cluster
<filename>config.ini</filename> file. It is a good idea to
- keep at least one empty <literal>[API]</literal> or
- <literal>[MYSQLD]</literal> section in
+ keep at least one empty <literal>[api]</literal> or
+ <literal>[mysqld]</literal> section in
<filename>config.ini</filename> that is not being used for a
MySQL server or other application for this reason (see
<xref linkend="mysql-cluster-api-definition"/>).
@@ -15026,7 +15026,7 @@
parallel, provided that there is a sufficient number of
cluster connections available. That is, when restoring to
multiple nodes in parallel, you must have an
- <literal>[API]</literal> or <literal>[MYSQLD]</literal>
+ <literal>[api]</literal> or <literal>[mysqld]</literal>
section in the cluster <filename>config.ini</filename>
file available for each concurrent
<command>ndb_restore</command> process. However, the data
@@ -20124,7 +20124,7 @@
</programlisting>
<para>
- in a <literal>[MYSQL_CLUSTER]</literal> section in the
+ in a <literal>[mysql_cluster]</literal> section in the
<filename>my.cnf file</filename>, where
<replaceable>management_host</replaceable> is the IP
address or hostname of the <literal>NDB</literal>
@@ -21531,7 +21531,7 @@
<filename>config.ini</filename> includes the following:
<programlisting>
-[ndbd default]
+[ndbddefault]
DataDir= /data0
</programlisting>
@@ -21731,8 +21731,8 @@
<para>
This determines the amount of space used for caching pages
- on disk, and is set in the <literal>[NDBD]</literal> or
- <literal>[NDBD DEFAULT]</literal> section of the
+ on disk, and is set in the <literal>[ndbd]</literal> or
+ <literal>[ndbddefault]</literal> section of the
<filename>config.ini</filename> file. It is measured in
bytes. Each page takes up 32 KB. This means that Cluster
Disk Data storage always uses <replaceable>N</replaceable> *
@@ -21755,8 +21755,8 @@
buffers, disk operations (such as page requests and wait
queues), and metadata for tablespaces, log file groups,
<literal>UNDO</literal> files, and data files. It can be set
- in the <literal>[NDBD]</literal> or <literal>[NDBD
- DEFAULT]</literal> section of the
+ in the <literal>[ndbd]</literal> or <literal>[NDBD
+ default]</literal> section of the
<filename>config.ini</filename> configuration file, and is
measured in bytes.
</para>
@@ -24064,7 +24064,7 @@
<emphasis>interfaces</emphasis> (such as Ethernet cards)
for a single data node, but these must be bound to the
same address. This also means that it not possible to use
- more than one <literal>[TCP]</literal> section per
+ more than one <literal>[tcp]</literal> section per
connection in the <literal>config.ini</literal> file. See
<xref linkend="mysql-cluster-tcp-definition"/>, for more
information.
Modified: trunk/refman-5.1/mysql-cluster-configuration.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-configuration.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.1/mysql-cluster-configuration.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 49, Lines Added: 84, Lines Deleted: 84; 23537 bytes
@@ -213,23 +213,23 @@
# Note: DB, API, and MGM are aliases for NDBD, MYSQLD, and NDB_MGMD
# respectively. DB and API are deprecated and should not be used in new
# installations.
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas= 1
-[MYSQLD DEFAULT]
-[NDB_MGMD DEFAULT]
-[TCP DEFAULT]
+[mysqld default]
+[NDB_MGMD default]
+[tcp default]
-[NDB_MGMD]
+[ndb_mgmd]
HostName= myhost.example.com
-[NDBD]
+[ndbd]
HostName= myhost.example.com
DataDir= /var/lib/mysql-cluster
-[MYSQLD]
-[MYSQLD]
-[MYSQLD]
+[mysqld]
+[mysqld]
+[mysqld]
</programlisting>
<para>
@@ -533,7 +533,7 @@
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>
+ <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
@@ -591,13 +591,13 @@
Default values are defined for most parameters, and can also be
specified in <filename>config.ini</filename>. To create a
default value section, simply add the word
- <literal>DEFAULT</literal> to the section name. For example, an
- <literal>[NDBD]</literal> section contains parameters that apply
+ <literal>default</literal> to the section name. For example, an
+ <literal>[ndbd]</literal> section contains parameters that apply
to a particular data node, whereas an <literal>[NDBD
- DEFAULT]</literal> section contains parameters that apply to all
+ default]</literal> section contains parameters that apply to all
data nodes. Suppose that all data nodes should use the same data
memory size. To configure them all, create an <literal>[NDBD
- DEFAULT]</literal> section that contains a
+ default]</literal> section that contains a
<literal>DataMemory</literal> line to specify the data memory
size.
</para>
@@ -617,22 +617,22 @@
# The first MySQL Server can be started from any host. The second
# can be started only on the host mysqld_5.mysql.com
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas= 2
DataDir= /var/lib/mysql-cluster
-[NDB_MGMD]
+[ndb_mgmd]
Hostname= ndb_mgmd.mysql.com
DataDir= /var/lib/mysql-cluster
-[NDBD]
+[ndbd]
HostName= ndbd_2.mysql.com
-[NDBD]
+[ndbd]
HostName= ndbd_3.mysql.com
-[MYSQLD]
-[MYSQLD]
+[mysqld]
+[mysqld]
HostName= mysqld_5.mysql.com
</programlisting>
@@ -640,7 +640,7 @@
Each node has its own section in the
<filename>config.ini</filename> file. For example, this cluster
has two data nodes, so the preceding configuration file contains
- two <literal>[NDBD]</literal> sections defining these nodes.
+ two <literal>[ndbd]</literal> sections defining these nodes.
</para>
<note>
@@ -667,7 +667,7 @@
<listitem>
<para>
- <literal>[COMPUTER]</literal>: Defines cluster hosts. This
+ <literal>[computer]</literal>: Defines cluster hosts. This
is not required to configure a viable MySQL Cluster, but be
may used as a convenience when setting up a large cluster.
See <xref linkend="mysql-cluster-computer-definition"/>, for
@@ -677,7 +677,7 @@
<listitem>
<para>
- <literal>[NDBD]</literal>: Defines a cluster data node
+ <literal>[ndbd]</literal>: Defines a cluster data node
(<command>ndbd</command> process). See
<xref linkend="mysql-cluster-ndbd-definition"/>, for
details.
@@ -686,7 +686,7 @@
<listitem>
<para>
- <literal>[MYSQLD]</literal>: Defines the cluster's MySQL
+ <literal>[mysqld]</literal>: Defines the cluster's MySQL
server nodes (also called SQL or API nodes). For a
discussion of SQL node configuration, see
<xref linkend="mysql-cluster-api-definition"/>.
@@ -695,7 +695,7 @@
<listitem>
<para>
- <literal>[MGM]</literal> or <literal>[NDB_MGMD]</literal>:
+ <literal>[mgm]</literal> or <literal>[ndb_mgmd]</literal>:
Defines a cluster management server (MGM) node. For
information concerning the configuration of MGM nodes, see
<xref linkend="mysql-cluster-mgm-definition"/>.
@@ -704,10 +704,10 @@
<listitem>
<para>
- <literal>[TCP]</literal>: Defines a TCP/IP connection
+ <literal>[tcp]</literal>: Defines a TCP/IP connection
between cluster nodes, with TCP/IP being the default
- connection protocol. Normally, <literal>[TCP]</literal> or
- <literal>[TCP DEFAULT]</literal> sections are not required
+ connection protocol. Normally, <literal>[tcp]</literal> or
+ <literal>[tcp default]</literal> sections are not required
to set up a MySQL Cluster, as the cluster handles this
automatically; however, it may be necessary in some
situations to override the defaults provided by the cluster.
@@ -721,7 +721,7 @@
<listitem>
<para>
- <literal>[SHM]</literal>: Defines shared-memory connections
+ <literal>[shm]</literal>: Defines shared-memory connections
between nodes. In MySQL ¤t-series;, it is enabled by
default, but should still be considered experimental. For a
discussion of SHM interconnects, see
@@ -731,7 +731,7 @@
<listitem>
<para>
- <literal>[SCI]</literal>:Defines <firstterm>Scalable
+ <literal>[sci]</literal>:Defines <firstterm>Scalable
Coherent Interface</firstterm> connections between cluster
data nodes. Such connections require software which, while
freely available, is not part of the MySQL Cluster
@@ -744,7 +744,7 @@
</itemizedlist>
<para>
- You can define <literal>DEFAULT</literal> values for each
+ You can define <literal>default</literal> values for each
section. All Cluster parameter names are case-insensitive, which
differs from parameters specified in <filename>my.cnf</filename>
or <filename>my.ini</filename> files.
@@ -903,7 +903,7 @@
</indexterm>
<para>
- The <literal>[COMPUTER]</literal> section has no real
+ The <literal>[computer]</literal> section has no real
significance other than serving as a way to avoid the need of
defining host names for each node in the system. All parameters
mentioned here are required.
@@ -952,8 +952,8 @@
</indexterm>
<para>
- The <literal>[NDB_MGMD]</literal> section is used to configure
- the behavior of the management server. <literal>[MGM]</literal>
+ The <literal>[ndb_mgmd]</literal> section is used to configure
+ the behavior of the management server. <literal>[mgm]</literal>
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.
@@ -997,7 +997,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers defined in a <literal>[COMPUTER]</literal> section
+ computers defined in a <literal>[computer]</literal> section
of the <filename>config.ini</filename> file.
</para>
</listitem>
@@ -1275,7 +1275,7 @@
</indexterm>
<para>
- The <literal>[NDBD]</literal> and [NDBD DEFAULT] sections are
+ The <literal>[ndbd]</literal> and [ndbddefault] sections are
used to configure the behavior of the cluster's data nodes.
There are many parameters which control buffer sizes, pool
sizes, timeouts, and so forth. The only mandatory parameters
@@ -1288,15 +1288,15 @@
<para>
Either <literal>ExecuteOnComputer</literal> or
<literal>HostName</literal>, which must be defined in the
- local <literal>[NDBD]</literal> section.
+ local <literal>[ndbd]</literal> section.
</para>
</listitem>
<listitem>
<para>
The parameter <literal>NoOfReplicas</literal>, which must be
- defined in the [NDBD DEFAULT] section, as it is common to
- all Cluster data nodes.
+ defined in the [ndbddefault] section, as it is common to all
+ Cluster data nodes.
</para>
</listitem>
@@ -1304,12 +1304,12 @@
<para>
Most data node parameters are set in the <literal>[NDBD
- DEFAULT]</literal> section. Only those parameters explicitly
+ default]</literal> section. Only those parameters explicitly
stated as being able to set local values are allowed to be
- changed in the <literal>[NDBD]</literal> section. Where present,
+ changed in the <literal>[ndbd]</literal> section. Where present,
<literal>HostName</literal>, <literal>Id</literal> and
<literal>ExecuteOnComputer</literal> <emphasis>must</emphasis>
- be defined in the local <literal>[NDBD]</literal> section, and
+ be defined in the local <literal>[ndbd]</literal> section, and
not in any other section of <filename>config.ini</filename>. In
other words, settings for these parameters are specific to one
data node.
@@ -1366,7 +1366,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers defined in a <literal>[COMPUTER]</literal>
+ computers defined in a <literal>[computer]</literal>
section.
</para>
</listitem>
@@ -1445,7 +1445,7 @@
<para>
This global parameter can be set only in the <literal>[NDBD
- DEFAULT]</literal> section, and defines the number of
+ default]</literal> section, and defines the number of
replicas for each table stored in the cluster. This
parameter also specifies the size of node groups. A node
group is a set of nodes all storing the same information.
@@ -1569,7 +1569,7 @@
<para>
<literal>DataMemory</literal> and <literal>IndexMemory</literal>
- are <literal>[NDBD]</literal> parameters specifying the size of
+ are <literal>[ndbd]</literal> parameters specifying the size of
memory segments used to store the actual records and their
indexes. In setting values for these, it is important to
understand how <literal>DataMemory</literal> and
@@ -1764,8 +1764,8 @@
<para>
This parameter determines how much memory is allocated for
strings such as table names, and is specified in an
- <literal>[NDBD]</literal> or <literal>[NDBD
- DEFAULT]</literal> section of the
+ <literal>[ndbd]</literal> or <literal>[NDBD
+ default]</literal> section of the
<filename>config.ini</filename> file. A value between
<literal>0</literal> and <literal>100</literal> inclusive is
interpreted as a percent of the maximum default value, which
@@ -1896,7 +1896,7 @@
<title>Transaction parameters</title>
<para id="mysql-cluster-transaction-parameters">
- The next three <literal>[NDBD]</literal> parameters that we
+ The next three <literal>[ndbd]</literal> 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.
@@ -2080,7 +2080,7 @@
<title>Transaction temporary storage</title>
<para id="mysql-cluster-transaction-temporary-storage">
- The next set of <literal>[NDBD]</literal> parameters is used
+ 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
@@ -2205,7 +2205,7 @@
<title>Scans and buffering</title>
<para id="mysql-cluster-scans-and-buffering">
- There are additional <literal>[NDBD]</literal> parameters in
+ There are additional <literal>[ndbd]</literal> parameters in
the <literal>Dblqh</literal> module (in
<filename>ndb/src/kernel/blocks/Dblqh/Dblqh.hpp</filename>)
that affect reads and updates. These include
@@ -2358,7 +2358,7 @@
<title>Logging and checkpointing</title>
<para id="mysql-cluster-logging-and-checkpointing">
- These <literal>[NDBD]</literal> parameters control log and
+ These <literal>[ndbd]</literal> parameters control log and
checkpoint behavior.
</para>
@@ -2526,7 +2526,7 @@
<title>Metadata objects</title>
<para id="mysql-cluster-metadata-objects">
- The next set of <literal>[NDBD]</literal> parameters defines
+ The next set of <literal>[ndbd]</literal> parameters defines
pool sizes for metadata objects, used to define the maximum
number of attributes, tables, indexes, and trigger objects
used by indexes, events, and replication between clusters.
@@ -2725,7 +2725,7 @@
<para id="mysql-cluster-boolean-parameters">
The behavior of data nodes is also affected by a set of
- <literal>[NDBD]</literal> parameters taking on boolean values.
+ <literal>[ndbd]</literal> parameters taking on boolean values.
These parameters can each be specified as
<literal>TRUE</literal> by setting them equal to
<literal>1</literal> or <literal>Y</literal>, and as
@@ -2953,7 +2953,7 @@
</para>
<para>
- There are a number of <literal>[NDBD]</literal> parameters
+ There are a number of <literal>[ndbd]</literal> parameters
specifying timeouts and intervals between various actions in
Cluster data nodes. Most of the timeout values are specified in
milliseconds. Any exceptions to this are mentioned where
@@ -3662,7 +3662,7 @@
<title>Buffering and logging</title>
<para id="mysql-cluster-buffering-and-logging">
- Several <literal>[NDBD]</literal> configuration parameters
+ Several <literal>[ndbd]</literal> configuration parameters
enable the advanced user to have more control over the
resources used by node processes and to adjust various buffer
sizes at need.
@@ -4073,10 +4073,10 @@
<para>
<literal>MemReportFrequency</literal> is not a required
parameter. If used, it can be set for all cluster data nodes
- in the <literal>[NDBD DEFAULT]</literal> section of
+ in the <literal>[ndbddefault]</literal> section of
<filename>config.ini</filename>, and can also be set or
overridden for individual data nodes in the corresponding
- <literal>[NDBD]</literal> sections of the configuration
+ <literal>[ndbd]</literal> sections of the configuration
file. The minimum value — which is also the default
value — is 0, in which case memory reports are logged
only when memory usage reaches certain percentages (80%,
@@ -4097,7 +4097,7 @@
<title>Backup parameters</title>
<para id="mysql-cluster-backup-parameters">
- The <literal>[NDBD]</literal> parameters discussed in this
+ The <literal>[ndbd]</literal> parameters discussed in this
section define memory buffers set aside for execution of
online backups.
</para>
@@ -4316,7 +4316,7 @@
</para>
<para>
- The <literal>[NDBD]</literal> parameters discussed in this
+ The <literal>[ndbd]</literal> parameters discussed in this
section are used in scheduling and locking of threads to
specific CPUs on multiprocessor data node hosts. They were
introduced in MySQL 5.1.22-ndb-6.3.4.
@@ -4452,7 +4452,7 @@
</indexterm>
<para>
- The <literal>[MYSQLD]</literal> and <literal>[API]</literal>
+ The <literal>[mysqld]</literal> and <literal>[api]</literal>
sections in the <filename>config.ini</filename> file define the
behavior of the MySQL servers (SQL nodes) and other applications
(API nodes) used to access cluster data. None of the parameters
@@ -4461,13 +4461,13 @@
</para>
<para>
- Generally speaking, a <literal>[MYSQLD]</literal> section is
+ Generally speaking, a <literal>[mysqld]</literal> section is
used to indicate a MySQL server providing an SQL interface to
- the cluster, and an <literal>[API]</literal> section is used for
+ the cluster, and an <literal>[api]</literal> section is used for
applications other than <command>mysqld</command> processes
accessing cluster data, but the two designations are actually
synonomous; you can, for instance, list parameters for a MySQL
- server acting as an SQL node in an <literal>[API]</literal>
+ server acting as an SQL node in an <literal>[api]</literal>
section.
</para>
@@ -4501,7 +4501,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers (hosts) defined in a <literal>[COMPUTER]</literal>
+ computers (hosts) defined in a <literal>[computer]</literal>
section of the configuration file.
</para>
</listitem>
@@ -4700,7 +4700,7 @@
node and all MySQL server nodes, and between each data node and
the management server. (For one exception to this rule, see
<xref linkend="mysql-cluster-tcp-definition-direct"/>.)
- <literal>[TCP]</literal> sections in the
+ <literal>[tcp]</literal> sections in the
<filename>config.ini</filename> file explicitly define TCP/IP
connections between nodes in the cluster.
</para>
@@ -4714,10 +4714,10 @@
<important>
<para>
- Any <literal>[TCP]</literal> sections in the
+ Any <literal>[tcp]</literal> sections in the
<filename>config.ini</filename> file should be listed last,
following any other sections in the file. This is not required
- for a <literal>[TCP DEFAULT]</literal> section. This is a
+ for a <literal>[tcp default]</literal> section. This is a
known issue with the way in which the
<filename>config.ini</filename> file is read by the cluster
management server.
@@ -4727,7 +4727,7 @@
<para>
It is also possible to change the default values for these
parameters by setting them in the <literal>[TCP
- DEFAULT]</literal> section.
+ default]</literal> section.
</para>
<itemizedlist>
@@ -4739,7 +4739,7 @@
<para>
To identify a connection between two nodes it is necessary
- to provide their node IDs in the <literal>[TCP]</literal>
+ to provide their node IDs in the <literal>[tcp]</literal>
section of the configuration file. These are the same unique
<literal>Id</literal> values for each of these nodes as
described in <xref linkend="mysql-cluster-api-definition"/>.
@@ -4869,7 +4869,7 @@
<para>
Setting up a cluster using direct connections between data nodes
requires specifying explicitly the crossover IP addresses of the
- data nodes so connected in the <literal>[TCP]</literal> section
+ data nodes so connected in the <literal>[tcp]</literal> section
of the cluster <filename>config.ini</filename> file.
</para>
@@ -4886,26 +4886,26 @@
<programlisting>
# Management Server
-[NDB_MGMD]
+[ndb_mgmd]
Id=1
HostName=172.23.72.20
# SQL Node
-[MYSQLD]
+[mysqld]
Id=2
HostName=172.23.72.21
# Data Nodes
-[NDBD]
+[ndbd]
Id=3
HostName=172.23.72.22
-[NDBD]
+[ndbd]
Id=4
HostName=172.23.72.23
# TCP/IP Connections
-[TCP]
+[tcp]
NodeId1=3
NodeId2=4
HostName1=1.1.0.1
@@ -4959,7 +4959,7 @@
<para>
MySQL Cluster attempts to use the shared memory transporter and
configure it automatically where possible.
- <literal>[SHM]</literal> sections in the
+ <literal>[shm]</literal> sections in the
<filename>config.ini</filename> file explicitly define
shared-memory connections between nodes in the cluster. When
explicitly defining shared memory as the connection method, it
@@ -5110,7 +5110,7 @@
</indexterm>
<para>
- <literal>[SCI]</literal> sections in the
+ <literal>[sci]</literal> sections in the
<filename>config.ini</filename> file explicitly define SCI
(Scalable Coherent Interface) connections between cluster nodes.
Using SCI transporters in MySQL Cluster is supported only when
@@ -5436,7 +5436,7 @@
</indexterm>
<indexterm>
- <primary><literal>[NDBD]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[ndbd]</literal> (MySQL Cluster)</primary>
</indexterm>
<indexterm>
@@ -5445,7 +5445,7 @@
<para>
The following table provides information about parameters used
- in the <literal>[NDBD]</literal> or
+ in the <literal>[ndbd]</literal> or
<literal>[NDB_DEFAULT]</literal> sections of a
<filename>config.ini</filename> file for configuring MySQL
Cluster data nodes. For detailed descriptions and other
@@ -6263,16 +6263,16 @@
</indexterm>
<indexterm>
- <primary><literal>[NDB_MGMD]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[ndb_mgmd]</literal> (MySQL Cluster)</primary>
</indexterm>
<indexterm>
- <primary><literal>[MGM]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[mgm]</literal> (MySQL Cluster)</primary>
</indexterm>
<para>
The following table provides information about parameters used
- in the <literal>[NDB_MGMD]</literal> or <literal>[MGM]</literal>
+ in the <literal>[ndb_mgmd]</literal> or <literal>[mgm]</literal>
sections of a <filename>config.ini</filename> file for
configuring MySQL Cluster management nodes. For detailed
descriptions and other additional information about each of
@@ -6413,12 +6413,12 @@
</indexterm>
<indexterm>
- <primary><literal>[API]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[api]</literal> (MySQL Cluster)</primary>
</indexterm>
<para>
The following table provides information about parameters used
- in the <literal>[SQL]</literal> and <literal>[API]</literal>
+ in the <literal>[SQL]</literal> and <literal>[api]</literal>
sections of a <filename>config.ini</filename> file for
configuring MySQL Cluster SQL nodes and API nodes. For detailed
descriptions and other additional information about each of
Modified: trunk/refman-5.1/mysql-cluster-disk-data.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-disk-data.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.1/mysql-cluster-disk-data.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 3, Lines Added: 5, Lines Deleted: 5; 1618 bytes
@@ -526,7 +526,7 @@
<filename>config.ini</filename> includes the following:
<programlisting>
-[ndbd default]
+[ndbddefault]
DataDir= /data0
</programlisting>
@@ -724,8 +724,8 @@
<para>
This determines the amount of space used for caching pages
- on disk, and is set in the <literal>[NDBD]</literal> or
- <literal>[NDBD DEFAULT]</literal> section of the
+ on disk, and is set in the <literal>[ndbd]</literal> or
+ <literal>[ndbddefault]</literal> section of the
<filename>config.ini</filename> file. It is measured in
bytes. Each page takes up 32 KB. This means that Cluster
Disk Data storage always uses <replaceable>N</replaceable> *
@@ -748,8 +748,8 @@
buffers, disk operations (such as page requests and wait
queues), and metadata for tablespaces, log file groups,
<literal>UNDO</literal> files, and data files. It can be set
- in the <literal>[NDBD]</literal> or <literal>[NDBD
- DEFAULT]</literal> section of the
+ in the <literal>[ndbd]</literal> or <literal>[NDBD
+ default]</literal> section of the
<filename>config.ini</filename> configuration file, and is
measured in bytes.
</para>
Modified: trunk/refman-5.1/mysql-cluster-limitations.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-limitations.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.1/mysql-cluster-limitations.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 819 bytes
@@ -1431,7 +1431,7 @@
<emphasis>interfaces</emphasis> (such as Ethernet cards) for
a single data node, but these must be bound to the same
address. This also means that it not possible to use more
- than one <literal>[TCP]</literal> section per connection in
+ than one <literal>[tcp]</literal> section per connection in
the <literal>config.ini</literal> file. See
<xref linkend="mysql-cluster-tcp-definition"/>, for more
information.
Modified: trunk/refman-5.1/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-multi-computer.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.1/mysql-cluster-multi-computer.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 5, Lines Added: 10, Lines Deleted: 10; 3154 bytes
@@ -982,12 +982,12 @@
<programlisting>
# Options for mysqld process:
-[MYSQLD]
+[mysqld]
ndbcluster # run NDB storage engine
ndb-connectstring=192.168.0.10 # location of management server
# Options for ndbd process:
-[MYSQL_CLUSTER]
+[mysql_cluster]
ndb-connectstring=192.168.0.10 # location of management server
</programlisting>
@@ -1002,7 +1002,7 @@
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>
+ <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
@@ -1037,7 +1037,7 @@
<programlisting>
# Options affecting ndbd processes on all data nodes:
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas=2 # Number of replicas
DataMemory=80M # How much memory to allocate for data storage
IndexMemory=18M # How much memory to allocate for index storage
@@ -1047,7 +1047,7 @@
# this example Cluster setup.
# TCP/IP options:
-[TCP DEFAULT]
+[tcp default]
portnumber=2202 # This the default; however, you can use any
# port that is free for all the hosts in the cluster
# Note: It is recommended that you do not specify the
@@ -1055,23 +1055,23 @@
# used instead
# Management process options:
-[NDB_MGMD]
+[ndb_mgmd]
hostname=192.168.0.10 # Hostname or IP address of MGM node
datadir=/var/lib/mysql-cluster # Directory for MGM node log files
# Options for data node "A":
-[NDBD]
- # (one [NDBD] section per data node)
+[ndbd]
+ # (one [ndbd] section per data node)
hostname=192.168.0.30 # Hostname or IP address
datadir=/usr/local/mysql/data # Directory for this data node's data files
# Options for data node "B":
-[NDBD]
+[ndbd]
hostname=192.168.0.40 # Hostname or IP address
datadir=/usr/local/mysql/data # Directory for this data node's data files
# SQL node options:
-[MYSQLD]
+[mysqld]
hostname=192.168.0.20 # Hostname or IP address
# (additional mysqld connections can be
# specified for this node for various
Modified: trunk/refman-5.1/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-replication.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.1/mysql-cluster-replication.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 823 bytes
@@ -1724,7 +1724,7 @@
previously enabled on the master server, prior to
starting the replication process. This can be done by
including the following line in a
- <literal>[MYSQL_CLUSTER]</literal> section in the
+ <literal>[mysql_cluster]</literal> section in the
<filename>my.cnf file</filename>, where
<replaceable>management_host</replaceable> is the IP
address or hostname of the <literal>NDB</literal>
Modified: trunk/refman-5.2/mysql-cluster-backup.xml
===================================================================
--- trunk/refman-5.2/mysql-cluster-backup.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.2/mysql-cluster-backup.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 4; 1744 bytes
@@ -592,11 +592,11 @@
utility acts as a cluster API node, and so requires a free
connection <quote>slot</quote> to connect to the cluster
management server. This means that there must be at least one
- <literal>[API]</literal> or <literal>[MYSQLD]</literal>
+ <literal>[api]</literal> or <literal>[mysqld]</literal>
section that can be used by it in the cluster
<filename>config.ini</filename> file. It is a good idea to
- keep at least one empty <literal>[API]</literal> or
- <literal>[MYSQLD]</literal> section in
+ keep at least one empty <literal>[api]</literal> or
+ <literal>[mysqld]</literal> section in
<filename>config.ini</filename> that is not being used for a
MySQL server or other application for this reason (see
<xref linkend="mysql-cluster-api-definition"/>).
@@ -723,7 +723,7 @@
parallel, provided that there is a sufficient number of
cluster connections available. That is, when restoring to
multiple nodes in parallel, you must have an
- <literal>[API]</literal> or <literal>[MYSQLD]</literal>
+ <literal>[api]</literal> or <literal>[mysqld]</literal>
section in the cluster <filename>config.ini</filename> file
available for each concurrent <command>ndb_restore</command>
process. However, the data files must always be applied
Modified: trunk/refman-5.2/mysql-cluster-configuration.xml
===================================================================
--- trunk/refman-5.2/mysql-cluster-configuration.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.2/mysql-cluster-configuration.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 49, Lines Added: 83, Lines Deleted: 83; 23458 bytes
@@ -213,23 +213,23 @@
# Note: DB, API, and MGM are aliases for NDBD, MYSQLD, and NDB_MGMD
# respectively. DB and API are deprecated and should not be used in new
# installations.
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas= 1
-[MYSQLD DEFAULT]
-[NDB_MGMD DEFAULT]
-[TCP DEFAULT]
+[mysqld default]
+[NDB_MGMD default]
+[tcp default]
-[NDB_MGMD]
+[ndb_mgmd]
HostName= myhost.example.com
-[NDBD]
+[ndbd]
HostName= myhost.example.com
DataDir= /var/lib/mysql-cluster
-[MYSQLD]
-[MYSQLD]
-[MYSQLD]
+[mysqld]
+[mysqld]
+[mysqld]
</programlisting>
<para>
@@ -533,7 +533,7 @@
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>
+ <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
@@ -591,13 +591,13 @@
Default values are defined for most parameters, and can also be
specified in <filename>config.ini</filename>. To create a
default value section, simply add the word
- <literal>DEFAULT</literal> to the section name. For example, an
- <literal>[NDBD]</literal> section contains parameters that apply
+ <literal>default</literal> to the section name. For example, an
+ <literal>[ndbd]</literal> section contains parameters that apply
to a particular data node, whereas an <literal>[NDBD
- DEFAULT]</literal> section contains parameters that apply to all
+ default]</literal> section contains parameters that apply to all
data nodes. Suppose that all data nodes should use the same data
memory size. To configure them all, create an <literal>[NDBD
- DEFAULT]</literal> section that contains a
+ default]</literal> section that contains a
<literal>DataMemory</literal> line to specify the data memory
size.
</para>
@@ -617,22 +617,22 @@
# The first MySQL Server can be started from any host. The second
# can be started only on the host mysqld_5.mysql.com
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas= 2
DataDir= /var/lib/mysql-cluster
-[NDB_MGMD]
+[ndb_mgmd]
Hostname= ndb_mgmd.mysql.com
DataDir= /var/lib/mysql-cluster
-[NDBD]
+[ndbd]
HostName= ndbd_2.mysql.com
-[NDBD]
+[ndbd]
HostName= ndbd_3.mysql.com
-[MYSQLD]
-[MYSQLD]
+[mysqld]
+[mysqld]
HostName= mysqld_5.mysql.com
</programlisting>
@@ -640,7 +640,7 @@
Each node has its own section in the
<filename>config.ini</filename> file. For example, this cluster
has two data nodes, so the preceding configuration file contains
- two <literal>[NDBD]</literal> sections defining these nodes.
+ two <literal>[ndbd]</literal> sections defining these nodes.
</para>
<note>
@@ -667,7 +667,7 @@
<listitem>
<para>
- <literal>[COMPUTER]</literal>: Defines cluster hosts. This
+ <literal>[computer]</literal>: Defines cluster hosts. This
is not required to configure a viable MySQL Cluster, but be
may used as a convenience when setting up a large cluster.
See <xref linkend="mysql-cluster-computer-definition"/>, for
@@ -677,7 +677,7 @@
<listitem>
<para>
- <literal>[NDBD]</literal>: Defines a cluster data node
+ <literal>[ndbd]</literal>: Defines a cluster data node
(<command>ndbd</command> process). See
<xref linkend="mysql-cluster-ndbd-definition"/>, for
details.
@@ -686,7 +686,7 @@
<listitem>
<para>
- <literal>[MYSQLD]</literal>: Defines the cluster's MySQL
+ <literal>[mysqld]</literal>: Defines the cluster's MySQL
server nodes (also called SQL or API nodes). For a
discussion of SQL node configuration, see
<xref linkend="mysql-cluster-api-definition"/>.
@@ -695,7 +695,7 @@
<listitem>
<para>
- <literal>[MGM]</literal> or <literal>[NDB_MGMD]</literal>:
+ <literal>[mgm]</literal> or <literal>[ndb_mgmd]</literal>:
Defines a cluster management server (MGM) node. For
information concerning the configuration of MGM nodes, see
<xref linkend="mysql-cluster-mgm-definition"/>.
@@ -704,10 +704,10 @@
<listitem>
<para>
- <literal>[TCP]</literal>: Defines a TCP/IP connection
+ <literal>[tcp]</literal>: Defines a TCP/IP connection
between cluster nodes, with TCP/IP being the default
- connection protocol. Normally, <literal>[TCP]</literal> or
- <literal>[TCP DEFAULT]</literal> sections are not required
+ connection protocol. Normally, <literal>[tcp]</literal> or
+ <literal>[tcp default]</literal> sections are not required
to set up a MySQL Cluster, as the cluster handles this
automatically; however, it may be necessary in some
situations to override the defaults provided by the cluster.
@@ -721,7 +721,7 @@
<listitem>
<para>
- <literal>[SHM]</literal>: Defines shared-memory connections
+ <literal>[shm]</literal>: Defines shared-memory connections
between nodes. In MySQL ¤t-series;, it is enabled by
default, but should still be considered experimental. For a
discussion of SHM interconnects, see
@@ -731,7 +731,7 @@
<listitem>
<para>
- <literal>[SCI]</literal>:Defines <firstterm>Scalable
+ <literal>[sci]</literal>:Defines <firstterm>Scalable
Coherent Interface</firstterm> connections between cluster
data nodes. Such connections require software which, while
freely available, is not part of the MySQL Cluster
@@ -744,7 +744,7 @@
</itemizedlist>
<para>
- You can define <literal>DEFAULT</literal> values for each
+ You can define <literal>default</literal> values for each
section. All Cluster parameter names are case-insensitive, which
differs from parameters specified in <filename>my.cnf</filename>
or <filename>my.ini</filename> files.
@@ -903,7 +903,7 @@
</indexterm>
<para>
- The <literal>[COMPUTER]</literal> section has no real
+ The <literal>[computer]</literal> section has no real
significance other than serving as a way to avoid the need of
defining host names for each node in the system. All parameters
mentioned here are required.
@@ -952,8 +952,8 @@
</indexterm>
<para>
- The <literal>[NDB_MGMD]</literal> section is used to configure
- the behavior of the management server. <literal>[MGM]</literal>
+ The <literal>[ndb_mgmd]</literal> section is used to configure
+ the behavior of the management server. <literal>[mgm]</literal>
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.
@@ -997,7 +997,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers defined in a <literal>[COMPUTER]</literal> section
+ computers defined in a <literal>[computer]</literal> section
of the <filename>config.ini</filename> file.
</para>
</listitem>
@@ -1273,7 +1273,7 @@
</indexterm>
<para>
- The <literal>[NDBD]</literal> and [NDBD DEFAULT] sections are
+ The <literal>[ndbd]</literal> and [ndbddefault] sections are
used to configure the behavior of the cluster's data nodes.
There are many parameters which control buffer sizes, pool
sizes, timeouts, and so forth. The only mandatory parameters
@@ -1286,14 +1286,14 @@
<para>
Either <literal>ExecuteOnComputer</literal> or
<literal>HostName</literal>, which must be defined in the
- local <literal>[NDBD]</literal> section.
+ local <literal>[ndbd]</literal> section.
</para>
</listitem>
<listitem>
<para>
The parameter <literal>NoOfReplicas</literal>, which must be
- defined in the [NDBD DEFAULT] section, as it is common to
+ defined in the [ndbddefault] section, as it is common to
all Cluster data nodes.
</para>
</listitem>
@@ -1302,12 +1302,12 @@
<para>
Most data node parameters are set in the <literal>[NDBD
- DEFAULT]</literal> section. Only those parameters explicitly
+ default]</literal> section. Only those parameters explicitly
stated as being able to set local values are allowed to be
- changed in the <literal>[NDBD]</literal> section. Where present,
+ changed in the <literal>[ndbd]</literal> section. Where present,
<literal>HostName</literal>, <literal>Id</literal> and
<literal>ExecuteOnComputer</literal> <emphasis>must</emphasis>
- be defined in the local <literal>[NDBD]</literal> section, and
+ be defined in the local <literal>[ndbd]</literal> section, and
not in any other section of <filename>config.ini</filename>. In
other words, settings for these parameters are specific to one
data node.
@@ -1364,7 +1364,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers defined in a <literal>[COMPUTER]</literal>
+ computers defined in a <literal>[computer]</literal>
section.
</para>
</listitem>
@@ -1433,7 +1433,7 @@
<para>
This global parameter can be set only in the <literal>[NDBD
- DEFAULT]</literal> section, and defines the number of
+ default]</literal> section, and defines the number of
replicas for each table stored in the cluster. This
parameter also specifies the size of node groups. A node
group is a set of nodes all storing the same information.
@@ -1557,7 +1557,7 @@
<para>
<literal>DataMemory</literal> and <literal>IndexMemory</literal>
- are <literal>[NDBD]</literal> parameters specifying the size of
+ are <literal>[ndbd]</literal> parameters specifying the size of
memory segments used to store the actual records and their
indexes. In setting values for these, it is important to
understand how <literal>DataMemory</literal> and
@@ -1752,8 +1752,8 @@
<para>
This parameter determines how much memory is allocated for
strings such as table names, and is specified in an
- <literal>[NDBD]</literal> or <literal>[NDBD
- DEFAULT]</literal> section of the
+ <literal>[ndbd]</literal> or <literal>[NDBD
+ default]</literal> section of the
<filename>config.ini</filename> file. A value between
<literal>0</literal> and <literal>100</literal> inclusive is
interpreted as a percent of the maximum default value, which
@@ -1884,7 +1884,7 @@
<title>Transaction parameters</title>
<para id="mysql-cluster-transaction-parameters">
- The next three <literal>[NDBD]</literal> parameters that we
+ The next three <literal>[ndbd]</literal> 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.
@@ -2068,7 +2068,7 @@
<title>Transaction temporary storage</title>
<para id="mysql-cluster-transaction-temporary-storage">
- The next set of <literal>[NDBD]</literal> parameters is used
+ 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
@@ -2193,7 +2193,7 @@
<title>Scans and buffering</title>
<para id="mysql-cluster-scans-and-buffering">
- There are additional <literal>[NDBD]</literal> parameters in
+ There are additional <literal>[ndbd]</literal> parameters in
the <literal>Dblqh</literal> module (in
<filename>ndb/src/kernel/blocks/Dblqh/Dblqh.hpp</filename>)
that affect reads and updates. These include
@@ -2340,7 +2340,7 @@
<title>Logging and checkpointing</title>
<para id="mysql-cluster-logging-and-checkpointing">
- These <literal>[NDBD]</literal> parameters control log and
+ These <literal>[ndbd]</literal> parameters control log and
checkpoint behavior.
</para>
@@ -2502,7 +2502,7 @@
<title>Metadata objects</title>
<para id="mysql-cluster-metadata-objects">
- The next set of <literal>[NDBD]</literal> parameters defines
+ The next set of <literal>[ndbd]</literal> parameters defines
pool sizes for metadata objects, used to define the maximum
number of attributes, tables, indexes, and trigger objects
used by indexes, events, and replication between clusters.
@@ -2701,7 +2701,7 @@
<para id="mysql-cluster-boolean-parameters">
The behavior of data nodes is also affected by a set of
- <literal>[NDBD]</literal> parameters taking on boolean values.
+ <literal>[ndbd]</literal> parameters taking on boolean values.
These parameters can each be specified as
<literal>TRUE</literal> by setting them equal to
<literal>1</literal> or <literal>Y</literal>, and as
@@ -2927,7 +2927,7 @@
</para>
<para>
- There are a number of <literal>[NDBD]</literal> parameters
+ There are a number of <literal>[ndbd]</literal> parameters
specifying timeouts and intervals between various actions in
Cluster data nodes. Most of the timeout values are specified in
milliseconds. Any exceptions to this are mentioned where
@@ -3621,7 +3621,7 @@
<title>Buffering and logging</title>
<para id="mysql-cluster-buffering-and-logging">
- Several <literal>[NDBD]</literal> configuration parameters
+ Several <literal>[ndbd]</literal> configuration parameters
enable the advanced user to have more control over the
resources used by node processes and to adjust various buffer
sizes at need.
@@ -4032,10 +4032,10 @@
<para>
<literal>MemReportFrequency</literal> is not a required
parameter. If used, it can be set for all cluster data nodes
- in the <literal>[NDBD DEFAULT]</literal> section of
+ in the <literal>[ndbddefault]</literal> section of
<filename>config.ini</filename>, and can also be set or
overridden for individual data nodes in the corresponding
- <literal>[NDBD]</literal> sections of the configuration
+ <literal>[ndbd]</literal> sections of the configuration
file. The minimum value — which is also the default
value — is 0, in which case memory reports are logged
only when memory usage reaches certain percentages (80%,
@@ -4051,7 +4051,7 @@
<title>Backup parameters</title>
<para id="mysql-cluster-backup-parameters">
- The <literal>[NDBD]</literal> parameters discussed in this
+ The <literal>[ndbd]</literal> parameters discussed in this
section define memory buffers set aside for execution of
online backups.
</para>
@@ -4259,7 +4259,7 @@
</para>
<para>
- The <literal>[NDBD]</literal> parameters discussed in this
+ The <literal>[ndbd]</literal> parameters discussed in this
section are used in scheduling and locking of threads to
specific CPUs on multiprocessor data node hosts.
</para>
@@ -4394,7 +4394,7 @@
</indexterm>
<para>
- The <literal>[MYSQLD]</literal> and <literal>[API]</literal>
+ The <literal>[mysqld]</literal> and <literal>[api]</literal>
sections in the <filename>config.ini</filename> file define the
behavior of the MySQL servers (SQL nodes) and other applications
(API nodes) used to access cluster data. None of the parameters
@@ -4403,13 +4403,13 @@
</para>
<para>
- Generally speaking, a <literal>[MYSQLD]</literal> section is
+ Generally speaking, a <literal>[mysqld]</literal> section is
used to indicate a MySQL server providing an SQL interface to
- the cluster, and an <literal>[API]</literal> section is used for
+ the cluster, and an <literal>[api]</literal> section is used for
applications other than <command>mysqld</command> processes
accessing cluster data, but the two designations are actually
synonomous; you can, for instance, list parameters for a MySQL
- server acting as an SQL node in an <literal>[API]</literal>
+ server acting as an SQL node in an <literal>[api]</literal>
section.
</para>
@@ -4443,7 +4443,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers (hosts) defined in a <literal>[COMPUTER]</literal>
+ computers (hosts) defined in a <literal>[computer]</literal>
section of the configuration file.
</para>
</listitem>
@@ -4640,7 +4640,7 @@
node and all MySQL server nodes, and between each data node and
the management server. (For one exception to this rule, see
<xref linkend="mysql-cluster-tcp-definition-direct"/>.)
- <literal>[TCP]</literal> sections in the
+ <literal>[tcp]</literal> sections in the
<filename>config.ini</filename> file explicitly define TCP/IP
connections between nodes in the cluster.
</para>
@@ -4654,10 +4654,10 @@
<important>
<para>
- Any <literal>[TCP]</literal> sections in the
+ Any <literal>[tcp]</literal> sections in the
<filename>config.ini</filename> file should be listed last,
following any other sections in the file. This is not required
- for a <literal>[TCP DEFAULT]</literal> section. This is a
+ for a <literal>[tcp default]</literal> section. This is a
known issue with the way in which the
<filename>config.ini</filename> file is read by the cluster
management server.
@@ -4667,7 +4667,7 @@
<para>
It is also possible to change the default values for these
parameters by setting them in the <literal>[TCP
- DEFAULT]</literal> section.
+ default]</literal> section.
</para>
<itemizedlist>
@@ -4679,7 +4679,7 @@
<para>
To identify a connection between two nodes it is necessary
- to provide their node IDs in the <literal>[TCP]</literal>
+ to provide their node IDs in the <literal>[tcp]</literal>
section of the configuration file. These are the same unique
<literal>Id</literal> values for each of these nodes as
described in <xref linkend="mysql-cluster-api-definition"/>.
@@ -4809,7 +4809,7 @@
<para>
Setting up a cluster using direct connections between data nodes
requires specifying explicitly the crossover IP addresses of the
- data nodes so connected in the <literal>[TCP]</literal> section
+ data nodes so connected in the <literal>[tcp]</literal> section
of the cluster <filename>config.ini</filename> file.
</para>
@@ -4826,26 +4826,26 @@
<programlisting>
# Management Server
-[NDB_MGMD]
+[ndb_mgmd]
Id=1
HostName=172.23.72.20
# SQL Node
-[MYSQLD]
+[mysqld]
Id=2
HostName=172.23.72.21
# Data Nodes
-[NDBD]
+[ndbd]
Id=3
HostName=172.23.72.22
-[NDBD]
+[ndbd]
Id=4
HostName=172.23.72.23
# TCP/IP Connections
-[TCP]
+[tcp]
NodeId1=3
NodeId2=4
HostName1=1.1.0.1
@@ -4899,7 +4899,7 @@
<para>
MySQL Cluster attempts to use the shared memory transporter and
configure it automatically where possible.
- <literal>[SHM]</literal> sections in the
+ <literal>[shm]</literal> sections in the
<filename>config.ini</filename> file explicitly define
shared-memory connections between nodes in the cluster. When
explicitly defining shared memory as the connection method, it
@@ -5050,7 +5050,7 @@
</indexterm>
<para>
- <literal>[SCI]</literal> sections in the
+ <literal>[sci]</literal> sections in the
<filename>config.ini</filename> file explicitly define SCI
(Scalable Coherent Interface) connections between cluster nodes.
Using SCI transporters in MySQL Cluster is supported only when
@@ -5376,7 +5376,7 @@
</indexterm>
<indexterm>
- <primary><literal>[NDBD]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[ndbd]</literal> (MySQL Cluster)</primary>
</indexterm>
<indexterm>
@@ -5385,7 +5385,7 @@
<para>
The following table provides information about parameters used
- in the <literal>[NDBD]</literal> or
+ in the <literal>[ndbd]</literal> or
<literal>[NDB_DEFAULT]</literal> sections of a
<filename>config.ini</filename> file for configuring MySQL
Cluster data nodes. For detailed descriptions and other
@@ -6178,16 +6178,16 @@
</indexterm>
<indexterm>
- <primary><literal>[NDB_MGMD]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[ndb_mgmd]</literal> (MySQL Cluster)</primary>
</indexterm>
<indexterm>
- <primary><literal>[MGM]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[mgm]</literal> (MySQL Cluster)</primary>
</indexterm>
<para>
The following table provides information about parameters used
- in the <literal>[NDB_MGMD]</literal> or <literal>[MGM]</literal>
+ in the <literal>[ndb_mgmd]</literal> or <literal>[mgm]</literal>
sections of a <filename>config.ini</filename> file for
configuring MySQL Cluster management nodes. For detailed
descriptions and other additional information about each of
@@ -6328,12 +6328,12 @@
</indexterm>
<indexterm>
- <primary><literal>[API]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[api]</literal> (MySQL Cluster)</primary>
</indexterm>
<para>
The following table provides information about parameters used
- in the <literal>[SQL]</literal> and <literal>[API]</literal>
+ in the <literal>[SQL]</literal> and <literal>[api]</literal>
sections of a <filename>config.ini</filename> file for
configuring MySQL Cluster SQL nodes and API nodes. For detailed
descriptions and other additional information about each of
Modified: trunk/refman-5.2/mysql-cluster-disk-data.xml
===================================================================
--- trunk/refman-5.2/mysql-cluster-disk-data.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.2/mysql-cluster-disk-data.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 3, Lines Added: 5, Lines Deleted: 5; 1618 bytes
@@ -520,7 +520,7 @@
<filename>config.ini</filename> includes the following:
<programlisting>
-[ndbd default]
+[ndbddefault]
DataDir= /data0
</programlisting>
@@ -718,8 +718,8 @@
<para>
This determines the amount of space used for caching pages
- on disk, and is set in the <literal>[NDBD]</literal> or
- <literal>[NDBD DEFAULT]</literal> section of the
+ on disk, and is set in the <literal>[ndbd]</literal> or
+ <literal>[ndbddefault]</literal> section of the
<filename>config.ini</filename> file. It is measured in
bytes. Each page takes up 32 KB. This means that Cluster
Disk Data storage always uses <replaceable>N</replaceable> *
@@ -742,8 +742,8 @@
buffers, disk operations (such as page requests and wait
queues), and metadata for tablespaces, log file groups,
<literal>UNDO</literal> files, and data files. It can be set
- in the <literal>[NDBD]</literal> or <literal>[NDBD
- DEFAULT]</literal> section of the
+ in the <literal>[ndbd]</literal> or <literal>[NDBD
+ default]</literal> section of the
<filename>config.ini</filename> configuration file, and is
measured in bytes.
</para>
Modified: trunk/refman-5.2/mysql-cluster-limitations.xml
===================================================================
--- trunk/refman-5.2/mysql-cluster-limitations.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.2/mysql-cluster-limitations.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 819 bytes
@@ -1448,7 +1448,7 @@
<emphasis>interfaces</emphasis> (such as Ethernet cards) for
a single data node, but these must be bound to the same
address. This also means that it not possible to use more
- than one <literal>[TCP]</literal> section per connection in
+ than one <literal>[tcp]</literal> section per connection in
the <literal>config.ini</literal> file. See
<xref linkend="mysql-cluster-tcp-definition"/>, for more
information.
Modified: trunk/refman-5.2/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/refman-5.2/mysql-cluster-multi-computer.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.2/mysql-cluster-multi-computer.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 5, Lines Added: 10, Lines Deleted: 10; 3152 bytes
@@ -958,12 +958,12 @@
<programlisting>
# Options for mysqld process:
-[MYSQLD]
+[mysqld]
ndbcluster # run NDB storage engine
ndb-connectstring=192.168.0.10 # location of management server
# Options for ndbd process:
-[MYSQL_CLUSTER]
+[mysql_cluster]
ndb-connectstring=192.168.0.10 # location of management server
</programlisting>
@@ -978,7 +978,7 @@
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>
+ <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
@@ -1013,7 +1013,7 @@
<programlisting>
# Options affecting ndbd processes on all data nodes:
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas=2 # Number of replicas
DataMemory=80M # How much memory to allocate for data storage
IndexMemory=18M # How much memory to allocate for index storage
@@ -1023,7 +1023,7 @@
# this example Cluster setup.
# TCP/IP options:
-[TCP DEFAULT]
+[tcp default]
portnumber=2202 # This the default; however, you can use any
# port that is free for all the hosts in the cluster
# Note: It is recommended that you do not specify the
@@ -1031,23 +1031,23 @@
# used instead
# Management process options:
-[NDB_MGMD]
+[ndb_mgmd]
hostname=192.168.0.10 # Hostname or IP address of MGM node
datadir=/var/lib/mysql-cluster # Directory for MGM node log files
# Options for data node "A":
-[NDBD]
- # (one [NDBD] section per data node)
+[ndbd]
+ # (one [ndbd] section per data node)
hostname=192.168.0.30 # Hostname or IP address
datadir=/usr/local/mysql/data # Directory for this data node's data files
# Options for data node "B":
-[NDBD]
+[ndbd]
hostname=192.168.0.40 # Hostname or IP address
datadir=/usr/local/mysql/data # Directory for this data node's data files
# SQL node options:
-[MYSQLD]
+[mysqld]
hostname=192.168.0.20 # Hostname or IP address
# (additional mysqld connections can be
# specified for this node for various
Modified: trunk/refman-5.2/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-5.2/mysql-cluster-replication.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-5.2/mysql-cluster-replication.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 823 bytes
@@ -1680,7 +1680,7 @@
previously enabled on the master server, prior to
starting the replication process. This can be done by
including the following line in a
- <literal>[MYSQL_CLUSTER]</literal> section in the
+ <literal>[mysql_cluster]</literal> section in the
<filename>my.cnf file</filename>, where
<replaceable>management_host</replaceable> is the IP
address or hostname of the <literal>NDB</literal>
Modified: trunk/refman-6.0/mysql-cluster-backup.xml
===================================================================
--- trunk/refman-6.0/mysql-cluster-backup.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-6.0/mysql-cluster-backup.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 4; 1744 bytes
@@ -592,11 +592,11 @@
utility acts as a cluster API node, and so requires a free
connection <quote>slot</quote> to connect to the cluster
management server. This means that there must be at least one
- <literal>[API]</literal> or <literal>[MYSQLD]</literal>
+ <literal>[api]</literal> or <literal>[mysqld]</literal>
section that can be used by it in the cluster
<filename>config.ini</filename> file. It is a good idea to
- keep at least one empty <literal>[API]</literal> or
- <literal>[MYSQLD]</literal> section in
+ keep at least one empty <literal>[api]</literal> or
+ <literal>[mysqld]</literal> section in
<filename>config.ini</filename> that is not being used for a
MySQL server or other application for this reason (see
<xref linkend="mysql-cluster-api-definition"/>).
@@ -723,7 +723,7 @@
parallel, provided that there is a sufficient number of
cluster connections available. That is, when restoring to
multiple nodes in parallel, you must have an
- <literal>[API]</literal> or <literal>[MYSQLD]</literal>
+ <literal>[api]</literal> or <literal>[mysqld]</literal>
section in the cluster <filename>config.ini</filename> file
available for each concurrent <command>ndb_restore</command>
process. However, the data files must always be applied
Modified: trunk/refman-6.0/mysql-cluster-configuration.xml
===================================================================
--- trunk/refman-6.0/mysql-cluster-configuration.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-6.0/mysql-cluster-configuration.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 49, Lines Added: 84, Lines Deleted: 84; 23495 bytes
@@ -213,23 +213,23 @@
# Note: DB, API, and MGM are aliases for NDBD, MYSQLD, and NDB_MGMD
# respectively. DB and API are deprecated and should not be used in new
# installations.
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas= 1
-[MYSQLD DEFAULT]
-[NDB_MGMD DEFAULT]
-[TCP DEFAULT]
+[mysqld default]
+[NDB_MGMD default]
+[tcp default]
-[NDB_MGMD]
+[ndb_mgmd]
HostName= myhost.example.com
-[NDBD]
+[ndbd]
HostName= myhost.example.com
DataDir= /var/lib/mysql-cluster
-[MYSQLD]
-[MYSQLD]
-[MYSQLD]
+[mysqld]
+[mysqld]
+[mysqld]
</programlisting>
<para>
@@ -533,7 +533,7 @@
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>
+ <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
@@ -591,13 +591,13 @@
Default values are defined for most parameters, and can also be
specified in <filename>config.ini</filename>. To create a
default value section, simply add the word
- <literal>DEFAULT</literal> to the section name. For example, an
- <literal>[NDBD]</literal> section contains parameters that apply
+ <literal>default</literal> to the section name. For example, an
+ <literal>[ndbd]</literal> section contains parameters that apply
to a particular data node, whereas an <literal>[NDBD
- DEFAULT]</literal> section contains parameters that apply to all
+ default]</literal> section contains parameters that apply to all
data nodes. Suppose that all data nodes should use the same data
memory size. To configure them all, create an <literal>[NDBD
- DEFAULT]</literal> section that contains a
+ default]</literal> section that contains a
<literal>DataMemory</literal> line to specify the data memory
size.
</para>
@@ -617,22 +617,22 @@
# The first MySQL Server can be started from any host. The second
# can be started only on the host mysqld_5.mysql.com
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas= 2
DataDir= /var/lib/mysql-cluster
-[NDB_MGMD]
+[ndb_mgmd]
Hostname= ndb_mgmd.mysql.com
DataDir= /var/lib/mysql-cluster
-[NDBD]
+[ndbd]
HostName= ndbd_2.mysql.com
-[NDBD]
+[ndbd]
HostName= ndbd_3.mysql.com
-[MYSQLD]
-[MYSQLD]
+[mysqld]
+[mysqld]
HostName= mysqld_5.mysql.com
</programlisting>
@@ -640,7 +640,7 @@
Each node has its own section in the
<filename>config.ini</filename> file. For example, this cluster
has two data nodes, so the preceding configuration file contains
- two <literal>[NDBD]</literal> sections defining these nodes.
+ two <literal>[ndbd]</literal> sections defining these nodes.
</para>
<note>
@@ -667,7 +667,7 @@
<listitem>
<para>
- <literal>[COMPUTER]</literal>: Defines cluster hosts. This
+ <literal>[computer]</literal>: Defines cluster hosts. This
is not required to configure a viable MySQL Cluster, but be
may used as a convenience when setting up a large cluster.
See <xref linkend="mysql-cluster-computer-definition"/>, for
@@ -677,7 +677,7 @@
<listitem>
<para>
- <literal>[NDBD]</literal>: Defines a cluster data node
+ <literal>[ndbd]</literal>: Defines a cluster data node
(<command>ndbd</command> process). See
<xref linkend="mysql-cluster-ndbd-definition"/>, for
details.
@@ -686,7 +686,7 @@
<listitem>
<para>
- <literal>[MYSQLD]</literal>: Defines the cluster's MySQL
+ <literal>[mysqld]</literal>: Defines the cluster's MySQL
server nodes (also called SQL or API nodes). For a
discussion of SQL node configuration, see
<xref linkend="mysql-cluster-api-definition"/>.
@@ -695,7 +695,7 @@
<listitem>
<para>
- <literal>[MGM]</literal> or <literal>[NDB_MGMD]</literal>:
+ <literal>[mgm]</literal> or <literal>[ndb_mgmd]</literal>:
Defines a cluster management server (MGM) node. For
information concerning the configuration of MGM nodes, see
<xref linkend="mysql-cluster-mgm-definition"/>.
@@ -704,10 +704,10 @@
<listitem>
<para>
- <literal>[TCP]</literal>: Defines a TCP/IP connection
+ <literal>[tcp]</literal>: Defines a TCP/IP connection
between cluster nodes, with TCP/IP being the default
- connection protocol. Normally, <literal>[TCP]</literal> or
- <literal>[TCP DEFAULT]</literal> sections are not required
+ connection protocol. Normally, <literal>[tcp]</literal> or
+ <literal>[tcp default]</literal> sections are not required
to set up a MySQL Cluster, as the cluster handles this
automatically; however, it may be necessary in some
situations to override the defaults provided by the cluster.
@@ -721,7 +721,7 @@
<listitem>
<para>
- <literal>[SHM]</literal>: Defines shared-memory connections
+ <literal>[shm]</literal>: Defines shared-memory connections
between nodes. In MySQL ¤t-series;, it is enabled by
default, but should still be considered experimental. For a
discussion of SHM interconnects, see
@@ -731,7 +731,7 @@
<listitem>
<para>
- <literal>[SCI]</literal>:Defines <firstterm>Scalable
+ <literal>[sci]</literal>:Defines <firstterm>Scalable
Coherent Interface</firstterm> connections between cluster
data nodes. Such connections require software which, while
freely available, is not part of the MySQL Cluster
@@ -744,7 +744,7 @@
</itemizedlist>
<para>
- You can define <literal>DEFAULT</literal> values for each
+ You can define <literal>default</literal> values for each
section. All Cluster parameter names are case-insensitive, which
differs from parameters specified in <filename>my.cnf</filename>
or <filename>my.ini</filename> files.
@@ -903,7 +903,7 @@
</indexterm>
<para>
- The <literal>[COMPUTER]</literal> section has no real
+ The <literal>[computer]</literal> section has no real
significance other than serving as a way to avoid the need of
defining host names for each node in the system. All parameters
mentioned here are required.
@@ -952,8 +952,8 @@
</indexterm>
<para>
- The <literal>[NDB_MGMD]</literal> section is used to configure
- the behavior of the management server. <literal>[MGM]</literal>
+ The <literal>[ndb_mgmd]</literal> section is used to configure
+ the behavior of the management server. <literal>[mgm]</literal>
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.
@@ -997,7 +997,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers defined in a <literal>[COMPUTER]</literal> section
+ computers defined in a <literal>[computer]</literal> section
of the <filename>config.ini</filename> file.
</para>
</listitem>
@@ -1273,7 +1273,7 @@
</indexterm>
<para>
- The <literal>[NDBD]</literal> and [NDBD DEFAULT] sections are
+ The <literal>[ndbd]</literal> and [ndbddefault] sections are
used to configure the behavior of the cluster's data nodes.
There are many parameters which control buffer sizes, pool
sizes, timeouts, and so forth. The only mandatory parameters
@@ -1286,15 +1286,15 @@
<para>
Either <literal>ExecuteOnComputer</literal> or
<literal>HostName</literal>, which must be defined in the
- local <literal>[NDBD]</literal> section.
+ local <literal>[ndbd]</literal> section.
</para>
</listitem>
<listitem>
<para>
The parameter <literal>NoOfReplicas</literal>, which must be
- defined in the [NDBD DEFAULT] section, as it is common to
- all Cluster data nodes.
+ defined in the [ndbddefault] section, as it is common to all
+ Cluster data nodes.
</para>
</listitem>
@@ -1302,12 +1302,12 @@
<para>
Most data node parameters are set in the <literal>[NDBD
- DEFAULT]</literal> section. Only those parameters explicitly
+ default]</literal> section. Only those parameters explicitly
stated as being able to set local values are allowed to be
- changed in the <literal>[NDBD]</literal> section. Where present,
+ changed in the <literal>[ndbd]</literal> section. Where present,
<literal>HostName</literal>, <literal>Id</literal> and
<literal>ExecuteOnComputer</literal> <emphasis>must</emphasis>
- be defined in the local <literal>[NDBD]</literal> section, and
+ be defined in the local <literal>[ndbd]</literal> section, and
not in any other section of <filename>config.ini</filename>. In
other words, settings for these parameters are specific to one
data node.
@@ -1364,7 +1364,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers defined in a <literal>[COMPUTER]</literal>
+ computers defined in a <literal>[computer]</literal>
section.
</para>
</listitem>
@@ -1433,7 +1433,7 @@
<para>
This global parameter can be set only in the <literal>[NDBD
- DEFAULT]</literal> section, and defines the number of
+ default]</literal> section, and defines the number of
replicas for each table stored in the cluster. This
parameter also specifies the size of node groups. A node
group is a set of nodes all storing the same information.
@@ -1557,7 +1557,7 @@
<para>
<literal>DataMemory</literal> and <literal>IndexMemory</literal>
- are <literal>[NDBD]</literal> parameters specifying the size of
+ are <literal>[ndbd]</literal> parameters specifying the size of
memory segments used to store the actual records and their
indexes. In setting values for these, it is important to
understand how <literal>DataMemory</literal> and
@@ -1752,8 +1752,8 @@
<para>
This parameter determines how much memory is allocated for
strings such as table names, and is specified in an
- <literal>[NDBD]</literal> or <literal>[NDBD
- DEFAULT]</literal> section of the
+ <literal>[ndbd]</literal> or <literal>[NDBD
+ default]</literal> section of the
<filename>config.ini</filename> file. A value between
<literal>0</literal> and <literal>100</literal> inclusive is
interpreted as a percent of the maximum default value, which
@@ -1884,7 +1884,7 @@
<title>Transaction parameters</title>
<para id="mysql-cluster-transaction-parameters">
- The next three <literal>[NDBD]</literal> parameters that we
+ The next three <literal>[ndbd]</literal> 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.
@@ -2068,7 +2068,7 @@
<title>Transaction temporary storage</title>
<para id="mysql-cluster-transaction-temporary-storage">
- The next set of <literal>[NDBD]</literal> parameters is used
+ 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
@@ -2193,7 +2193,7 @@
<title>Scans and buffering</title>
<para id="mysql-cluster-scans-and-buffering">
- There are additional <literal>[NDBD]</literal> parameters in
+ There are additional <literal>[ndbd]</literal> parameters in
the <literal>Dblqh</literal> module (in
<filename>ndb/src/kernel/blocks/Dblqh/Dblqh.hpp</filename>)
that affect reads and updates. These include
@@ -2340,7 +2340,7 @@
<title>Logging and checkpointing</title>
<para id="mysql-cluster-logging-and-checkpointing">
- These <literal>[NDBD]</literal> parameters control log and
+ These <literal>[ndbd]</literal> parameters control log and
checkpoint behavior.
</para>
@@ -2502,7 +2502,7 @@
<title>Metadata objects</title>
<para id="mysql-cluster-metadata-objects">
- The next set of <literal>[NDBD]</literal> parameters defines
+ The next set of <literal>[ndbd]</literal> parameters defines
pool sizes for metadata objects, used to define the maximum
number of attributes, tables, indexes, and trigger objects
used by indexes, events, and replication between clusters.
@@ -2701,7 +2701,7 @@
<para id="mysql-cluster-boolean-parameters">
The behavior of data nodes is also affected by a set of
- <literal>[NDBD]</literal> parameters taking on boolean values.
+ <literal>[ndbd]</literal> parameters taking on boolean values.
These parameters can each be specified as
<literal>TRUE</literal> by setting them equal to
<literal>1</literal> or <literal>Y</literal>, and as
@@ -2927,7 +2927,7 @@
</para>
<para>
- There are a number of <literal>[NDBD]</literal> parameters
+ There are a number of <literal>[ndbd]</literal> parameters
specifying timeouts and intervals between various actions in
Cluster data nodes. Most of the timeout values are specified in
milliseconds. Any exceptions to this are mentioned where
@@ -3621,7 +3621,7 @@
<title>Buffering and logging</title>
<para id="mysql-cluster-buffering-and-logging">
- Several <literal>[NDBD]</literal> configuration parameters
+ Several <literal>[ndbd]</literal> configuration parameters
enable the advanced user to have more control over the
resources used by node processes and to adjust various buffer
sizes at need.
@@ -4032,10 +4032,10 @@
<para>
<literal>MemReportFrequency</literal> is not a required
parameter. If used, it can be set for all cluster data nodes
- in the <literal>[NDBD DEFAULT]</literal> section of
+ in the <literal>[ndbddefault]</literal> section of
<filename>config.ini</filename>, and can also be set or
overridden for individual data nodes in the corresponding
- <literal>[NDBD]</literal> sections of the configuration
+ <literal>[ndbd]</literal> sections of the configuration
file. The minimum value — which is also the default
value — is 0, in which case memory reports are logged
only when memory usage reaches certain percentages (80%,
@@ -4051,7 +4051,7 @@
<title>Backup parameters</title>
<para id="mysql-cluster-backup-parameters">
- The <literal>[NDBD]</literal> parameters discussed in this
+ The <literal>[ndbd]</literal> parameters discussed in this
section define memory buffers set aside for execution of
online backups.
</para>
@@ -4259,7 +4259,7 @@
</para>
<para>
- The <literal>[NDBD]</literal> parameters discussed in this
+ The <literal>[ndbd]</literal> parameters discussed in this
section are used in scheduling and locking of threads to
specific CPUs on multiprocessor data node hosts.
</para>
@@ -4394,7 +4394,7 @@
</indexterm>
<para>
- The <literal>[MYSQLD]</literal> and <literal>[API]</literal>
+ The <literal>[mysqld]</literal> and <literal>[api]</literal>
sections in the <filename>config.ini</filename> file define the
behavior of the MySQL servers (SQL nodes) and other applications
(API nodes) used to access cluster data. None of the parameters
@@ -4403,13 +4403,13 @@
</para>
<para>
- Generally speaking, a <literal>[MYSQLD]</literal> section is
+ Generally speaking, a <literal>[mysqld]</literal> section is
used to indicate a MySQL server providing an SQL interface to
- the cluster, and an <literal>[API]</literal> section is used for
+ the cluster, and an <literal>[api]</literal> section is used for
applications other than <command>mysqld</command> processes
accessing cluster data, but the two designations are actually
synonomous; you can, for instance, list parameters for a MySQL
- server acting as an SQL node in an <literal>[API]</literal>
+ server acting as an SQL node in an <literal>[api]</literal>
section.
</para>
@@ -4443,7 +4443,7 @@
<para>
This refers to the <literal>Id</literal> set for one of the
- computers (hosts) defined in a <literal>[COMPUTER]</literal>
+ computers (hosts) defined in a <literal>[computer]</literal>
section of the configuration file.
</para>
</listitem>
@@ -4640,7 +4640,7 @@
node and all MySQL server nodes, and between each data node and
the management server. (For one exception to this rule, see
<xref linkend="mysql-cluster-tcp-definition-direct"/>.)
- <literal>[TCP]</literal> sections in the
+ <literal>[tcp]</literal> sections in the
<filename>config.ini</filename> file explicitly define TCP/IP
connections between nodes in the cluster.
</para>
@@ -4654,10 +4654,10 @@
<important>
<para>
- Any <literal>[TCP]</literal> sections in the
+ Any <literal>[tcp]</literal> sections in the
<filename>config.ini</filename> file should be listed last,
following any other sections in the file. This is not required
- for a <literal>[TCP DEFAULT]</literal> section. This is a
+ for a <literal>[tcp default]</literal> section. This is a
known issue with the way in which the
<filename>config.ini</filename> file is read by the cluster
management server.
@@ -4667,7 +4667,7 @@
<para>
It is also possible to change the default values for these
parameters by setting them in the <literal>[TCP
- DEFAULT]</literal> section.
+ default]</literal> section.
</para>
<itemizedlist>
@@ -4679,7 +4679,7 @@
<para>
To identify a connection between two nodes it is necessary
- to provide their node IDs in the <literal>[TCP]</literal>
+ to provide their node IDs in the <literal>[tcp]</literal>
section of the configuration file. These are the same unique
<literal>Id</literal> values for each of these nodes as
described in <xref linkend="mysql-cluster-api-definition"/>.
@@ -4809,7 +4809,7 @@
<para>
Setting up a cluster using direct connections between data nodes
requires specifying explicitly the crossover IP addresses of the
- data nodes so connected in the <literal>[TCP]</literal> section
+ data nodes so connected in the <literal>[tcp]</literal> section
of the cluster <filename>config.ini</filename> file.
</para>
@@ -4826,26 +4826,26 @@
<programlisting>
# Management Server
-[NDB_MGMD]
+[ndb_mgmd]
Id=1
HostName=172.23.72.20
# SQL Node
-[MYSQLD]
+[mysqld]
Id=2
HostName=172.23.72.21
# Data Nodes
-[NDBD]
+[ndbd]
Id=3
HostName=172.23.72.22
-[NDBD]
+[ndbd]
Id=4
HostName=172.23.72.23
# TCP/IP Connections
-[TCP]
+[tcp]
NodeId1=3
NodeId2=4
HostName1=1.1.0.1
@@ -4899,7 +4899,7 @@
<para>
MySQL Cluster attempts to use the shared memory transporter and
configure it automatically where possible.
- <literal>[SHM]</literal> sections in the
+ <literal>[shm]</literal> sections in the
<filename>config.ini</filename> file explicitly define
shared-memory connections between nodes in the cluster. When
explicitly defining shared memory as the connection method, it
@@ -5050,7 +5050,7 @@
</indexterm>
<para>
- <literal>[SCI]</literal> sections in the
+ <literal>[sci]</literal> sections in the
<filename>config.ini</filename> file explicitly define SCI
(Scalable Coherent Interface) connections between cluster nodes.
Using SCI transporters in MySQL Cluster is supported only when
@@ -5376,7 +5376,7 @@
</indexterm>
<indexterm>
- <primary><literal>[NDBD]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[ndbd]</literal> (MySQL Cluster)</primary>
</indexterm>
<indexterm>
@@ -5385,7 +5385,7 @@
<para>
The following table provides information about parameters used
- in the <literal>[NDBD]</literal> or
+ in the <literal>[ndbd]</literal> or
<literal>[NDB_DEFAULT]</literal> sections of a
<filename>config.ini</filename> file for configuring MySQL
Cluster data nodes. For detailed descriptions and other
@@ -6178,16 +6178,16 @@
</indexterm>
<indexterm>
- <primary><literal>[NDB_MGMD]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[ndb_mgmd]</literal> (MySQL Cluster)</primary>
</indexterm>
<indexterm>
- <primary><literal>[MGM]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[mgm]</literal> (MySQL Cluster)</primary>
</indexterm>
<para>
The following table provides information about parameters used
- in the <literal>[NDB_MGMD]</literal> or <literal>[MGM]</literal>
+ in the <literal>[ndb_mgmd]</literal> or <literal>[mgm]</literal>
sections of a <filename>config.ini</filename> file for
configuring MySQL Cluster management nodes. For detailed
descriptions and other additional information about each of
@@ -6328,12 +6328,12 @@
</indexterm>
<indexterm>
- <primary><literal>[API]</literal> (MySQL Cluster)</primary>
+ <primary><literal>[api]</literal> (MySQL Cluster)</primary>
</indexterm>
<para>
The following table provides information about parameters used
- in the <literal>[SQL]</literal> and <literal>[API]</literal>
+ in the <literal>[SQL]</literal> and <literal>[api]</literal>
sections of a <filename>config.ini</filename> file for
configuring MySQL Cluster SQL nodes and API nodes. For detailed
descriptions and other additional information about each of
Modified: trunk/refman-6.0/mysql-cluster-disk-data.xml
===================================================================
--- trunk/refman-6.0/mysql-cluster-disk-data.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-6.0/mysql-cluster-disk-data.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 3, Lines Added: 5, Lines Deleted: 5; 1618 bytes
@@ -520,7 +520,7 @@
<filename>config.ini</filename> includes the following:
<programlisting>
-[ndbd default]
+[ndbddefault]
DataDir= /data0
</programlisting>
@@ -718,8 +718,8 @@
<para>
This determines the amount of space used for caching pages
- on disk, and is set in the <literal>[NDBD]</literal> or
- <literal>[NDBD DEFAULT]</literal> section of the
+ on disk, and is set in the <literal>[ndbd]</literal> or
+ <literal>[ndbddefault]</literal> section of the
<filename>config.ini</filename> file. It is measured in
bytes. Each page takes up 32 KB. This means that Cluster
Disk Data storage always uses <replaceable>N</replaceable> *
@@ -742,8 +742,8 @@
buffers, disk operations (such as page requests and wait
queues), and metadata for tablespaces, log file groups,
<literal>UNDO</literal> files, and data files. It can be set
- in the <literal>[NDBD]</literal> or <literal>[NDBD
- DEFAULT]</literal> section of the
+ in the <literal>[ndbd]</literal> or <literal>[NDBD
+ default]</literal> section of the
<filename>config.ini</filename> configuration file, and is
measured in bytes.
</para>
Modified: trunk/refman-6.0/mysql-cluster-limitations.xml
===================================================================
--- trunk/refman-6.0/mysql-cluster-limitations.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-6.0/mysql-cluster-limitations.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 819 bytes
@@ -1448,7 +1448,7 @@
<emphasis>interfaces</emphasis> (such as Ethernet cards) for
a single data node, but these must be bound to the same
address. This also means that it not possible to use more
- than one <literal>[TCP]</literal> section per connection in
+ than one <literal>[tcp]</literal> section per connection in
the <literal>config.ini</literal> file. See
<xref linkend="mysql-cluster-tcp-definition"/>, for more
information.
Modified: trunk/refman-6.0/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/refman-6.0/mysql-cluster-multi-computer.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-6.0/mysql-cluster-multi-computer.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 5, Lines Added: 10, Lines Deleted: 10; 3152 bytes
@@ -958,12 +958,12 @@
<programlisting>
# Options for mysqld process:
-[MYSQLD]
+[mysqld]
ndbcluster # run NDB storage engine
ndb-connectstring=192.168.0.10 # location of management server
# Options for ndbd process:
-[MYSQL_CLUSTER]
+[mysql_cluster]
ndb-connectstring=192.168.0.10 # location of management server
</programlisting>
@@ -978,7 +978,7 @@
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>
+ <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
@@ -1013,7 +1013,7 @@
<programlisting>
# Options affecting ndbd processes on all data nodes:
-[NDBD DEFAULT]
+[ndbddefault]
NoOfReplicas=2 # Number of replicas
DataMemory=80M # How much memory to allocate for data storage
IndexMemory=18M # How much memory to allocate for index storage
@@ -1023,7 +1023,7 @@
# this example Cluster setup.
# TCP/IP options:
-[TCP DEFAULT]
+[tcp default]
portnumber=2202 # This the default; however, you can use any
# port that is free for all the hosts in the cluster
# Note: It is recommended that you do not specify the
@@ -1031,23 +1031,23 @@
# used instead
# Management process options:
-[NDB_MGMD]
+[ndb_mgmd]
hostname=192.168.0.10 # Hostname or IP address of MGM node
datadir=/var/lib/mysql-cluster # Directory for MGM node log files
# Options for data node "A":
-[NDBD]
- # (one [NDBD] section per data node)
+[ndbd]
+ # (one [ndbd] section per data node)
hostname=192.168.0.30 # Hostname or IP address
datadir=/usr/local/mysql/data # Directory for this data node's data files
# Options for data node "B":
-[NDBD]
+[ndbd]
hostname=192.168.0.40 # Hostname or IP address
datadir=/usr/local/mysql/data # Directory for this data node's data files
# SQL node options:
-[MYSQLD]
+[mysqld]
hostname=192.168.0.20 # Hostname or IP address
# (additional mysqld connections can be
# specified for this node for various
Modified: trunk/refman-6.0/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-6.0/mysql-cluster-replication.xml 2007-10-31 10:21:18 UTC (rev 8425)
+++ trunk/refman-6.0/mysql-cluster-replication.xml 2007-10-31 11:27:01 UTC (rev 8426)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 823 bytes
@@ -1680,7 +1680,7 @@
previously enabled on the master server, prior to
starting the replication process. This can be done by
including the following line in a
- <literal>[MYSQL_CLUSTER]</literal> section in the
+ <literal>[mysql_cluster]</literal> section in the
<filename>my.cnf file</filename>, where
<replaceable>management_host</replaceable> is the IP
address or hostname of the <literal>NDB</literal>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8426 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-5.2 refman-6.0 | jon | 31 Oct |
