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

[jon]

Author: jstephens
Date: 2007-03-23 10:45:55 +0100 (Fri, 23 Mar 2007)
New Revision: 5516

Log:

Documenting MCCGE bugfixes (Cluster/General):

  Bug #26825, Bug #27003, Bug #27087, Bug #27203, Bug #27233, 
  Bug #27286, Bug #27291



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-03-23 08:09:20 UTC (rev 5515)
+++ branches/telcos/refman-5.1/news-5.1.xml	2007-03-23 09:45:55 UTC (rev 5516)
Changed blocks: 2, Lines Added: 184, Lines Deleted: 1; 7324 bytes

@@ -156,7 +156,10 @@
         
         <listitem>
           <para>
-            
+            An incorrect assertion was made when sending a
+            <literal>TCKEYFAILREF</literal> or
+            <literal>TCKEYCONF</literal> message to a failed data node.
+            (Bug #26814)
           </para>
         </listitem>
         

@@ -1192,6 +1195,186 @@
       &current-series; releases based on MySQL 5.1.15.
     </para>
     
+    <section id="news-5-1-15-ndb-6-1-6">
+      
+      <title>Changes in release MySQL 5.1.15/NDB-6.1.6-beta (Not yet
+        released)</title>
+      
+      <para role="release-level">
+        This is a new Beta development release, fixing recently discovered
+        bugs and incorporating improvements made since the previous
+        &current-series; release.
+      </para>
+      
+<!--      
+      <para>
+        Like all releases for MySQL &current-series;, this is a
+        source-only release which you must compile and install using the
+        instructions found in <xref linkend="installing-source"/>, and in
+        <xref linkend="mysql-cluster-building"/>. You can download the
+        source code archive for this release from the MySQL FTP site at
+        <ulink
url="ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.15-ndb-6.1.5/"/>.
+        The file
+        <filename>mysqlcom-5.1.15-ndb-6.1.5-telco.tar.gz</filename> in
+        this directory contains the complete source archive.
+      </para>
+-->
+      
+      <para role="release-non-production">
+        <emphasis role="bold">NOTE</emphasis>: Although MySQL has worked
+        very hard to ensure a high level of quality, protect your data by
+        making a backup as you would for any software beta release. Please
+        refer to our bug database at <ulink url="http://bugs.mysql.com/"/>
+        for more details about the individual bugs fixed in this version.
+      </para>
+      
+      <para>
+        This Beta release incorporates all bugfixes and feature changes made in MySQL
+        5.1.14/NDB-6.1.0, MySQL 5.1.15/NDB-6.1.1, MySQL 5.1.15/NDB-6.1.2,
+        MySQL 5.1.15/NDB-6.1.3, MySQL 5.1.15/NDB-6.1.4, and MySQL
+        5.1.15/NDB-6.1.5. This version also incorporates all bugfixes
+        and feature changes which were added in the mainline MySQL 5.1
+        releases up to and including 5.1.15 (see <xref linkend="news-5-1-15"/>).
+      </para>
+      
+<!--      
+      <important>
+        <formalpara>
+          <title>Upgrading to MySQL 5.1.15/NDB-6.1.6 from a previous
release</title>
+          
+          
+          
+          <para>
+            This release is not binary compatible with releases previous
+            to MySQL 5.1.15/NDB-6.1.3. This means that:
+            
+            <itemizedlist>
+              
+              <listitem>
+                <para>
+                  You cannot perform an online upgrade to this release
+                  from MySQL 5.1.14/NDB-6.1.0, MySQL 5.1.15/NDB-6.1.1,
+                  MySQL 5.1.15/NDB-6.1.2, or any of the mainline MySQL 5.1
+                  releases. When upgrading from one of these versions, you
+                  must shut down the cluster, replace all binaries, then
+                  restart the cluster.
+                </para>
+              </listitem>
+              
+              <listitem>
+                <para>
+                  You must recompile all NDB API and MGM API applications
+                  used with a previous version of MySQL Cluster, including
+                  those compiled against MySQL 5.1.15/NDB-6.1.3.
+                </para>
+              </listitem>
+              
+            </itemizedlist>
+            
+            This release is also not backwards compatible with MySQL
+            -5.1.15/NDB-6.1.14 or any release previous to MySQL
+            -5.1.15/NDB-6.1.14 due to changes in the
+            <literal>mysql</literal> system database. See
+            <citetitle>Functionality added or changed</citetitle> for more
+            information.
+          </para>
+        </formalpara>
+      </important>
+-->
+      
+<!--      
+      <para>
+        Functionality added or changed:
+      </para>
+      
+      <itemizedlist>
+        
+        <listitem>
+          <para>
+            <emphasis role="bold">Incompatible change</emphasis>: The
+            schema for the <literal>ndb_apply_status</literal> table in
+            the <literal>mysql</literal> system database has changed. When
+            upgrading to this release from a previous &current-series; or
+            mainline MySQL 5.1 release, you must drop the
+            <literal>mysql.ndb_apply_status</literal> table, then restart
+            the server in order for the table to be re-created with the
+            new schema.
+          </para>
+          
+          <para>
+            See <xref linkend="mysql-cluster-replication-schema"/>, for
+            additional information.
+          </para>
+        </listitem>
+        
+      </itemizedlist>
+-->
+      
+      <para>
+        This release fixes the following bugs:
+      </para>
+      
+      <itemizedlist>
+        <listitem>
+          <para>
+            It was not possible to set
+            <literal>LockPagesInMainMemory</literal> equal to
+            <literal>0</literal>. (Bug #27291) 
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+            A race condition could sometimes occur if the node
+            acting as master failed while node IDs were still being
+            allocated during startup. (Bug #27286)
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            When a data node was taking over as the master node, a race
+            condition could sometimes  occur as the node was assuming
+            responsibility for handling of global checkpoints. (Bug #27283)
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            A delete operation using a scan following by an insert using
+            a scan could cause a data node to fail. (Bug #27203)
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The same failed request from an API node could be handled by
+            the cluster multiple times, resulting in reduced performance. (Bug #27087) 
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            <command>mysqld</command> processes would sometimes crash
+            under high load. (Bug #26825)
+          </para>
+          
+          <para>
+            This improves on and replaces the fix for this bug that was
+            made in MySQL 5.1.15/NDB-6.1.5.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The failure of a data node while restarting could cause
+            other data nodes to hang or crash. (Bug #27003)
+          </para>
+        </listitem>
+        
+      </itemizedlist>
+      
+    </section>
+    
     <section id="news-5-1-15-ndb-6-1-5">
       
       <title>Changes in release MySQL 5.1.15/NDB-6.1.5-beta (15 March
2007)</title>