Author: jstephens
Date: 2007-05-18 10:54:38 +0200 (Fri, 18 May 2007)
New Revision: 6519
Log:
Some more little fixups...
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 08:03:02 UTC (rev 6518)
+++ trunk/refman-5.1/mysql-cluster-limitations-working.xml 2007-05-18 08:54:38 UTC (rev 6519)
Changed blocks: 8, Lines Added: 36, Lines Deleted: 24; 4655 bytes
@@ -1225,9 +1225,9 @@
</formalpara>
- <itemizedlist>
+
- <listitem>
+
<formalpara>
<title>Multiple network addresses</title>
@@ -1239,23 +1239,27 @@
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>
</para>
</formalpara>
- <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>
- </listitem>
+
- </itemizedlist>
+
</section>
@@ -1276,11 +1280,14 @@
<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>
Previously, for example, any Cluster table having one or
more <literal>VARCHAR</literal> fields which contained only
@@ -1313,18 +1320,21 @@
<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>Circular Replication</title>
<para>
- However, circular replication is <emphasis>not</emphasis>
- currently supported for MySQL Cluster. See
+ Circular replication is supported for MySQL Cluster
+ beginning with MySQL 5.1.18. See
<xref linkend="mysql-cluster-replication-issues"/>.
- </para>
+ </para></formalpara>
</listitem>
<listitem>
@@ -1332,7 +1342,8 @@
<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
@@ -1340,7 +1351,7 @@
and is connected to the cluster at the time that the
database is created on a different
<command>mysqld</command>.
- </para>
+ </para></formalpara>
<para>
What this means is that if a <command>mysqld</command>
@@ -1364,7 +1375,8 @@
</para>
</listitem>
- <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.
@@ -1372,7 +1384,7 @@
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>
+ </para></formalpara>
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6519 - trunk/refman-5.1 | jon | 18 May |
