svn commit - mysqldoc@docsrva: r5798 - branches/telcos/refman-5.1

[jon]

Author: jstephens
Date: 2007-04-10 15:19:59 +0200 (Tue, 10 Apr 2007)
New Revision: 5798

Log:

Documenting MCCGE bugfixes:

  Bug #21494, Bug #27081, Bug #27529, Bug #27663



Modified:
   branches/telcos/refman-5.1/news-5.1.xml


Modified: branches/telcos/refman-5.1/news-5.1.xml
===================================================================
--- branches/telcos/refman-5.1/news-5.1.xml	2007-04-10 13:16:53 UTC (rev 5797)
+++ branches/telcos/refman-5.1/news-5.1.xml	2007-04-10 13:19:59 UTC (rev 5798)
Changed blocks: 2, Lines Added: 65, Lines Deleted: 5; 3648 bytes

@@ -157,6 +157,47 @@
         
         <listitem>
           <para>
+            <emphasis role="bold">Cluster APIs</emphasis>: An issue with
+            the way in which the
+            <literal>NdbDictionary::Dictionary::listEvents()</literal>
+            method freed resources could sometimes lead to memory
+            corruption. (Bug #27663)
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            <emphasis role="bold">Cluster APIs</emphasis>: Using
+            <literal>NdbBlob::writeData()</literal> to write data in the
+            middle of an existing blob value (that is, updating the value)
+            could overwrite some data past the end of the data to be
+            changed. (Bug #27018)
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            <emphasis role="bold">Cluster Replication</emphasis>: Trying
+            to replicate a large number of frequent updates with a
+            relatively small relay log
+            (<literal>max-relay-log-size</literal> set to 1M or less)
+            could cause the slave to crash. (Bug #27529) 
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            <emphasis role="bold">Cluster Replication</emphasis>: An SQL
+            node acting as a replication master server could be a single
+            point of failure; that is, if it failed, the replication
+            slave had no way of knowing this, which could result in a
+            mismatch of data between the master and the slave. (Bug
+            #21494) 
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
             Memory usage of a <command>mysqld</command> process grew
             even while idle. (Bug #27560)
           </para>

@@ -1398,16 +1439,35 @@
         
         <listitem>
           <para>
-            <literal>NDB Cluster</literal>: Under certain rare
-            circumstances, <literal>DROP TABLE</literal> or
-            <literal>TRUNCATE</literal> of an
<literal>NDB</literal> table
-            could cause a node failure or forced cluster shutdown. (Bug
-            #27581)  
+            <emphasis role="bold">Cluster APIs</emphasis>: An issue with
+            the way in which the
+            <literal>NdbDictionary::Dictionary::listEvents()</literal>
+            method freed resources could sometimes lead to memory
+            corruption. (Bug #27663)
           </para>
         </listitem>
         
         <listitem>
           <para>
+            <emphasis role="bold">Cluster Replication</emphasis>: Trying
+            to replicate a large number of frequent updates with a
+            relatively small relay log
+            (<literal>max-relay-log-size</literal> set to 1M or less)
+            could cause the slave to crash. (Bug #27529) 
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            Under certain rare circumstances, <literal>DROP
+            TABLE</literal> or <literal>TRUNCATE</literal> of an
+            <literal>NDB</literal> table could cause a node failure or
+            forced cluster shutdown. (Bug #27581)  
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
             Memory usage of a <command>mysqld</command> process grew
             even while idle. (Bug #27560)
           </para>