svn commit - mysqldoc@docsrva: r3826 - in trunk: refman-4.1 refman-5.0 refman-5.1

[jon]

Author: jstephens
Date: 2006-11-02 11:30:28 +0100 (Thu, 02 Nov 2006)
New Revision: 3826

Log:


Documenting Cluster bugfixes and associated feature/function changes:

  Bug # 15303, Bug # 17582, Bug # 19045, Bug # 19047, Bug # 19148,
  Bug # 19198, Bug # 19651, Bug # 19787, Bug # 19873, Bug # 19914,
  Bug # 20446, Bug # 20575, Bug # 20848, Bug # 20895, Bug # 21056,
  Bug # 21072, Bug # 21378, Bug # 21345, Bug # 21530, Bug # 21535,
  Bug # 21585, Bug # 21756, Bug # 21799, Bug # 21873, Bug # 21994,
  Bug # 22195, Bug # 22295, Bug # 22838, Bug # 23103, Bug # 22892,
  Bug # 22893, Bug # 23200, Bug # 23203, Bug # 23210, Bug # 23449,
  Bug # 23494, Bug #23502



Modified:
   trunk/refman-4.1/mysql-cluster.xml
   trunk/refman-4.1/news-4.1.xml
   trunk/refman-5.0/database-administration.xml
   trunk/refman-5.0/mysql-cluster.xml
   trunk/refman-5.0/releasenotes-cs-5.0.xml
   trunk/refman-5.1/database-administration.xml
   trunk/refman-5.1/mysql-cluster.xml
   trunk/refman-5.1/news-5.1.xml


Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml	2006-11-02 04:49:37 UTC (rev 3825)
+++ trunk/refman-4.1/mysql-cluster.xml	2006-11-02 10:30:28 UTC (rev 3826)
Changed blocks: 2, Lines Added: 15, Lines Deleted: 1; 1154 bytes

@@ -12393,7 +12393,7 @@
       </indexterm>
 
       <indexterm>
-        <primary><command>ndb_restore</command> (MySQL Cluster
program)</primary>
+        <primary><command>ndb_restore</command></primary>
       </indexterm>
 
       <para>

@@ -12676,6 +12676,20 @@
           </tbody>
         </tgroup>
       </informaltable>
+      
+      <indexterm>
+        <primary><command>ndb_restore</command></primary>
+        <secondary>errors</secondary>
+      </indexterm>
+      
+      <para>
+        <emphasis role="bold">Note</emphasis>:
+        <command>ndb_restore</command> reports both temporary and
+        permanent errors. In the case of temporary errors, it may able
+        to recover from them. Beginning with MySQL 4.1.22, it reports
+        <literal>Restore successful, but encountered temporary error,
+          please look at configuration</literal> in such cases.
+      </para>
 
     </section>
 


Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml	2006-11-02 04:49:37 UTC (rev 3825)
+++ trunk/refman-4.1/news-4.1.xml	2006-11-02 10:30:28 UTC (rev 3826)
Changed blocks: 2, Lines Added: 121, Lines Deleted: 11; 5575 bytes

@@ -549,17 +549,6 @@
 
       <listitem>
         <para>
