Author: jstephens
Date: 2006-03-14 12:23:47 +0100 (Tue, 14 Mar 2006)
New Revision: 1571
Log:
Documenting Cluster bugfixes:
Bug #14028, Bug #16386, Bug #16657/Bug #17890, Bug #16913, Bug #17536,
Bug #17838, Bug #17854, Bug #18026, Bug #18039, Bug #18040, Bug #18067,
Bug # 18075
Max # logfile groups is 1 beginning in 5.1.8.
Modified:
trunk/refman-5.1/ndbcluster.xml
trunk/refman-5.1/sql-syntax.xml
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml 2006-03-14 03:23:53 UTC (rev 1570)
+++ trunk/refman-5.1/ndbcluster.xml 2006-03-14 11:23:47 UTC (rev 1571)
@@ -10084,6 +10084,11 @@
the permitted values for this clause are
<literal>NDB</literal> and <literal>NDBCLUSTER</literal>.
</para>
+
+ <para>
+ <emphasis role="bold">Important</emphasis>: In MySQL 5.1.8 and
+ later, there can exist only one logfile group at any given time.
+ </para>
</listitem>
<listitem>
@@ -10094,6 +10099,13 @@
cluster.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <literal>UNDO_BUFFER_SIZE</literal> is limited by the amount of
+ system memory available.
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2006-03-14 03:23:53 UTC (rev 1570)
+++ trunk/refman-5.1/sql-syntax.xml 2006-03-14 11:23:47 UTC (rev 1571)
@@ -3589,20 +3589,27 @@
LOGFILE GROUP</literal> statement has one and only one
<literal>ADD UNDOFILE</literal> clause.
</para>
+
+ <para>
+ Beginning with MySQL 5.1.8, you can have only one logfile group per
+ Cluster at any given time. (See Bug #16386)
+ </para>
<para>
The <literal>INITIAL_SIZE</literal> parameter sets the
<literal>UNDO</literal> file's initial size. The optional
<literal>UNDO_BUFFFER_SIZE</literal> parameter sets the size
used by the <literal>UNDO</literal> buffer for the logfile
- group; the default is <literal>8M</literal> (eight megabytes).
- Both <replaceable>initial_size</replaceable> and
- <replaceable>undo_buffer_size_size</replaceable> are specified
- in bytes. You may optionally follow either or both of these with
- a one-letter abbreviation for an order of magnitude, similar to
- those used in <filename>my.cnf</filename>. Generally, this is
- one of the letters <literal>M</literal> (for megabytes) or
- <literal>G</literal> (for gigabytes).
+ group; The default value for <literal>UNDO_BUFFER_SIZE</literal> is
+ <literal>8M</literal> (eight megabytes); this value cannot exceeed the
+ amount of system memory avilable. Both
+ <replaceable>initial_size</replaceable> and
+ <replaceable>undo_buffer_size_size</replaceable> are specified in bytes.
+ You may optionally follow either or both of these with a one-letter
+ abbreviation for an order of magnitude, similar to those used in
+ <filename>my.cnf</filename>. Generally, this is one of the letters
+ <literal>M</literal> (for megabytes) or <literal>G</literal> (for
+ gigabytes).
</para>
<para>
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-03-14 03:23:53 UTC (rev 1570)
+++ trunk/refman-common/news-4.1.xml 2006-03-14 11:23:47 UTC (rev 1571)
@@ -190,6 +190,14 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Inserting and deleting
+ <literal>BLOB</literal> column values while a backup was in process
+ could cause the loss of an <command>ndbd</command> node. (Bug #14028)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-03-14 03:23:53 UTC (rev 1570)
+++ trunk/refman-common/news-5.0.xml 2006-03-14 11:23:47 UTC (rev 1571)
@@ -208,6 +208,14 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Inserting and deleting
+ <literal>BLOB</literal> column values while a backup was in process
+ could cause the loss of an <command>ndbd</command> node. (Bug #14028)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-03-14 03:23:53 UTC (rev 1570)
+++ trunk/refman-common/news-5.1.xml 2006-03-14 11:23:47 UTC (rev 1571)
@@ -192,6 +192,14 @@
linkend="partitioning-handling-nulls"/>. (Bug #15447)
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): You can now have only one
+ logfile group at any one time. See
+ <xref linkend="create-logfile-group"/>. (Bug #16386)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -376,14 +384,101 @@
<listitem>
<para>
- Using ALTER TABLE ... REBUILD PARTITION without specifying the name of
- the partition caused the server to crash, rather than reporting a
- syntax error. (Bug #17947)
+ <literal>NDB Cluster</literal>: Variable-length columns used as
+ primary keys were not handled correctly. (Bug #18075)
</para>
</listitem>
<listitem>
<para>
+ <literal>NDB Cluster</literal>: Row-based replication could fail with
+ tables using <literal>VARCHAR</literal> columns for primary keys and
+ having <literal>BLOB</literal> columns. (Bug #18067)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: <literal>CREATE UNIQUE INDEX</literal>
+ on a column containing non-unique data could cause one or more
+ <command>ndbd</command> nodes to hang or crash. (Bug #18040)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): <literal>CREATE UNIQUE
+ INDEX</literal> failed with <errortext>Error 4243: Index not
+ found</errortext>. (Bug #18039)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Node recovery of tables with
+ <literal>VARCHAR</literal> columns using character sets was
+ inconsistent, which could cause a number of issues, including the
+ data nodes failing to restart and <literal>ALTER TABLE</literal>
+ statements to hang. (Bug #18026)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: In some cases, a single
+ <command>ndbd</command> node would fail following a system restart.
+ (Bug #17854)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Replication): The binary log on the
+ secondary master was not being set up correctly following a table
+ rename. (Bug #17838)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: With a single replica, transactions
+ waiting in the log synchronisation queue were not being restarted,
+ causing them to be aborted. (Bug #17536)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): It was not possible to
+ create more than 9 tablespaces. (Bug #16913)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Inserting and deleting
+ <literal>BLOB</literal> column values while a backup was in process
+ could cause the loss of an <command>ndbd</command> node. (Bug #14028)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: <literal>UNDO_BUFFER_SIZE</literal>
+ was limited to 17 MB. (Bug #16657, Bug #17890)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>ALTER TABLE ... REBUILD PARTITION</literal> without
+ specifying the name of the partition caused the server to crash,
+ rather than reporting a syntax error. (Bug #17947)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
When attempting to insert a <literal>0</literal> into a
<literal>LIST</literal>-partitioned table that had no value-list
containing <literal>0</literal>, no error was reported. (Bug #15253)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1571 - in trunk: refman-5.1 refman-common | jon | 14 Mar |
