Author: jstephens
Date: 2006-02-01 04:26:29 +0100 (Wed, 01 Feb 2006)
New Revision: 1162
Log:
Fixed some msic. issues in Cluster chapter. (Thanks, Paul!)
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-02-01 02:02:30 UTC (rev 1161)
+++ trunk/refman-4.1/ndbcluster.xml 2006-02-01 03:26:29 UTC (rev 1162)
@@ -547,10 +547,12 @@
<para>
This section is a <quote>How-To</quote> that describes the basics
for how to plan, install, configure, and run a MySQL Cluster.
- Unlike the example in
- <xref linkend="mysql-cluster-configuration"/>, the result of
- following the guidelines and procedures outlined here should be a
- usable MySQL Cluster which meets minimum requirements for
+ Whereas the examples in
+ <xref linkend="mysql-cluster-configuration"/> provide more
+ in-depth information on a variety of clustering options and
+ configuration, the result of following the guidelines and
+ procedures outlined here should be a usable MySQL Cluster which
+ meets the <emphasis>minimum</emphasis> requirements for
availability and safeguarding of data.
</para>
@@ -638,11 +640,11 @@
Each host in our scenario is an Intel-based desktop PC running
a common, generic Linux distribution installed to disk in a
standard configuration, and running no unnecessary services.
- The core OS with a standard TCP/IP networking client should be
- sufficient. Also for the sake of simplicity, we also assume
- that the filesystems on all hosts are set up identically. In
- the event that they are not, you will need to adapt these
- instructions accordingly.
+ The core OS with standard TCP/IP networking capabilities
+ should be sufficient. Also for the sake of simplicity, we also
+ assume that the filesystems on all hosts are set up
+ identically. In the event that they are not, you will need to
+ adapt these instructions accordingly.
</para>
</listitem>
@@ -1419,7 +1421,8 @@
that is to be part of the clustered database. The easiest
way to accomplish this is to do a search-and-replace on the
<filename>world.sql</filename> file and replace all
- instances of <literal>TYPE=MyISAM</literal> with
+ instances of <literal>TYPE=MyISAM</literal> or
+ <literal>ENGINE=MyISAM</literal> with
<literal>ENGINE=NDBCLUSTER</literal>. If you do not want to
modify the file, you can also use <literal>ALTER
TABLE</literal> to change their type. The particulars are
@@ -7113,11 +7116,12 @@
</informaltable>
<para>
- Event severity levels can be turned on or off. If a severity
- level is turned on, all events with a priority less than or
- equal to the category thresholds are logged. If the severity
- level is turned off then no events belonging to that severity
- level are logged.
+ Event severity levels can be turned on or off (using
+ <literal>CLUSTERLOG FILTER</literal> — see above). If a
+ severity level is turned on, then all events with a priority
+ less than or equal to the category thresholds are logged. If
+ the severity level is turned off then no events belonging to
+ that severity level are logged.
</para>
<remark role="todo">
@@ -9010,9 +9014,9 @@
There are several other optimized socket implementations for
computer clusters, including Myrinet, Gigabit Ethernet,
Infiniband and the VIA interface. We have tested MySQL Cluster
- so far only with SCI sockets. We also include documentation
- above on how to set up SCI sockets using ordinary TCP/IP for
- MySQL Cluster.
+ so far only with SCI sockets. See <xref linkend="sci-sockets"/>
+ for information on how to set up SCI sockets using ordinary
+ TCP/IP for MySQL Cluster.
</para>
</section>
@@ -9967,13 +9971,15 @@
<listitem>
<para>
- <emphasis>What storage engines does Cluster
- support?</emphasis>
+ <emphasis>What storage engines are supported by MySQL Cluster?</emphasis>
</para>
<para>
- <literal>NDB</literal> is the only MySQL storage engine that
- supports clustering.
+ Clustering in MySQL is supported only by the
+ <literal>NDB</literal> storage engine. That is, in order for a
+ table to be shared between nodes in a cluster, it must be
+ created using <literal>ENGINE=NDB</literal> (or
+ <literal>ENGINE=NDBCLUSTER</literal>, which is equivalent).
</para>
<para>
@@ -10338,10 +10344,11 @@
¤t-series;, Cluster tables (that is, tables created with
<literal>ENGINE=NDBCLUSTER</literal>) have only fixed-width
rows. This means that (for example) each record containing a
- <literal>VARCHAR(255)</literal> column will require 256 bytes
- of storage for that column, regardless of the size of the data
- stored therein. This issue is expected to be fixed in a future
- MySQL release series.
+ <literal>VARCHAR(255)</literal> column will require space for
+ 255 characters (as required for the character set and
+ collation being used for the table), regardless of the actual
+ number of characters stored therein. This issue is expected to
+ be fixed in a future MySQL release series.
</para>
<para>
@@ -10463,9 +10470,8 @@
Yes, so long as all machines and operating systems have the
same endianness (all big-endian or all little-endian). It is
also possible to use different MySQL Cluster releases on
- different nodes (for example, 4.1.8 on some nodes and 4.1.9 on
- others). However, we recommend this be done only as part of a
- rolling upgrade procedure.
+ different nodes. However, we recommend this be done only as
+ part of a rolling upgrade procedure.
</para>
</listitem>
@@ -10987,12 +10993,12 @@
<para>
As is usual in the context of a relational database, the term
- <quote>table</quote> denotes an ordered set of identically
- structured records. In MySQL Cluster, a database table is
- stored in a data node as a set of fragments, each of which is
- replicated on additional data nodes. The set of data nodes
- replicating the same fragment or set of fragments is referred
- to as a <emphasis>node group</emphasis>.
+ <quote>table</quote> denotes a set of identically structured
+ records. In MySQL Cluster, a database table is stored in a
+ data node as a set of fragments, each of which is replicated
+ on additional data nodes. The set of data nodes replicating
+ the same fragment or set of fragments is referred to as a
+ <emphasis>node group</emphasis>.
</para>
</listitem>
Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml 2006-02-01 02:02:30 UTC (rev 1161)
+++ trunk/refman-5.0/ndbcluster.xml 2006-02-01 03:26:29 UTC (rev 1162)
@@ -547,10 +547,12 @@
<para>
This section is a <quote>How-To</quote> that describes the basics
for how to plan, install, configure, and run a MySQL Cluster.
- Unlike the example in
- <xref linkend="mysql-cluster-configuration"/>, the result of
- following the guidelines and procedures outlined here should be a
- usable MySQL Cluster which meets minimum requirements for
+ Whereas the examples in
+ <xref linkend="mysql-cluster-configuration"/> provide more
+ in-depth information on a variety of clustering options and
+ configuration, the result of following the guidelines and
+ procedures outlined here should be a usable MySQL Cluster which
+ meets the <emphasis>minimum</emphasis> requirements for
availability and safeguarding of data.
</para>
@@ -638,11 +640,11 @@
Each host in our scenario is an Intel-based desktop PC running
a common, generic Linux distribution installed to disk in a
standard configuration, and running no unnecessary services.
- The core OS with a standard TCP/IP networking client should be
- sufficient. Also for the sake of simplicity, we also assume
- that the filesystems on all hosts are set up identically. In
- the event that they are not, you will need to adapt these
- instructions accordingly.
+ The core OS with standard TCP/IP networking capabilities
+ should be sufficient. Also for the sake of simplicity, we also
+ assume that the filesystems on all hosts are set up
+ identically. In the event that they are not, you will need to
+ adapt these instructions accordingly.
</para>
</listitem>
@@ -7089,11 +7091,12 @@
</informaltable>
<para>
- Event severity levels can be turned on or off. If a severity
- level is turned on, all events with a priority less than or
- equal to the category thresholds are logged. If the severity
- level is turned off then no events belonging to that severity
- level are logged.
+ Event severity levels can be turned on or off (using
+ <literal>CLUSTERLOG FILTER</literal> — see above). If a
+ severity level is turned on, then all events with a priority
+ less than or equal to the category thresholds are logged. If
+ the severity level is turned off then no events belonging to
+ that severity level are logged.
</para>
<remark role="todo">
@@ -8984,9 +8987,9 @@
There are several other optimized socket implementations for
computer clusters, including Myrinet, Gigabit Ethernet,
Infiniband and the VIA interface. We have tested MySQL Cluster
- so far only with SCI sockets. We also include documentation
- above on how to set up SCI sockets using ordinary TCP/IP for
- MySQL Cluster.
+ so far only with SCI sockets. See <xref linkend="sci-sockets"/>
+ for information on how to set up SCI sockets using ordinary
+ TCP/IP for MySQL Cluster.
</para>
</section>
@@ -9717,8 +9720,8 @@
MySQL replication</emphasis>: This will make it possible to
update from any MySQL Server in the cluster and still have
the MySQL Replication handled by one of the MySQL Servers in
- the cluster and the installation on the slave side
- consistent.
+ the cluster, with the state of the slave side remaining
+ consistent with the cluster acting as the master.
</para>
</listitem>
@@ -9747,15 +9750,16 @@
<listitem>
<para>
<emphasis role="bold">User-defined partitioning</emphasis>:
- Users will be able to define partitions based on the fields
- part of the primary key. The MySQL Server will be able to
- discover whether it is possible to prune away some of the
- partitions from the <literal>WHERE</literal> clause.
+ Users will be able to define partitions based on columns
+ that are part of the primary key. The MySQL Server will be
+ able to discover whether it is possible to prune away some
+ of the partitions from the <literal>WHERE</literal> clause.
Partitioning based on <literal>KEY</literal>,
<literal>HASH</literal>, <literal>RANGE</literal>, and
<literal>LIST</literal> handlers will be possible, as well
as subpartitioning. This feature should also be available
- for many other handlers.
+ for many other handlers, and not only <literal>NDB
+ Cluster</literal>.
</para>
</listitem>
@@ -10247,13 +10251,15 @@
<listitem>
<para>
- <emphasis>What storage engines does Cluster
- support?</emphasis>
+ <emphasis>What storage engines are supported by MySQL Cluster?</emphasis>
</para>
<para>
- <literal>NDB</literal> is the only MySQL storage engine that
- supports clustering.
+ Clustering in MySQL is supported only by the
+ <literal>NDB</literal> storage engine. That is, in order for a
+ table to be shared between nodes in a cluster, it must be
+ created using <literal>ENGINE=NDB</literal> (or
+ <literal>ENGINE=NDBCLUSTER</literal>, which is equivalent).
</para>
<para>
@@ -10626,10 +10632,11 @@
(that is, tables created with
<literal>ENGINE=NDBCLUSTER</literal>) have only fixed-width
rows. This means that (for example) each record containing a
- <literal>VARCHAR(255)</literal> column will require 256 bytes
- of storage for that column, regardless of the size of the data
- stored therein. This issue is expected to be fixed in a future
- MySQL release series.
+ <literal>VARCHAR(255)</literal> column will require space for
+ 255 characters (as required for the character set and
+ collation being used for the table), regardless of the actual
+ number of characters stored therein. This issue is expected to
+ be fixed in a future MySQL release series.
</para>
<para>
@@ -11274,12 +11281,12 @@
<para>
As is usual in the context of a relational database, the term
- <quote>table</quote> denotes an ordered set of identically
- structured records. In MySQL Cluster, a database table is
- stored in a data node as a set of fragments, each of which is
- replicated on additional data nodes. The set of data nodes
- replicating the same fragment or set of fragments is referred
- to as a <emphasis>node group</emphasis>.
+ <quote>table</quote> denotes a set of identically structured
+ records. In MySQL Cluster, a database table is stored in a
+ data node as a set of fragments, each of which is replicated
+ on additional data nodes. The set of data nodes replicating
+ the same fragment or set of fragments is referred to as a
+ <emphasis>node group</emphasis>.
</para>
</listitem>
Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml 2006-02-01 02:02:30 UTC (rev 1161)
+++ trunk/refman-5.1/ndbcluster.xml 2006-02-01 03:26:29 UTC (rev 1162)
@@ -547,10 +547,12 @@
<para>
This section is a <quote>How-To</quote> that describes the basics
for how to plan, install, configure, and run a MySQL Cluster.
- Unlike the example in
- <xref linkend="mysql-cluster-configuration"/>, the result of
- following the guidelines and procedures outlined here should be a
- usable MySQL Cluster which meets minimum requirements for
+ Whereas the examples in
+ <xref linkend="mysql-cluster-configuration"/> provide more
+ in-depth information on a variety of clustering options and
+ configuration, the result of following the guidelines and
+ procedures outlined here should be a usable MySQL Cluster which
+ meets the <emphasis>minimum</emphasis> requirements for
availability and safeguarding of data.
</para>
@@ -638,11 +640,11 @@
Each host in our scenario is an Intel-based desktop PC running
a common, generic Linux distribution installed to disk in a
standard configuration, and running no unnecessary services.
- The core OS with a standard TCP/IP networking client should be
- sufficient. Also for the sake of simplicity, we also assume
- that the filesystems on all hosts are set up identically. In
- the event that they are not, you will need to adapt these
- instructions accordingly.
+ The core OS with standard TCP/IP networking capabilities
+ should be sufficient. Also for the sake of simplicity, we also
+ assume that the filesystems on all hosts are set up
+ identically. In the event that they are not, you will need to
+ adapt these instructions accordingly.
</para>
</listitem>
@@ -7087,11 +7089,12 @@
</informaltable>
<para>
- Event severity levels can be turned on or off. If a severity
- level is turned on, all events with a priority less than or
- equal to the category thresholds are logged. If the severity
- level is turned off then no events belonging to that severity
- level are logged.
+ Event severity levels can be turned on or off (using
+ <literal>CLUSTERLOG FILTER</literal> — see above). If a
+ severity level is turned on, then all events with a priority
+ less than or equal to the category thresholds are logged. If
+ the severity level is turned off then no events belonging to
+ that severity level are logged.
</para>
<remark role="todo">
@@ -10638,9 +10641,9 @@
There are several other optimized socket implementations for
computer clusters, including Myrinet, Gigabit Ethernet,
Infiniband and the VIA interface. We have tested MySQL Cluster
- so far only with SCI sockets. We also include documentation
- above on how to set up SCI sockets using ordinary TCP/IP for
- MySQL Cluster.
+ so far only with SCI sockets. See <xref linkend="sci-sockets"/>
+ for information on how to set up SCI sockets using ordinary
+ TCP/IP for MySQL Cluster.
</para>
</section>
@@ -10683,16 +10686,15 @@
</para>
<remark role="todo">
- [pd] I see no such list. Should we comment out the following
- paragraph?
+ [js] Commented out the following paragraph until the 5.1 list is ready.
</remark>
-
+<!--
<para>
(<emphasis role="bold">Note</emphasis>: See the end of this
section for a list of issues in MySQL &previous-series; Cluster
that have been resolved in the current version.)
</para>
-
+-->
<itemizedlist>
<listitem>
@@ -11244,8 +11246,8 @@
<title>&title-mysql-5-0-cluster-changes;</title>
<para>
- MySQL 5.0.3-beta and later releases contain a number of new
- features that are likely to be of interest:
+ MySQL Cluster in versions 5.0.3-beta and later contains a number
+ of new features that are likely to be of interest:
</para>
<itemizedlist>
@@ -11375,8 +11377,8 @@
MySQL replication</emphasis>: This will make it possible to
update from any MySQL Server in the cluster and still have
the MySQL Replication handled by one of the MySQL Servers in
- the cluster and the installation on the slave side
- consistent.
+ the cluster, with the state of the slave side remaining
+ consistent with the cluster acting as the master.
</para>
</listitem>
@@ -11405,15 +11407,16 @@
<listitem>
<para>
<emphasis role="bold">User-defined partitioning</emphasis>:
- Users will be able to define partitions based on the fields
- part of the primary key. The MySQL Server will be able to
- discover whether it is possible to prune away some of the
- partitions from the <literal>WHERE</literal> clause.
+ Users will be able to define partitions based on columns
+ that are part of the primary key. The MySQL Server will be
+ able to discover whether it is possible to prune away some
+ of the partitions from the <literal>WHERE</literal> clause.
Partitioning based on <literal>KEY</literal>,
<literal>HASH</literal>, <literal>RANGE</literal>, and
<literal>LIST</literal> handlers will be possible, as well
as subpartitioning. This feature should also be available
- for many other handlers.
+ for many other handlers, and not only <literal>NDB
+ Cluster</literal>.
</para>
</listitem>
@@ -11905,13 +11908,15 @@
<listitem>
<para>
- <emphasis>What storage engines does Cluster
- support?</emphasis>
+ <emphasis>What storage engines are supported by MySQL Cluster?</emphasis>
</para>
<para>
- <literal>NDB</literal> is the only MySQL storage engine that
- supports clustering.
+ Clustering in MySQL is supported only by the
+ <literal>NDB</literal> storage engine. That is, in order for a
+ table to be shared between nodes in a cluster, it must be
+ created using <literal>ENGINE=NDB</literal> (or
+ <literal>ENGINE=NDBCLUSTER</literal>, which is equivalent).
</para>
<para>
@@ -12284,10 +12289,11 @@
(that is, tables created with
<literal>ENGINE=NDBCLUSTER</literal>) have only fixed-width
rows. This means that (for example) each record containing a
- <literal>VARCHAR(255)</literal> column will require 256 bytes
- of storage for that column, regardless of the size of the data
- stored therein. This issue is expected to be fixed in a future
- MySQL release series.
+ <literal>VARCHAR(255)</literal> column will require space for
+ 255 characters (as required for the character set and
+ collation being used for the table), regardless of the actual
+ number of characters stored therein. This issue is expected to
+ be fixed in a future MySQL release series.
</para>
<para>
@@ -12932,12 +12938,12 @@
<para>
As is usual in the context of a relational database, the term
- <quote>table</quote> denotes an ordered set of identically
- structured records. In MySQL Cluster, a database table is
- stored in a data node as a set of fragments, each of which is
- replicated on additional data nodes. The set of data nodes
- replicating the same fragment or set of fragments is referred
- to as a <emphasis>node group</emphasis>.
+ <quote>table</quote> denotes a set of identically structured
+ records. In MySQL Cluster, a database table is stored in a
+ data node as a set of fragments, each of which is replicated
+ on additional data nodes. The set of data nodes replicating
+ the same fragment or set of fragments is referred to as a
+ <emphasis>node group</emphasis>.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1162 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 1 Feb |