-          The <command>ndb_mgm</command> program was included in both
-          the <literal>MySQL-ndb-tools</literal> and
-          <literal>MySQL-ndb-management</literal> RPM packages,
-          resulting in a conflict if both were installed. Now
-          <command>ndb_mgm</command> is included only in
-          <literal>MySQL-ndb-tools</literal>. (Bug #21058)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           The <literal>myisam_stats_method</literal> variable was
           mishandled when set from an option file or on the command
           line. (Bug #21054)

@@ -726,9 +715,130 @@
           for client connections. (Bug #7192)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Restoring a cluster failed if
+          there were any tables with 128 or more columns. (Bug #23502)
+        </para>
+      </listitem>
 
       <listitem>
         <para>
+          <literal>NDB Cluster</literal>: <literal>INSERT ... ON
+            DUPLICATE KEY UPDATE</literal> on an <literal>NDB</literal>
+          table could lead to deadlocks and memory leaks. (Bug #23200)
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: If a node restart could not be
+          performed from the REDO log, no node takeover took place. This
+          could cause partitions to be left empty during a system
+          restart. (Bug #22893)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Multiple node restarts in
+          rapid succession could cause a system restart to fail (Bug
+          #22892), or induce a race condition (Bug #23210).
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The node recovery algorithm
+          was missing a version check for tables in the
+          <literal>ALTER_TABLE_COMMITTED</literal> state (as opposed to
+          the <literal>TABLE_ADD_COMMITTED</literal> state, which has
+          the version check). This could cause inconsistent schemas
+          across nodes following node recovery. (Bug #21756)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The output for the
<option>--help</option>
+          option used with <literal>NDB</literal> executable programs
+          (<command>ndbd</command>, <command>ndb_mgm</command>,
+          <command>ndb_restore</command>,
<command>ndb_config</command>,
+          and so on) referred to the <filename>Ndb.cfg</filename>  file,
+          instead of <filename>my.cnf</filename>. (Bug #21585) 
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The
<command>ndb_mgm</command>
+          management client did not set the exit status on errors,
+          always returning 0 instead. (Bug #21530)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Cluster logs were not rotated
+          following the first rotation cycle. (Bug #21345)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: When inserting a row into an
+          <literal>NDB</literal> table with a duplicate value for a
+          non-primary unique key, the error issued would reference the
+          wrong key. (Bug #21072)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Under some circumstances,
+          local checkpointing would hang, keeping any unstarted nodes
+          from being started. (Bug #20895) 
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: In some cases where
+          <literal>SELECT COUNT(*)</literal> from an
+          <literal>NDB</literal> table should have yielded an error,
+          <literal>MAX_INT</literal> was returned instead. (Bug #19914)  
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>:
<command>ndb_restore</command> did not always
+          make clear that it had recovered successfully from temporary
+          errors while restoring a cluster backup. (Bug #19651)
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: A problem with takeover during
+          a system restart caused ordered 
+          indexes to be rebuilt incorrectly. (Bug #15303)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The
<command>ndb_mgm</command>
+          program was included in both the
+          <literal>MySQL-ndb-tools</literal> and
+          <literal>MySQL-ndb-management</literal> RPM packages,
+          resulting in a conflict if both were installed. Now 
+          <command>ndb_mgm</command> is included only in
+          <literal>MySQL-ndb-tools</literal>. (Bug #21058)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal>:
<command>ndb_size.pl</command>
           and <command>ndb_error_reporter</command> were missing from
           RPM packages. (Bug #20426)


Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml	2006-11-02 04:49:37 UTC (rev 3825)
+++ trunk/refman-5.0/database-administration.xml	2006-11-02 10:30:28 UTC (rev 3826)
Changed blocks: 2, Lines Added: 7, Lines Deleted: 2; 1001 bytes

@@ -9555,8 +9555,8 @@
           </listitem>
 
           <listitem>
-            <para id="optvar_Ndb_number_of_storage_nodes">
-              <literal>Ndb_number_of_storage_nodes</literal>
+            <para id="optvar_Ndb_number_of_data_nodes">
+              <literal>Ndb_number_of_data_nodes</literal>
             </para>
 
             <para>

@@ -9568,6 +9568,11 @@
               If the server is not part of a MySQL Cluster, then the
               value of this variable is 0.
             </para>
+            
+            <para>
+              Prior to MySQL 5.0.29, this variable was named
+              <literal>Ndb_number_of_storage_nodes</literal>.
+              </para>
           </listitem>
 
           <listitem>


Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml	2006-11-02 04:49:37 UTC (rev 3825)
+++ trunk/refman-5.0/mysql-cluster.xml	2006-11-02 10:30:28 UTC (rev 3826)
Changed blocks: 4, Lines Added: 34, Lines Deleted: 4; 2223 bytes

@@ -9637,6 +9637,21 @@
         </para>
 
         <itemizedlist>
+          
+          <listitem>
+            <para>
+              <option>--bind-address</option>
+            </para>
+            
+            <para>
+              Causes <command>ndbd</command> to bind to a specific
+              network interface. This option has no default value. 
+            </para>
+            
+            <para>
+              This option was added in MySQL 5.0.29.
+            </para>
+          </listitem>
 
           <listitem>
             <para>

@@ -12438,7 +12453,7 @@
       </indexterm>
 
       <indexterm>
-        <primary><command>ndb_restore</command> (MySQL Cluster
program)</primary>
+        <primary><command>ndb_restore</command></primary>
       </indexterm>
 
       <para>

@@ -12721,7 +12736,22 @@
           </tbody>
         </tgroup>
       </informaltable>
+      
+      <indexterm>
+        <primary><command>ndb_restore</command></primary>
+        <secondary>errors</secondary>
+      </indexterm>
+      
+      <para>
+        <emphasis role="bold">Note</emphasis>:
+        <command>ndb_restore</command> reports both temporary and
+        permanent errors. In the case of temporary errors, it may able
+        to recover from them. Beginning with MySQL 5.0.29, it reports
+        <literal>Restore successful, but encountered temporary error,
+          please look at configuration</literal> in such cases.
+      </para>
 
+
     </section>
 
     <section id="mysql-cluster-backup-configuration">

@@ -13274,9 +13304,9 @@
           </para>
 
           <para>
-            <emphasis role="bold">Note</emphasis>: The use of
-            <option>-c</option> as a short version for this option is
-            not currently supported with <command>ndb_config</command>.
+            The use of <option>-c</option> as a short version for this
+            option is supported for <command>ndb_config</command>
+            beginning with MySQL 5.0.29.
           </para>
         </listitem>
 


Modified: trunk/refman-5.0/releasenotes-cs-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-cs-5.0.xml	2006-11-02 04:49:37 UTC (rev 3825)
+++ trunk/refman-5.0/releasenotes-cs-5.0.xml	2006-11-02 10:30:28 UTC (rev 3826)
Changed blocks: 1, Lines Added: 302, Lines Deleted: 0; 10278 bytes

@@ -26,6 +26,308 @@
     earlier versions, see <xref linkend="news"/>.
   </para>
 
+  <section id="releasenotes-cs-5-0-29">
+
+    <title>Release Notes for MySQL Community Server 5.0.29 (Not Yet
+      Released)</title>
+    
+    <para role="release-level">
+      This is a bugfix release for the current production release
+      family.
+    </para>
+
+    <para>
+      Functionality added or changed:
+    </para>
+    
+    <itemizedlist>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Added the --bind-address
+          option for <command>ndbd</command>. This allows a data node
+          process to be bound to a specific network interface. (Bug
+          #22195) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para><literal>NDB Cluster</literal>: The
+          <literal>Ndb_number_of_storage_nodes</literal> system variable was
+          renamed to <literal>Ndb_number_of_data_nodes</literal>. (Bug
#20848)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The
+          <command>ndb_config</command> utility now accepts
+          <option>-c</option> as a short form of the
+          <option>--ndb-connectstring</option> option. (Bug #22295) 
+        </para>
+      </listitem>
+
+      
+    </itemizedlist>
+    
+    
+    <para>
+      Bugs fixed:
+    </para>
+
+    <itemizedlist>
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: A problem with takeover during
+          a system restart caused ordered 
+          indexes to be rebuilt incorrectly. (Bug #15303)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The
<command>ndb_config</command> utility
+          did not perform host lookups correctly when using the
<option>--host</option>
+          option. (Bug #17582)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The
<command>ndb_config</command> utility
+          did not perform host lookups correctly when using the
<option>--host</option>
+          option (Bug #17582)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The error returned by the
+          cluster when too many nodes were defined did not make clear
+          the nature of the problem. (Bug #19045)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <command>ndb_mgm -e show |
+            head</command> would hang after displaying the first 10
+          lines of output. (Bug #19047)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: In rare situations with
+          resource shortages, a crash could result from insufficient
+          <literal>IndexScanOperations</literal>. (Bug #19198)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>:
<command>ndb_restore</command> did not always
+          make clear that it had recovered successfully from temporary
+          errors while restoring a cluster backup. (Bug #19651)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Error messages given when
+          trying to make online changes parameters such as
+          <literal>NoOfReplicas</literal> thast can only be changed via
+          a complete shutdown and restart of the cluster did not
+          indicate the true nature of the problem. (Bug #19787)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Following the restart of an MGM
node,
+          the Cluster management client did not automatically reconnect.
+          (Bug #19873)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: In some cases where
+          <literal>SELECT COUNT(*)</literal> from an
+          <literal>NDB</literal> table should have yielded an error,
+          <literal>MAX_INT</literal> was returned instead. (Bug #19914)  
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (<literal>NDB</literal>
API):
+          When multiple processes or threads in parallel performed the
+          same ordered scan with exclusive lock and updating the
+          retrieved records, the scan could skip some records, which were
+          not updated as the result. (Bug #20446)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Using an invalid node ID with
+          the management client <literal>STOP</literal> command could
+          cause <command>ndb_mgm</command> to hang. (Bug #20575)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Under some circumstances,
+          local checkpointing would hang, keeping any unstarted nodes
+          from being started. (Bug #20895) 
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Condition pushdown did not
+          work correctly with <literal>DATETIME</literal> columns. (Bug
+          #21056)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: When inserting a row into an
+          <literal>NDB</literal> table with a duplicate value for a
+          non-primary unique key, the error issued would reference the
+          wrong key. (Bug #21072)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Cluster logs were not rotated
+          following the first rotation cycle. (Bug #21345)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The
<command>ndb_mgm</command>
+          management client did not set the exit status on errors,
+          always returning 0 instead. (Bug #21530)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Partition distribution keys
+          were updated only for the primary and starting replicas during
+          node recovery. This could lead to node failure recovery for
+          clusters having an odd number of replicas. (Bug #21535)
+        </para>
+        
+        <para>
+          <emphasis role="bold">Note</emphasis>: We recommend values
+          for <literal>NumberOfReplicas</literal> that are even powers
+          of 2, for best results.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The output for the
<option>--help</option>
+          option used with <literal>NDB</literal> executable programs
+          (<command>ndbd</command>, <command>ndb_mgm</command>,
+          <command>ndb_restore</command>,
<command>ndb_config</command>,
+          and so on) referred to the <filename>Ndb.cfg</filename>  file,
+          instead of <filename>my.cnf</filename>. (Bug #21585) 
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The node recovery algorithm
+          was missing a version check for tables in the
+          <literal>ALTER_TABLE_COMMITTED</literal> state (as opposed to
+          the <literal>TABLE_ADD_COMMITTED</literal> state, which has
+          the version check). This could cause inconsistent schemas
+          across nodes following node recovery. (Bug #21756)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: A scan timeout returned Error
+          4028 (<errortext>Node failure caused abort of
+          transaction</errortext>) instead of Error 4008
+          (<errortext>Node failure caused abort of
+          transaction...</errortext>). (Bug #21799)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The
<option>--help</option>
+          output from <literal>NDB</literal> 
+          binaries did not include file-related options. (Bug #21994)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Multiple node restarts in
+          rapid succession could cause a system restart to fail (Bug
+          #22892), or induce a race condition (Bug #23210).
+        </para>
+      </listitem>
+
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: If a node restart could not be
+          performed from the REDO log, no node takeover took place. This
+          could cause partitions to be left empty during a system
+          restart. (Bug #22893)
+        </para>
+      </listitem>
+
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <literal>INSERT ... ON
+            DUPLICATE KEY UPDATE</literal> on an <literal>NDB</literal>
+          table could lead to deadlocks and memory leaks. (Bug #23200)
+        </para>
+      </listitem>
+
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The management client command
+          <literal>ALL DUMP 1000</literal> would cause the cluster to
+          crash if data nodes were connected to the cluster but not yret
+          fully started. (Bug #23203)
+        </para>
+      </listitem>
+
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Cluster backups would fail
+          when there were more than 2048 schema objects in the cluster.
+          (Bug #23499)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Restoring a cluster failed if
+          there were any tables with 128 or more columns. (Bug #23502)
+        </para>
+      </listitem>
+    </itemizedlist>
+
+  </section>
+
   <section id="releasenotes-cs-5-0-27">
 
     <title>Release Notes for MySQL Community Server 5.0.27 (21 October
2006)</title>


Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml	2006-11-02 04:49:37 UTC (rev 3825)
+++ trunk/refman-5.1/database-administration.xml	2006-11-02 10:30:28 UTC (rev 3826)
Changed blocks: 2, Lines Added: 7, Lines Deleted: 2; 999 bytes

@@ -9744,8 +9744,8 @@
           </listitem>
 
           <listitem>
-            <para id="optvar_Ndb_number_of_storage_nodes">
-              <literal>Ndb_number_of_storage_nodes</literal>
+            <para id="optvar_Ndb_number_of_data_nodes">
+              <literal>Ndb_number_of_data_nodes</literal>
             </para>
 
             <para>

@@ -9757,6 +9757,11 @@
               If the server is not part of a MySQL Cluster, then the
               value of this variable is 0.
             </para>
+            
+            <para>
+              Prior to MySQL 5.1.12, this variable was named
+              <literal>Ndb_number_of_storage_nodes</literal>.
+            </para>
           </listitem>
 
           <listitem>


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2006-11-02 04:49:37 UTC (rev 3825)
+++ trunk/refman-5.1/mysql-cluster.xml	2006-11-02 10:30:28 UTC (rev 3826)
Changed blocks: 4, Lines Added: 34, Lines Deleted: 4; 2223 bytes

@@ -9664,6 +9664,21 @@
         </para>
 
         <itemizedlist>
+          
+          <listitem>
+            <para>
+              <option>--bind-address</option>
+            </para>
+            
+            <para>
+              Causes <command>ndbd</command> to bind to a specific
+              network interface. This option has no default value. 
+            </para>
+            
+            <para>
+              This option was added in MySQL 5.1.12.
+            </para>
+          </listitem>
 
           <listitem>
             <para>

@@ -12482,7 +12497,7 @@
       </indexterm>
 
       <indexterm>
-        <primary><command>ndb_restore</command> (MySQL Cluster
program)</primary>
+        <primary><command>ndb_restore</command></primary>
       </indexterm>
 
       <para>

@@ -12792,7 +12807,22 @@
           </tbody>
         </tgroup>
       </informaltable>
+      
+      <indexterm>
+        <primary><command>ndb_restore</command></primary>
+        <secondary>errors</secondary>
+      </indexterm>
+      
+      <para>
+        <emphasis role="bold">Note</emphasis>:
+        <command>ndb_restore</command> reports both temporary and
+        permanent errors. In the case of temporary errors, it may able
+        to recover from them. Beginning with MySQL 5.1.12, it reports
+        <literal>Restore successful, but encountered temporary error,
+          please look at configuration</literal> in such cases.
+      </para>
 
+
     </section>
 
     <section id="mysql-cluster-backup-configuration">

@@ -13349,9 +13379,9 @@
           </para>
 
           <para>
-            <emphasis role="bold">Note</emphasis>: The use of
-            <option>-c</option> as a short version for this option is
-            not currently supported with <command>ndb_config</command>.
+            The use of <option>-c</option> as a short version for this
+            option is supported for <command>ndb_config</command>
+            beginning with MySQL 5.1.12.
           </para>
         </listitem>
 


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2006-11-02 04:49:37 UTC (rev 3825)
+++ trunk/refman-5.1/news-5.1.xml	2006-11-02 10:30:28 UTC (rev 3826)
Changed blocks: 7, Lines Added: 288, Lines Deleted: 19; 12291 bytes

@@ -71,7 +71,7 @@
       additions to be reported.
     </remark>
 
-<!--
+
   <para>
     Functionality added or changed:
   </para>

@@ -79,12 +79,17 @@
   <itemizedlist>
 
     <listitem>
-      <para></para>
+      <para>
+        A change in the interfaces for the
+        <literal>INFORMATION_SCHEMA.FILES</literal> table have made the
+        table accessible to storage engines other than
+        <literal>NDB</literal>. (Bug #23013) 
+      </para>
     </listitem>
 
   </itemizedlist>
--->
 
+
     <para>
       Bugs fixed:
     </para>

@@ -230,7 +235,89 @@
           in table corruption. (Bug #8283)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Restoring a cluster failed if
+          there were any tables with 128 or more columns. (Bug #23494,
+          Bug #23502)
+        </para>
+      </listitem>
 
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Cluster backups would fail
+          when there were more than 2048 schema objects in the cluster.
+          (Bug #23499)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The management client command
+          <literal>ALL DUMP 1000</literal> would cause the cluster to
+          crash if data nodes were connected to the cluster but not yret
+          fully started. (Bug #23203)
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <literal>INSERT ... ON
+            DUPLICATE KEY UPDATE</literal> on an <literal>NDB</literal>
+          table could lead to deadlocks and memory leaks. (Bug #23200)
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: If a node restart could not be
+          performed from the REDO log, no node takeover took place. This
+          could cause partitions to be left empty during a system
+          restart. (Bug #22893)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Multiple node restarts in
+          rapid succession could cause a system restart to fail (Bug
+          #22892), or induce a race condition (Bug #23210).
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Attempting to create a unique
+          constraint with <literal>USING HASH</literal> on an
+          <literal>NDB</literal> table caused
<command>mysqld</command>
+          to crash. (Bug #21873)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: When inserting a row into an
+          <literal>NDB</literal> table with a duplicate value for a
+          non-primary unique key, the error issued would reference the
+          wrong key. (Bug #21072)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (<literal>NDB</literal>
API):
+          When multiple processes or threads in parallel performed the
+          same ordered scan with exclusive lock and updating the
+          retrieved records, the scan could skip some records, which were
+          not updated as the result. (Bug #20446)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para><literal>NDB Cluster</literal>: Aborting a cluster backup
+          too soon after starting it caused a forced shutdown of the
+          data nodes. (Bug #19148)</para>
+      </listitem>
+
     </itemizedlist>
 
   </section>

@@ -671,9 +758,46 @@
           be specified for processing binary log files. (Bug #18351)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Inserting into an
+          <literal>NDB</literal> table failed when the table had no
+          primary key but had a unique key added after table was created
+          on one or more <literal>NOT NULL</literal> columns. This
+          occurred when the unique key had been adding using either
+          <literal>ALTER TABLE</literal> or <literal>CREATE UNIQUE
+            KEY</literal>. (Bug #22838)
+        </para>
+      </listitem>
 
       <listitem>
         <para>
+          <literal>NDB Cluster</literal>: The
+          <command>ndb_config</command> utility now accepts
+          <option>-c</option> as a short form of the
+          <option>--ndb-connectstring</option> option. (Bug #22295) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Added the --bind-address
+          option for <command>ndbd</command>. This allows a data node
+          process to be bound to a specific network interface. (Bug
+          #22195) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para><literal>NDB Cluster</literal>: The
+          <literal>Ndb_number_of_storage_nodes</literal> system variable was
+          renamed to <literal>Ndb_number_of_data_nodes</literal>. (Bug
#20848)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Added the <option>--ndb-use-copying-alter-table</option>
           option to <command>mysqld</command> to provide a fallback in
           case of problems with online <literal>ALTER TABLE</literal>

@@ -696,14 +820,6 @@
 
       <listitem>
         <para>
-          <literal>NDB Cluster</literal>: Some queries involving joins
-          on very large <literal>NDB</literal> tables could crash the
-          MySQL server. (Bug #21059)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           <literal>NDB Cluster</literal>: The status variables
           <literal>Ndb_connected_host</literal> and
           <literal>Ndb_connected_port</literal> were renamed to

@@ -2110,6 +2226,167 @@
 
       <listitem>
         <para>
+          <literal>NDB Cluster</literal>: The
<option>--help</option>
+          output from <literal>NDB</literal> 
+          binaries did not include file-related options. (Bug #21994)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The node recovery algorithm
+          was missing a version check for tables in the
+          <literal>ALTER_TABLE_COMMITTED</literal> state (as opposed to
+          the <literal>TABLE_ADD_COMMITTED</literal> state, which has
+          the version check). This could cause inconsistent schemas
+          across nodes following node recovery. (Bug #21756)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The output for the
<option>--help</option>
+          option used with <literal>NDB</literal> executable programs
+          (<command>ndbd</command>, <command>ndb_mgm</command>,
+          <command>ndb_restore</command>,
<command>ndb_config</command>,
+          and so on) referred to the <filename>Ndb.cfg</filename>  file,
+          instead of <filename>my.cnf</filename>. (Bug #21585) 
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Partition distribution keys
+          were updated only for the primary and starting replicas during
+          node recovery. This could lead to node failure recovery for
+          clusters having an odd number of replicas. (Bug #21535)
+        </para>
+        
+        <para>
+          <emphasis role="bold">Note</emphasis>: We recommend values
+          for <literal>NumberOfReplicas</literal> that are even powers
+          of 2, for best results.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The
<command>ndb_mgm</command>
+          management client did not set the exit status on errors,
+          always returning 0 instead. (Bug #21530)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Cluster logs were not rotated
+          following the first rotation cycle. (Bug #21345)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Condition pushdown did not
+          work correctly with <literal>DATETIME</literal> columns. (Bug
+          #21056)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Under some circumstances,
+          local checkpointing would hang, keeping any unstarted nodes
+          from being started. (Bug #20895) 
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Using an invalid node ID with
+          the management client <literal>STOP</literal> command could
+          cause <command>ndb_mgm</command> to hang. (Bug #20575)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: In some cases where
+          <literal>SELECT COUNT(*)</literal> from an
+          <literal>NDB</literal> table should have yielded an error,
+          <literal>MAX_INT</literal> was returned instead. (Bug #19914)  
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Following the restart of an MGM
node,
+          the Cluster management client did not automatically reconnect.
+          (Bug #19873)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Error messages given when
+          trying to make online changes parameters such as
+          <literal>NoOfReplicas</literal> thast can only be changed via
+          a complete shutdown and restart of the cluster did not
+          indicate the true nature of the problem. (Bug #19787)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>:
<command>ndb_restore</command> did not always
+          make clear that it had recovered successfully from temporary
+          errors while restoring a cluster backup. (Bug #19651)
+        </para>
+      </listitem>
+
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: In rare situations with
+          resource shortages, a crash could result from insufficient
+          <literal>IndexScanOperations</literal>. (Bug #19198)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <command>ndb_mgm -e show |
+            head</command> would hang after displaying the first 10
+          lines of output. (Bug #19047)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The error returned by the
+          cluster when too many nodes were defined did not make clear
+          the nature of the problem. (Bug #19045)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: A problem with takeover during
+          a system restart caused ordered 
+          indexes to be rebuilt incorrectly. This also adversely
+          affected Cluster Replication. (Bug #15303)
+        </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)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal> (Disk Data):
           <command>mysqldump</command> did not back up tablespace or
           logfile group information for Disk Data tables correctly.

@@ -6685,14 +6962,6 @@
 
       <listitem>
         <para>
-          <literal>NDB Cluster</literal>: In rare situations with
-          resource shortages, a crash could result from insufficient
-          <literal>IndexScanOperations</literal>. (Bug #19198)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           <literal>InnoDB</literal>: A <literal>DELETE</literal>
           followed by an <literal>INSERT</literal> and then by an
           <literal>UPDATE</literal> on a partitioned