MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon.stephens Date:March 5 2010 1:58pm
Subject:svn commit - mysqldoc@docsrva: r19424 - trunk/dynamic-docs/changelog
View as plain text  
Author: jstephens
Date: 2010-03-05 14:58:10 +0100 (Fri, 05 Mar 2010)
New Revision: 19424

Log:

Documented Cluster bugfixes:

	BUG#46114, BUG#50196, BUG#51111, 
	BUG#51644, BUG#51645, BUG#51723



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


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2010-03-05 13:56:16 UTC (rev 19423)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2010-03-05 13:58:10 UTC (rev 19424)
Changed blocks: 2, Lines Added: 134, Lines Deleted: 0; 3989 bytes

@@ -8,7 +8,139 @@
 
   <logentry entrytype="bug">
 
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="redo log"/>
+    </tags>
+
     <bugs>
+      <fixes bugid="51723"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.41-ndb-6.3.33"/>
+      <version ver="5.1.41-ndb-7.0.14"/>
+      <version ver="5.1.41-ndb-7.1.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The redo log protects itself from being filled up by
+        periodically checking how much space remains free. If
+        insufficient redo log space is available, it sets the state
+        <literal>TAIL_PROBLEM</literal> which results in transactions
+        being aborted with error code 410 (<errortext>out of redo
+        log</errortext>). However, this state was not set following a
+        node restart, which meant that if a data node had insufficient
+        redo log space following a node restart, it could crash a short
+        time later with <errortext>Fatal error due to end of REDO
+        log</errortext>. Now, this space is checked during node
+        restarts.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="ndbmtd"/>
+      <manual type="system restarts"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="51645"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.41-ndb-7.0.13"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When performing a system restart of a MySQL Cluster where
+        multi-threaded data nodes were in use, there was a slight risk
+        that the restart would hang due to incorrect serialization of
+        signals passed between LQH instances and proxies; some signals
+        were sent using a proxy, and others directly, which meant that
+        the order in which they were sent and received could not be
+        guaranteed. If signals arrived in the wrong order, this could
+        cause one or more data nodes to hang. Now all signals that need
+        to be sent and received in the same order are sent using the
+        same path.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="local checkpoints"/>
+      <manual type="system restarts"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="51644"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.41-ndb-6.3.32"/>
+      <version ver="5.1.41-ndb-7.0.13"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When one or more data nodes read their LCPs and applied undo
+        logs significantly faster than others, this could lead to a race
+        condition causing system restarts of data nodes to hang. This
+        could most often occur when using both <command>ndbd</command>
+        and <command>ndbmtd</command> processes for the data nodes.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="ndb_mgm"/>
+      <manual type="HELP"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="46114"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.41-ndb-7.0.14"/>
+      <version ver="5.1.41-ndb-7.1.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Information about several management client commands was missing
+        from (that is, truncated in) the output of the
+        <literal>HELP</literal> command.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
       <fixes bugid="48757"/>
     </bugs>
 

@@ -72,7 +204,9 @@
     </bugs>
 
     <versions>
+      <version ver="5.1.41-ndb-6.3.33"/>
       <version ver="5.1.41-ndb-7.0.14"/>
+      <version ver="5.1.41-ndb-7.1.2"/>
     </versions>
 
     <message>


Thread
svn commit - mysqldoc@docsrva: r19424 - trunk/dynamic-docs/changelogjon.stephens5 Mar