List:Commits« Previous MessageNext Message »
From:jon.stephens Date:November 5 2010 10:33pm
Subject:svn commit - mysqldoc@docsrva: r23591 - trunk/dynamic-docs/changelog
View as plain text  
Author: jstephens
Date: 2010-11-05 23:33:29 +0100 (Fri, 05 Nov 2010)
New Revision: 23591

Log:

Added changelog entries for Cluster bugfixes:

  BUG#57848, BUG#57896, BUG#57897, BUG#57946, BUG#57949



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


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2010-11-05 21:08:15 UTC (rev 23590)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2010-11-05 22:33:29 UTC (rev 23591)
Changed blocks: 1, Lines Added: 162, Lines Deleted: 0; 4276 bytes

@@ -10,7 +10,169 @@
 
     <tags>
       <highlight type="cluster"/>
+      <manual type="Windows"/>
+      <manual type="angel process"/>
+      <manual type="space character"/>
+      <manual type="argv"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="57949"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.51-ndb-7.0.20"/>
+      <version ver="5.1.51-ndb-7.1.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        On Windows, the angel process which monitors and (when
+        necessary) restarts the data node process failed to spawn a new
+        worker in some circumstances where the arguments vector
+        contained extra items placed at its beginning. This could occur
+        when the path to <command>ndbd.exe</command> or
+        <command>ndbmtd.exe</command> contained one or more spaces.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="heartbeat"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="57946"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.51-ndb-7.0.20"/>
+      <version ver="5.1.51-ndb-7.1.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The disconnection of an API or management node due to missed
+        heartbeats led to a race condition which could cause data nodes
+        to crash.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="table schemas"/>
+      <manual type="P0.SchemaLog"/>
+      <manual type="schema transactions"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="57897"/>
+      <seealsobug bugid="57896"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.51-ndb-7.0.20"/>
+      <version ver="5.1.51-ndb-7.1.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The method for calculating table schema versions used by schema
+        transactions did not follow the established rules for recording
+        schemas used in the <filename>P0.SchemaLog</filename> file.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="LQHKEYREQ"/>
+      <manual type="table schemas"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="57896"/>
+      <seealsobug bugid="57897"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.51-ndb-6.3.39"/>
+      <version ver="5.1.51-ndb-7.0.20"/>
+      <version ver="5.1.51-ndb-7.1.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The <literal>LQHKEYREQ</literal> request message used by the
+        local query handler when checking the major schema version of a
+        table, being only 16 bits wide, could cause this check to fail
+        with an <errortext>Invalid schema version</errortext> error
+        (<literal role="se">NDB</literal> error code 1227). This issue
+        occurred after creating and dropping (and re-creating) the same
+        table 65537 times, then trying to insert rows into the table.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="diskdata"/>
+      <manual type="online operations"/>
+      <manual type="DBACC"/>
+      <manual type="DBTUP"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="57848"/>
+      <seealsobug bugid="57827"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.51-ndb-7.0.20"/>
+      <version ver="5.1.51-ndb-7.1.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When performing online DDL on Disk Data tables, scans and moving
+        of the relevant tuples were done in more or less random order.
+        This fix causes these scans to be done in the order of the
+        tuples, which should improve performance of such operations due
+        to the more sequential ordering of the scans.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="diskdata"/>
       <manual type="unique indexes"/>
+      <manual type="ndb_restore"/>
     </tags>
 
     <bugs>


Thread
svn commit - mysqldoc@docsrva: r23591 - trunk/dynamic-docs/changelogjon.stephens5 Nov