svn commit - mysqldoc@docsrva: r7889 - in trunk: dynamic-docs/command-optvars refman-5.1

[jon]

Author: jstephens
Date: 2007-09-20 17:58:27 +0200 (Thu, 20 Sep 2007)
New Revision: 7889

Log:

Added CGE-6.3.3 changelog

Documented CGE bugfixes:
  Bug #30877, Bug #31082

Documented ndb_conflict_fn_max status variable (CGE 6.3.3)



Modified:
   trunk/dynamic-docs/command-optvars/mysqld.xml
   trunk/refman-5.1/mysql-cluster.xml
   trunk/refman-5.1/news-5.1.xml


Modified: trunk/dynamic-docs/command-optvars/mysqld.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqld.xml	2007-09-20 13:44:12 UTC (rev 7888)
+++ trunk/dynamic-docs/command-optvars/mysqld.xml	2007-09-20 15:58:27 UTC (rev 7889)
Changed blocks: 1, Lines Added: 19, Lines Deleted: 0; 1275 bytes

@@ -2257,6 +2257,25 @@
       <introduced version="5.1.12"/>
     </versions>
   </option>
+  <option command="mysqld" section="ndb" id="Ndb_conflict_fn_max">
+    <xrefto id="option_mysqld_Ndb_conflict_fn_max"/>
+    <name>Ndb_conflict_fn_max</name>
+    <shortdescription lang="en">If the server is part of a MySQL Cluster
+      involved in cluster replication, the value of this variable
+      indicates the number of times that conflict resolution has been
+      applied</shortdescription>
+    <types>
+      <vartype isdynamic="no" class="status" scope="global"/>
+    </types>
+    <values vartype="numeric" platform="all">
+      <value default="0"/>
+    </values>
+    <versions>
+      <manual version="5.1"/>
+      <manual version="5.2"/>
+      <introduced version="5.1.22-ndb-6.3.3"/>
+    </versions>
+  </option>
   <option command="mysqld" section="server" id="Not_flushed_delayed_rows">
     <xrefto id="option_mysqld_Not_flushed_delayed_rows"/>
     <name>Not_flushed_delayed_rows</name>


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2007-09-20 13:44:12 UTC (rev 7888)
+++ trunk/refman-5.1/mysql-cluster.xml	2007-09-20 15:58:27 UTC (rev 7889)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 753 bytes

@@ -21552,6 +21552,14 @@
 
       </formalpara>
 
+      <para>
+        Beginning with MySQL 5.1.22-ndb-6.3.3, a server status variable
+        <literal>ndb_conflict_fn_max</literal> provides a count of the
+        number of times that conflict resolution for has been applied on
+        the current SQL node since the last time that
+        <command>mysqld</command> was started.
+      </para>
+
       <indexterm>
         <primary>conflict resolution</primary>
         <secondary>enabling</secondary>


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-09-20 13:44:12 UTC (rev 7888)
+++ trunk/refman-5.1/news-5.1.xml	2007-09-20 15:58:27 UTC (rev 7889)
Changed blocks: 7, Lines Added: 149, Lines Deleted: 6; 7235 bytes

@@ -682,9 +682,9 @@
       &mccge-series; releases based on MySQL 5.1.22.
     </para>
 
-    <section id="news-5-1-22-ndb-6-3-2">
+    <section id="news-5-1-22-ndb-6-3-3">
 
-      <title>Changes in release MySQL 5.1.22-ndb-6.3.2-beta (Not yet
released)</title>
+      <title>Changes in release MySQL 5.1.22-ndb-6.3.3-beta (20 September
2007)</title>
 
       <para role="release-level">
         This is a new Beta development release, fixing recently

@@ -696,8 +696,107 @@
         [js] Uncomment next para following release.
       </remark>
 
+      <para>
+        Like all releases for &mccge-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.22-ndb-6.3.3"/>.
+        The file
+        <filename>mysqlcom-5.1.22-ndb-6.3.3-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.19-ndb-6.3.0, MySQL 5.1.19-ndb-6.3.1, and
+        MySQL 5.1.19-ndb-6.3.2, as well as all bugfixes and feature
+        changes which were added in the mainline 5.1.21 and 5.1.22
+        releases; information about these can be found in
+        <xref linkend="news-5-1-21"/> and <xref linkend="news-5-1-22"/>.
+      </para>
+
 <!--
