svn commit - mysqldoc@docsrva: r20850 - trunk/dynamic-docs/changelog

[jon.stephens]

Author: jstephens
Date: 2010-05-25 14:52:38 +0200 (Tue, 25 May 2010)
New Revision: 20850

Log:

Documented Cluster bugfixes:

	BUG#53935, BUG#53944



Modified:
   trunk/dynamic-docs/changelog/mysqld-2.xml


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2010-05-25 12:13:57 UTC (rev 20849)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2010-05-25 12:52:38 UTC (rev 20850)
Changed blocks: 1, Lines Added: 73, Lines Deleted: 0; 2406 bytes

@@ -10,6 +10,79 @@
 
     <tags>
       <highlight type="cluster"/>
+      <manual type="MaxNoOfAttributes"/>
+      <manual type="CREATE TABLE"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="53944"/>
+      <regressionof bugid="44294"/>
+      <seealsobug bugid="52055"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.44-ndb-7.0.15"/>
+      <version ver="5.1.44-ndb-7.1.4"/>
+    </versions>
+
+    <message>
+
+      <para>
+        After creating <literal role="se">NDB</literal> tables until
+        creation of a table failed due to
+        <literal role="se">NDB</literal> error 905 <errortext>Out of
+        attribute records (increase MaxNoOfAttributes)</errortext>, then
+        increasing <literal>MaxNoOfAttributes</literal> and restarting
+        all management node and data node processes, attempting to drop
+        and re-create one of the tables failed with the error
+        <errortext>Out of table records...</errortext>, even when
+        sufficient table records were available.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="Disk Data"/>
+      <manual type="DBTUP"/>
+      <manual type="restarts"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="53935"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.44-ndb-6.2.19"/>
+      <version ver="5.1.44-ndb-6.3.34"/>
+      <version ver="5.1.44-ndb-7.0.15"/>
+      <version ver="5.1.44-ndb-7.1.4"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Creating a Disk Data table, dropping it, then creating an
+        in-memory table and performing a restart, could cause data node
+        processes to fail with errors in the <literal>DBTUP</literal>
+        kernel block if the new table&apos;s internal ID was the same as
+        that of the old Disk Data table. This could occur because undo
+        log handling during the restart did not check that the table
+        having this ID was now in-memory only.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
       <manual type="MTOIB"/>
     </tags>