Author: jstephens
Date: 2006-04-05 13:33:32 +0200 (Wed, 05 Apr 2006)
New Revision: 1724
Log:
"Storage nodes" -> "data nodes".
Modified:
trunk/refman-4.1/ndbcluster.xml
trunk/refman-5.0/ndbcluster.xml
trunk/refman-5.1/ndbcluster.xml
Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml 2006-04-05 11:19:57 UTC (rev 1723)
+++ trunk/refman-4.1/ndbcluster.xml 2006-04-05 11:33:32 UTC (rev 1724)
@@ -272,7 +272,7 @@
Configuration of a cluster involves configuring each individual
node in the cluster and setting up individual communication links
between nodes. MySQL Cluster is currently designed with the
- intention that storage nodes are homogeneous in terms of processor
+ intention that data nodes are homogeneous in terms of processor
power, memory space, and bandwidth. In addition, to provide a
single point of configuration, all configuration data for the
cluster as a whole is located in one configuration file.
@@ -1595,7 +1595,7 @@
<para>
Applications that use MySQL can employ standard APIs to access
NDB tables. It is important to remember that your application
- must access the SQL node, and not the MGM or storage nodes. This
+ must access the SQL node, and not the MGM or data nodes. This
brief example shows how we might execute the
<literal>SELECT</literal> statement just shown by using PHP 5's
<literal>mysqli</literal> extension running on a Web server
@@ -4089,7 +4089,7 @@
<para>
This parameter specifies how long the Cluster waits for
- all storage nodes to come up before the cluster
+ all data nodes to come up before the cluster
initialization routine is invoked. This timeout is used to
avoid a partial Cluster startup whenever possible.
</para>
@@ -4134,7 +4134,7 @@
The default value is 60000 milliseconds (60 seconds). For
data nodes containing extremely large amounts of data,
this parameter should be increased. For example, in the
- case of a storage node containing several gigabytes of
+ case of a data node containing several gigabytes of
data, a period as long as 10−15 minutes (that is,
600,000 to 1,000,000 milliseconds) might be required to to
perform a node restart.
@@ -4188,7 +4188,7 @@
<para>
The default interval is 1500 milliseconds (1.5 seconds).
This interval can vary between individual data nodes
- because each storage node watches the MySQL servers
+ because each data node watches the MySQL servers
connected to it, independently of all other data nodes.
</para>
</listitem>
@@ -5681,7 +5681,7 @@
<para>
<command>ndbd</command> is the process that is used to handle
all the data in tables using the NDB Cluster storage engine.
- This is the process that empowers a storage node to accomplish
+ This is the process that empowers a data node to accomplish
distributed transaction handling, node recovery, checkpointing
to disk, online backup, and related tasks.
</para>
@@ -5715,7 +5715,7 @@
identifier.Note that <replaceable>node_id</replaceable>
represents the node's unique identifier. For example,
<filename>ndb_2_error.log</filename> is the error log generated
- by the storage node whose node ID is <literal>2</literal>.
+ by the data node whose node ID is <literal>2</literal>.
</para>
<itemizedlist>
@@ -9734,7 +9734,7 @@
<emphasis role="bold">recommended</emphasis> number of
computers in a MySQL Cluster is four: one each to run the
management and SQL nodes, and two computers to serve as
- storage nodes. The purpose of the two data nodes is to provide
+ data nodes. The purpose of the two data nodes is to provide
redundancy; the management node must run on a separate machine
to guarantee continued arbitration services in the event that
one of the data nodes fails.
@@ -10897,17 +10897,16 @@
<emphasis>node</emphasis> is a logical or functional component
(that is, a process).
</para>
-
+
<para>
- <emphasis role="bold">Note Regarding Obsolete
- Terms</emphasis>: In older versions of the MySQL Cluster
- documentation, data nodes were sometimes referred to as
- <quote>database nodes,</quote> <quote>DB nodes,</quote> or
- occasionally <quote>storage nodes.</quote> In addition, SQL
- nodes were sometimes known as <quote>client nodes</quote> or
- <quote>API nodes.</quote> This older terminology has been
- deprecated to minimize confusion, and for these reasons should
- be avoided.
+ <emphasis role="bold">Note Regarding Terms</emphasis>: In
+ older versions of the MySQL Cluster documentation, data nodes
+ were sometimes referred to as <quote>database nodes</quote> or
+ <quote>DB nodes</quote>. The term <quote>storage nodes</quote>
+ has also been used. In addition, SQL nodes were sometimes
+ known as <quote>client nodes</quote> or <quote>API
+ nodes</quote>. This older terminology has been deprecated to
+ minimize confusion, and for these reasons should be avoided.
</para>
</listitem>
Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml 2006-04-05 11:19:57 UTC (rev 1723)
+++ trunk/refman-5.0/ndbcluster.xml 2006-04-05 11:33:32 UTC (rev 1724)
@@ -272,7 +272,7 @@
Configuration of a cluster involves configuring each individual
node in the cluster and setting up individual communication links
between nodes. MySQL Cluster is currently designed with the
- intention that storage nodes are homogeneous in terms of processor
+ intention that data nodes are homogeneous in terms of processor
power, memory space, and bandwidth. In addition, to provide a
single point of configuration, all configuration data for the
cluster as a whole is located in one configuration file.
@@ -1597,7 +1597,7 @@
<para>
Applications that use MySQL can employ standard APIs to access
NDB tables. It is important to remember that your application
- must access the SQL node, and not the MGM or storage nodes. This
+ must access the SQL node, and not the MGM or data nodes. This
brief example shows how we might execute the
<literal>SELECT</literal> statement just shown by using PHP 5's
<literal>mysqli</literal> extension running on a Web server
@@ -4097,7 +4097,7 @@
<para>
This parameter specifies how long the Cluster waits for
- all storage nodes to come up before the cluster
+ all data nodes to come up before the cluster
initialization routine is invoked. This timeout is used to
avoid a partial Cluster startup whenever possible.
</para>
@@ -4142,7 +4142,7 @@
The default value is 60000 milliseconds (60 seconds). For
data nodes containing extremely large amounts of data,
this parameter should be increased. For example, in the
- case of a storage node containing several gigabytes of
+ case of a data node containing several gigabytes of
data, a period as long as 10−15 minutes (that is,
600,000 to 1,000,000 milliseconds) might be required to to
perform a node restart.
@@ -4196,7 +4196,7 @@
<para>
The default interval is 1500 milliseconds (1.5 seconds).
This interval can vary between individual data nodes
- because each storage node watches the MySQL servers
+ because each data node watches the MySQL servers
connected to it, independently of all other data nodes.
</para>
</listitem>
@@ -5688,7 +5688,7 @@
<para>
<command>ndbd</command> is the process that is used to handle
all the data in tables using the NDB Cluster storage engine.
- This is the process that empowers a storage node to accomplish
+ This is the process that empowers a data node to accomplish
distributed transaction handling, node recovery, checkpointing
to disk, online backup, and related tasks.
</para>
@@ -5712,7 +5712,7 @@
log files are listed below. Note that
<replaceable>node_id</replaceable> represents the node's unique
identifier. For example, <filename>ndb_2_error.log</filename> is
- the error log generated by the storage node whose node ID is
+ the error log generated by the data node whose node ID is
<literal>2</literal>.
</para>
@@ -10024,7 +10024,7 @@
<emphasis role="bold">recommended</emphasis> number of
computers in a MySQL Cluster is four: one each to run the
management and SQL nodes, and two computers to serve as
- storage nodes. The purpose of the two data nodes is to provide
+ data nodes. The purpose of the two data nodes is to provide
redundancy; the management node must run on a separate machine
to guarantee continued arbitration services in the event that
one of the data nodes fails.
@@ -11195,17 +11195,16 @@
<emphasis>node</emphasis> is a logical or functional component
(that is, a process).
</para>
-
+
<para>
- <emphasis role="bold">Note Regarding Obsolete
- Terms</emphasis>: In older versions of the MySQL Cluster
- documentation, data nodes were sometimes referred to as
- <quote>database nodes,</quote> <quote>DB nodes,</quote> or
- occasionally <quote>storage nodes.</quote> In addition, SQL
- nodes were sometimes known as <quote>client nodes</quote> or
- <quote>API nodes.</quote> This older terminology has been
- deprecated to minimize confusion, and for these reasons should
- be avoided.
+ <emphasis role="bold">Note Regarding Terms</emphasis>: In
+ older versions of the MySQL Cluster documentation, data nodes
+ were sometimes referred to as <quote>database nodes</quote> or
+ <quote>DB nodes</quote>. The term <quote>storage nodes</quote>
+ has also been used. In addition, SQL nodes were sometimes
+ known as <quote>client nodes</quote> or <quote>API
+ nodes</quote>. This older terminology has been deprecated to
+ minimize confusion, and for these reasons should be avoided.
</para>
</listitem>
Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml 2006-04-05 11:19:57 UTC (rev 1723)
+++ trunk/refman-5.1/ndbcluster.xml 2006-04-05 11:33:32 UTC (rev 1724)
@@ -269,7 +269,7 @@
Configuration of a cluster involves configuring each individual
node in the cluster and setting up individual communication links
between nodes. MySQL Cluster is currently designed with the
- intention that storage nodes are homogeneous in terms of processor
+ intention that data nodes are homogeneous in terms of processor
power, memory space, and bandwidth. In addition, to provide a
single point of configuration, all configuration data for the
cluster as a whole is located in one configuration file.
@@ -1579,7 +1579,7 @@
<para>
Applications that use MySQL can employ standard APIs to access
NDB tables. It is important to remember that your application
- must access the SQL node, and not the MGM or storage nodes. This
+ must access the SQL node, and not the MGM or data nodes. This
brief example shows how we might execute the
<literal>SELECT</literal> statement just shown by using PHP 5's
<literal>mysqli</literal> extension running on a Web server
@@ -4076,7 +4076,7 @@
<para>
This parameter specifies how long the Cluster waits for
- all storage nodes to come up before the cluster
+ all data nodes to come up before the cluster
initialization routine is invoked. This timeout is used to
avoid a partial Cluster startup whenever possible.
</para>
@@ -4121,7 +4121,7 @@
The default value is 60000 milliseconds (60 seconds). For
data nodes containing extremely large amounts of data,
this parameter should be increased. For example, in the
- case of a storage node containing several gigabytes of
+ case of a data node containing several gigabytes of
data, a period as long as 10−15 minutes (that is,
600,000 to 1,000,000 milliseconds) might be required to to
perform a node restart.
@@ -4175,7 +4175,7 @@
<para>
The default interval is 1500 milliseconds (1.5 seconds).
This interval can vary between individual data nodes
- because each storage node watches the MySQL servers
+ because each data node watches the MySQL servers
connected to it, independently of all other data nodes.
</para>
</listitem>
@@ -5667,7 +5667,7 @@
<para>
<command>ndbd</command> is the process that is used to handle
all the data in tables using the NDB Cluster storage engine.
- This is the process that empowers a storage node to accomplish
+ This is the process that empowers a data node to accomplish
distributed transaction handling, node recovery, checkpointing
to disk, online backup, and related tasks.
</para>
@@ -5691,7 +5691,7 @@
log files are listed below. Note that
<replaceable>node_id</replaceable> represents the node's unique
identifier. For example, <filename>ndb_2_error.log</filename> is
- the error log generated by the storage node whose node ID is
+ the error log generated by the data node whose node ID is
<literal>2</literal>.
</para>
@@ -9776,7 +9776,7 @@
the cluster must be made aware of the change. When a database
is created or dropped, the appropriate <literal>CREATE
SCHEMA</literal> or <literal>DROP SCHEMA</literal> statement
- should be issued on each storage node in the cluster to induce
+ should be issued on each data node in the cluster to induce
discovery of the change, that is:
</para>
@@ -11985,7 +11985,7 @@
<emphasis role="bold">recommended</emphasis> number of
computers in a MySQL Cluster is four: one each to run the
management and SQL nodes, and two computers to serve as
- storage nodes. The purpose of the two data nodes is to provide
+ data nodes. The purpose of the two data nodes is to provide
redundancy; the management node must run on a separate machine
to guarantee continued arbitration services in the event that
one of the data nodes fails.
@@ -13158,17 +13158,16 @@
<emphasis>node</emphasis> is a logical or functional component
(that is, a process).
</para>
-
+
<para>
- <emphasis role="bold">Note Regarding Obsolete
- Terms</emphasis>: In older versions of the MySQL Cluster
- documentation, data nodes were sometimes referred to as
- <quote>database nodes,</quote> <quote>DB nodes,</quote> or
- occasionally <quote>storage nodes.</quote> In addition, SQL
- nodes were sometimes known as <quote>client nodes</quote> or
- <quote>API nodes.</quote> This older terminology has been
- deprecated to minimize confusion, and for these reasons should
- be avoided.
+ <emphasis role="bold">Note Regarding Terms</emphasis>: In
+ older versions of the MySQL Cluster documentation, data nodes
+ were sometimes referred to as <quote>database nodes</quote> or
+ <quote>DB nodes</quote>. The term <quote>storage nodes</quote>
+ has also been used. In addition, SQL nodes were sometimes
+ known as <quote>client nodes</quote> or <quote>API
+ nodes</quote>. This older terminology has been deprecated to
+ minimize confusion, and for these reasons should be avoided.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1724 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 5 Apr |