+        <important>
+          <formalpara>
+            
+            <title>Upgrading to MySQL 5.1.18-ndb-6.2.1 from a previous
release</title>
+            
+            <para>
+              
+            </para>
+            
+          </formalpara>
+          
+        </important>
+-->
+
       <para>
+        Functionality added or changed:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            A server status variable
+            <literal>ndb_conflict_fn_max</literal> now provides a count
+            of the number of times that conflict resolution for MySQL
+            Cluster Replication has been applied.
+          </para>
+
+          <para>
+            See
+            <xref linkend="mysql-cluster-replication-conflict-resolution"/>,
+            for more information.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+      <para>
+        This release fixes the following bug:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            Errors could sometimes occur during an online <literal>ADD
+            COLUMN</literal> under load. (Bug #31082)
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+    </section>
+
+    <section id="news-5-1-22-ndb-6-3-2">
+
+      <title>Changes in release MySQL 5.1.22-ndb-6.3.2-beta (07 September
2007)</title>
+
+      <para role="release-level">
+        This is a new Beta development release, fixing recently
+        discovered bugs and incorporating improvements made since the
+        previous &mccge-series; release.
+      </para>
+
+      <remark role="TODO">
+        [js] Uncomment next para following release.
+      </remark>
+
+      <para>
         Like all releases for &mccge-series;, this is a source-only
         release which you must compile and install using the
         instructions found in <xref linkend="installing-source"/>, and

@@ -709,7 +808,6 @@
         <filename>mysqlcom-5.1.22-ndb-6.3.2-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

@@ -819,6 +917,37 @@
 
         <listitem>
           <para>
+            <literal>NDB Cluster</literal>: An insufficiently
+            descriptive and potentially misleading Error 4006
+            (<errortext>Connect failure - out of connection
+            objects...</errortext>) was produced when either of the
+            following two conditions occurred:
+
+            <orderedlist>
+
+              <listitem>
+                <para>
+                  There were no more transaction records in the
+                  transaction coordinator
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  an <literal>Ndb</literal> object in the NDB API was
+                  initialized with insufficient parallellism
+                </para>
+              </listitem>
+
+            </orderedlist>
+
+            Separate error messages are now generated for each of these
+            two cases. (Bug #11313)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
             For micro-GCPs, fixed the assignment of <quote>fake</quote>
             CGI events so that they do not cause buckets to be sent out
             of order. Now, when assigning a GCI to a non-GCI event (that

@@ -829,20 +958,27 @@
           </para>
         </listitem>
 
+        <listitem>
+          <para>
+            When an <literal>NDB</literal> event was left behind but the
+            corresponding table was later recreated and received a new
+            table ID, the event could not be dropped. (Bug #30877)
+          </para>
+        </listitem>
+
       </itemizedlist>
 
     </section>
 
     <section id="news-5-1-22-ndb-6-2-6">
 
-      <title>Changes in release MySQL 5.1.22-ndb-6.2.6-beta (Not yet
released)</title>
+      <title>Changes in release MySQL 5.1.22-ndb-6.2.6-beta (20 September
2007)</title>
 
       <para role="release-level">
         This is a new Beta development release, fixing recently
         discovered bugs.
       </para>
 
-<!--
       <para>
         Like all releases for &mccge-series;, this is a source-only
         release which you must compile and install using the

@@ -855,7 +991,6 @@
         <filename>mysqlcom-5.1.22-ndb-6.2.6-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

@@ -939,6 +1074,14 @@
           </para>
         </listitem>
 
+        <listitem>
+          <para>
+            When an <literal>NDB</literal> event was left behind but the
+            corresponding table was later recreated and received a new
+            table ID, the event could not be dropped. (Bug #30877)
+          </para>
+        </listitem>
+
       </itemizedlist>
 
     </section>