List:Commits« Previous MessageNext Message »
From:jon Date:September 2 2006 6:45am
Subject:svn commit - mysqldoc@docsrva: r3205 - in trunk: ndbapi refman-5.0 refman-5.1
View as plain text  
Author: jstephens
Date: 2006-09-02 08:45:22 +0200 (Sat, 02 Sep 2006)
New Revision: 3205

Log:
Documenting Cluster bugfixes:
	- General: Bug #13985, Bug #19852, Bug #21050, Bug #21670
	- APIs: Bug #21129, BUg #21671

Uncommented MGM API ndb_logevent_get_fd() function description in API Guide

Modified:
   trunk/ndbapi/mgm-api.xml
   trunk/refman-5.0/news-5.0.xml
   trunk/refman-5.1/news-5.1.xml


Modified: trunk/ndbapi/mgm-api.xml
===================================================================
--- trunk/ndbapi/mgm-api.xml	2006-09-02 05:34:16 UTC (rev 3204)
+++ trunk/ndbapi/mgm-api.xml	2006-09-02 06:45:22 UTC (rev 3205)
Changed blocks: 4, Lines Added: 6, Lines Deleted: 5; 935 bytes

@@ -520,7 +520,7 @@
 
       </section>
 
-<!--
+
         <section id="ndb-logevent-get-fd">
 
         <title><literal>ndb_logevent_get_fd()</literal></title>

@@ -535,7 +535,8 @@
 
           <para>
             This function retrieves a file descriptor from an
-            <literal>NdbMgmLogEventHandle</literal>.
+            <literal>NdbMgmLogEventHandle</literal>. It was implemented
+            in MySQL 5.1.12.
           </para>
 
         </formalpara>

@@ -583,8 +584,8 @@
 
         </formalpara>
 
--->
 
+
 <!--
         <formalpara>
 

@@ -599,11 +600,11 @@
         </formalpara>
 -->
 
-<!--
 
+
     </section>
--->
 
+
       <section id="ndb-logevent-get-next">
 
         <title><literal>ndb_logevent_get_next()</literal></title>


Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml	2006-09-02 05:34:16 UTC (rev 3204)
+++ trunk/refman-5.0/news-5.0.xml	2006-09-02 06:45:22 UTC (rev 3205)
Changed blocks: 4, Lines Added: 55, Lines Deleted: 5; 3347 bytes

@@ -426,9 +426,9 @@
 
       <listitem>
         <para>
-          <command>ndb_size.pl</command> and
-          <command>ndb_error_reporter</command> were missing from RPM
-          packages. (Bug #20426)
+          <literal>NDB Cluster</literal>: <command>ndb_size.pl</command>
+          and <command>ndb_error_reporter</command> were missing from
+          RPM packages. (Bug #20426)
         </para>
       </listitem>
 

@@ -880,9 +880,59 @@
           (Bug #21007)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (Direct APIs): Invoking the MGM
+          API function <literal>ndb_mgm_listen_event()</literal> caused
+          a memory leak. (Bug #21671)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (Direct APIs): The MGM API
+          function <literal>ndb_logevent_get_fd()</literal> was not
+          actually implemented. (Bug #21129)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A memory leak was found when running
+          <literal><command>ndb_mgm</command> -e "SHOW"</literal>. (Bug
+          #21670) 
+        </para>
+      </listitem>
 
       <listitem>
         <para>
+          <literal>NDB Cluster</literal>: Restarting a data node while
+          DDL operations were in progress on the cluster could cause
+          other data nodes to fail. This could also lead to
+          <command>mysqld</command> hanging or crashing under some
+          circumstances. (Bug #21017, Bug #21050)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: An issue that arose from a
+          patch for Bug #19852 made in MySQL 5.0.23 was corrected. (See
+          <xref linkend="news-5-0-23"/>.)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The management client
+          <literal>ALL STATUS</literal> command could sometimes report
+          the status of some data nodes incorrectly. (Bug #13985)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal>: Some queries involving joins
           on very large <literal>NDB</literal> tables could crash the
           MySQL server. (Bug #21059)

@@ -995,7 +1045,7 @@
           revert the patch. 
         </remark>
         <para>
-          <literal>NDB Cluster</literal> (NDB API): When multiple
+          <literal>NDB Cluster</literal> (Direct APIs): When multiple
           processes or threads in parallel were performing a scan with
           an exclusive lock, then updated only one record from the
           subset cached in the client by

@@ -1012,7 +1062,7 @@
 
       <listitem>
         <para>
-          <literal>NDB Cluster</literal> (NDB API):
+          <literal>NDB Cluster</literal> (Direct APIs):
           <literal>NdbScanOperation::readTuples()</literal> and
           <literal>NdbIndexScanOperation::readTuples()</literal> ignored
           the <replaceable>batch</replaceable> parameter. (Bug #20252)


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2006-09-02 05:34:16 UTC (rev 3204)
+++ trunk/refman-5.1/news-5.1.xml	2006-09-02 06:45:22 UTC (rev 3205)
Changed blocks: 4, Lines Added: 34, Lines Deleted: 2; 2305 bytes

@@ -2024,6 +2024,22 @@
           could cause errors or crash the server. (Bug #20583)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (Direct APIss): Invoking the MGM
+          API function <literal>ndb_mgm_listen_event()</literal> caused
+          a memory leak. (Bug #21671)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The management client
+          <literal>ALL STATUS</literal> command could sometimes report
+          the status of some data nodes incorrectly. (Bug #13985)
+        </para>
+      </listitem>
 
       <listitem>
         <para>

@@ -2060,6 +2076,22 @@
           cluster log for each cluster node. (Bug #21044)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          A memory leak was found when running
+          <literal><command>ndb_mgm</command> -e "SHOW"</literal>. (Bug
+          #21670) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (Direct APIs): The MGM API
+          function <literal>ndb_logevent_get_fd()</literal> was not
+          actually implemented. (Bug #21129)
+        </para>
+      </listitem>
 
       <listitem>
         <para>

@@ -2191,7 +2223,7 @@
           revert the patch. 
         </remark>
         <para>
-          <literal>NDB Cluster</literal> (NDB API): When multiple
+          <literal>NDB Cluster</literal> (Direct APIs): When multiple
           processes or threads in parallel were performing a scan with
           an exclusive lock, then updated only one record from the
           subset cached in the client by

@@ -2208,7 +2240,7 @@
 
       <listitem>
         <para>
-          <literal>NDB Cluster</literal> (NDB API):
+          <literal>NDB Cluster</literal> (Direct APIs):
           <literal>NdbScanOperation::readTuples()</literal> and
           <literal>NdbIndexScanOperation::readTuples()</literal> ignored
           the <replaceable>batch</replaceable> parameter. (Bug #20252)


Thread
svn commit - mysqldoc@docsrva: r3205 - in trunk: ndbapi refman-5.0 refman-5.1jon2 Sep