List:Commits« Previous MessageNext Message »
From:jon Date:November 2 2006 4:01pm
Subject:svn commit - mysqldoc@docsrva: r3831 - trunk/refman-5.0
View as plain text  
Author: jstephens
Date: 2006-11-02 17:01:34 +0100 (Thu, 02 Nov 2006)
New Revision: 3831

Log:

Moved recent Cluster bugfixes tagged 5.0.29 to 5.0.30-es release notes.

Removed releasenotes-5.0.29-cs section.

Updated renamed-nodes.txt just in case.

Reformat.



Modified:
   trunk/refman-5.0/releasenotes-cs-5.0.xml
   trunk/refman-5.0/releasenotes-es-5.0.xml
   trunk/refman-5.0/renamed-nodes.txt


Modified: trunk/refman-5.0/releasenotes-cs-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-cs-5.0.xml	2006-11-02 15:29:21 UTC (rev 3830)
+++ trunk/refman-5.0/releasenotes-cs-5.0.xml	2006-11-02 16:01:34 UTC (rev 3831)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 336; 11307 bytes

@@ -26,342 +26,6 @@
     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> (NDB API): Inacivity timeouts
-          for scans were not correctly handled. (Bug #23107)
-        </para>
-      </listitem>
-      
-      <listitem>
-        <para>
-          <literal>NDB Cluster</literal> (NDB API): Attempting to read a
-          nonexistent tuple using <literal>Commit</literal> mode for
-          <literal>NdbTransaction::execute()</literal> caused node
-          failures. (Bug #22672)
-        </para>
-      </listitem>
-      
-      <listitem>
-        <para>
-          <literal>NDB Cluster</literal> (NDB API): Scans closed before
-          being executed were still placed in the send queue. (Bug
-          #21941)
-        </para>
-      </listitem>
-      
-      <listitem>
-        <para>
-          <literal>NDB Cluster</literal> (NDB API): The
-          <literal>NdbOperation::getBlobHandle()</literal> method, when
-          called with the name of a nonexistent column, caused a
-          segmentation fault. (Bug #21036)
-        </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_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> (NDB 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 a
-          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.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2006-11-02 15:29:21 UTC (rev 3830)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2006-11-02 16:01:34 UTC (rev 3831)
Changed blocks: 1, Lines Added: 325, Lines Deleted: 0; 11248 bytes

@@ -41,13 +41,338 @@
     </para>
 
     <para>
+      Functionality added or changed:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <remark role="cluster-tagged-5.0.29-begin"/>
+
+        <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>
+
+        <remark role="cluster-tagged-5.0.29-end"/>
+      </listitem>
+
+    </itemizedlist>
+
+    <para>
       Bugs fixed:
     </para>
 
     <itemizedlist>
 
       <listitem>
+        <remark role="cluster-tagged-5.0.29-begin"/>
+
         <para>
+          <literal>NDB Cluster</literal> (NDB API): Inacivity timeouts
+          for scans were not correctly handled. (Bug #23107)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (NDB API): Attempting to read a
+          nonexistent tuple using <literal>Commit</literal> mode for
+          <literal>NdbTransaction::execute()</literal> caused node
+          failures. (Bug #22672)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (NDB API): Scans closed before
+          being executed were still placed in the send queue. (Bug
+          #21941)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (NDB API): The
+          <literal>NdbOperation::getBlobHandle()</literal> method, when
+          called with the name of a nonexistent column, caused a
+          segmentation fault. (Bug #21036)
+        </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_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> (NDB 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 a
+          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>
+
+        <remark role="cluster-tagged-5.0.29-end"/>
+      </listitem>
+
+      <listitem>
+        <para>
           The optimizer failed to use equality propagation for
           <literal>BETWEEN</literal> and <literal>IN</literal>
           predicates with string arguments. (Bug #22753)


Modified: trunk/refman-5.0/renamed-nodes.txt
===================================================================
--- trunk/refman-5.0/renamed-nodes.txt	2006-11-02 15:29:21 UTC (rev 3830)
+++ trunk/refman-5.0/renamed-nodes.txt	2006-11-02 16:01:34 UTC (rev 3831)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 0; 477 bytes

@@ -601,3 +601,5 @@
 cj-faq connector-j-usagenotes-troubleshooting
 cj-reporting-bugs connector-j-support-bug-report
 innodb-implicit-command-or-rollback innodb-implicit-commit
+
+releasenotes-cs-5-0-29 releasenotes-es-5-0-30


Thread
svn commit - mysqldoc@docsrva: r3831 - trunk/refman-5.0jon2 Nov