Author: jstephens
Date: 2007-05-18 11:53:10 +0200 (Fri, 18 May 2007)
New Revision: 6522
Log:
More misc. fixups + reformat.
Modified:
trunk/refman-5.1/mysql-cluster-limitations-working.xml
Modified: trunk/refman-5.1/mysql-cluster-limitations-working.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-limitations-working.xml 2007-05-18 09:33:19 UTC (rev 6521)
+++ trunk/refman-5.1/mysql-cluster-limitations-working.xml 2007-05-18 09:53:10 UTC (rev 6522)
Changed blocks: 8, Lines Added: 120, Lines Deleted: 98; 10652 bytes
@@ -1070,7 +1070,7 @@
<section id="mysql-cluster-limitations-disk-data">
- <title>Limitation Relating to Disk Data Storage</title>
+ <title>Limitations Relating to Disk Data Storage</title>
<indexterm>
<primary>MySQL Cluster limitations</primary>
@@ -1140,26 +1140,35 @@
<itemizedlist>
- <listitem><formalpara>
- <title><literal>ALTER TABLE</literal> operations</title>
- <para>
- <literal>ALTER TABLE</literal> is not fully locking when
- running multiple MySQL servers (no distributed table
- lock).
- </para></formalpara>
+ <listitem>
+ <formalpara>
+
+ <title><literal>ALTER TABLE</literal> operations</title>
+
+ <para>
+ <literal>ALTER TABLE</literal> is not fully locking when
+ running multiple MySQL servers (no distributed table
+ lock).
+ </para>
+
+ </formalpara>
</listitem>
<listitem>
<formalpara>
+
<title>DDL operations</title>
- <para>
- DDL operations (such as <literal>CREATE TABLE</literal> or
- <literal>ALTER TABLE</literal>) are not safe from data
- node failures. If a data node fails while trying to peform
- one of these, the data dictionary is locked and no further
- DDL statements can be executed without restarting the
- cluster.
- </para></formalpara>
+
+ <para>
+ DDL operations (such as <literal>CREATE TABLE</literal>
+ or <literal>ALTER TABLE</literal>) are not safe from
+ data node failures. If a data node fails while trying to
+ peform one of these, the data dictionary is locked and
+ no further DDL statements can be executed without
+ restarting the cluster.
+ </para>
+
+ </formalpara>
</listitem>
</itemizedlist>
@@ -1202,23 +1211,21 @@
</formalpara>
+ <formalpara>
- <formalpara>
-
<title>Multiple data node processes</title>
-
+
<para>
While it is possible to run multiple cluster processes
- concurrently on a single host, it is not always advisable
- to do so for reasons of performance and high availability,
- as well as other considerations. In particular, in MySQL
- ¤t-series; or &mccge-series;, we do not support for
- production use any MySQL Cluster deployment in which more
- than one <command>ndbd</command> process is run on a
- single physical machine.
+ concurrently on a single host, it is not always advisable to do
+ so for reasons of performance and high availability, as well as
+ other considerations. In particular, in MySQL ¤t-series;
+ or &mccge-series;, we do not support for production use any
+ MySQL Cluster deployment in which more than one
+ <command>ndbd</command> process is run on a single physical
+ machine.
+
<note>
-
-
<para>
We may support multiple data nodes per host in a future
MySQL release, following additional testing. However, in
@@ -1227,45 +1234,37 @@
</para>
</note>
</para>
-
-
-
+
</formalpara>
-
- <formalpara>
+ <formalpara>
- <title>Multiple network addresses</title>
+ <title>Multiple network addresses</title>
+ <para>
+ Multiple network addresses per data node are not supported. Use
+ of these is liable to cause problems: In the event of a data
+ node failure, an SQL node waits for confirmation that the data
+ node went down but never receives it because another route to
+ that data node remains open. This can effectively make the
+ cluster inoperable.
+
+ <note>
<para>
- Multiple network addresses per data node are not supported.
- Use of these is liable to cause problems: In the event of a
- data node failure, an SQL node waits for confirmation that
- the data node went down but never receives it because
- another route to that data node remains open. This can
- effectively make the cluster inoperable.
-
- <note>
-
- <para>
- It is possible to use multiple network hardware
- <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 the
- <literal>config.ini</literal> file. See
- <xref linkend="mysql-cluster-tcp-definition"/>, for more
- information.
- </para>
- </note>
+ It is possible to use multiple network hardware
+ <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
+ the <literal>config.ini</literal> file. See
+ <xref linkend="mysql-cluster-tcp-definition"/>, for more
+ information.
</para>
+ </note>
+ </para>
- </formalpara>
+ </formalpara>
-
-
-
-
</section>
<section id="mysql-cluster-limitations-resolved">
@@ -1285,15 +1284,19 @@
<itemizedlist>
<listitem>
-
<formalpara>
+
<title>Variable-length column support</title>
+
+ <para>
+ The <literal>NDB Cluster</literal> storage engine now
+ supports variable-length column types for in-memory
+ tables.
+ </para>
+
+ </formalpara>
+
<para>
- The <literal>NDB Cluster</literal> storage engine now
- supports variable-length column types for in-memory tables.
- </para>
-</formalpara>
- <para>
Previously, for example, any Cluster table having one or
more <literal>VARCHAR</literal> fields which contained only
relatively small values, much more memory and disk space
@@ -1325,21 +1328,30 @@
<primary>MySQL Cluster limitations</primary>
<secondary>replication</secondary>
</indexterm>
-<formalpara>
- <title>Replication with MySQL Cluster</title>
- <para>
- It is now possible to use MySQL replication with Cluster
- databases. For details, see
- <xref linkend="mysql-cluster-replication"/>.
- </para>
-</formalpara>
+
<formalpara>
+
+ <title>Replication with MySQL Cluster</title>
+
+ <para>
+ It is now possible to use MySQL replication with Cluster
+ databases. For details, see
+ <xref linkend="mysql-cluster-replication"/>.
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
<title>Circular Replication</title>
- <para>
- Circular replication is supported for MySQL Cluster
- beginning with MySQL 5.1.18. See
- <xref linkend="mysql-cluster-replication-issues"/>.
- </para></formalpara>
+
+ <para>
+ Circular replication is supported for MySQL Cluster
+ beginning with MySQL 5.1.18. See
+ <xref linkend="mysql-cluster-replication-issues"/>.
+ </para>
+
+ </formalpara>
</listitem>
<listitem>
@@ -1347,17 +1359,22 @@
<primary>MySQL Cluster limitations</primary>
<secondary>autodiscovery</secondary>
</indexterm>
-<formalpara>
- <title>Database autodiscovery and online schema changes</title>
- <para>
- Autodiscovery of databases is now supported for multiple
- MySQL servers accessing the same MySQL Cluster, provided
- that a given <command>mysqld</command> is already running
- and is connected to the cluster at the time that the
- database is created on a different
- <command>mysqld</command>.
- </para></formalpara>
+ <formalpara>
+
+ <title>Database autodiscovery and online schema changes</title>
+
+ <para>
+ Autodiscovery of databases is now supported for multiple
+ MySQL servers accessing the same MySQL Cluster, provided
+ that a given <command>mysqld</command> is already running
+ and is connected to the cluster at the time that the
+ database is created on a different
+ <command>mysqld</command>.
+ </para>
+
+ </formalpara>
+
<para>
What this means is that if a <command>mysqld</command>
process first connects to the cluster after a database named
@@ -1380,16 +1397,21 @@
</para>
</listitem>
- <listitem><formalpara>
- <title>Backup and restore between architectures</title>
- <para>
- Beginning with MySQL 5.1.10, it is possible to perform a
- Cluster backup and restore between different architectures.
- Previously — for example — you could not back up
- a cluster running on a big-endian platform and then restore
- from that backup to a cluster running on a little-endian
- system. (Bug #19255)
- </para></formalpara>
+ <listitem>
+ <formalpara>
+
+ <title>Backup and restore between architectures</title>
+
+ <para>
+ Beginning with MySQL 5.1.10, it is possible to perform a
+ Cluster backup and restore between different
+ architectures. Previously — for example — you
+ could not back up a cluster running on a big-endian
+ platform and then restore from that backup to a cluster
+ running on a little-endian system. (Bug #19255)
+ </para>
+
+ </formalpara>
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6522 - trunk/refman-5.1 | jon | 18 May |
