List:Commits« Previous MessageNext Message »
From:jon Date:November 6 2007 10:34pm
Subject:svn commit - mysqldoc@docsrva: r8562 - trunk/dynamic-docs/changelog
View as plain text  
Author: jstephens
Date: 2007-11-06 23:34:45 +0100 (Tue, 06 Nov 2007)
New Revision: 8562

Log:

More Cluster changelog entry cleanups



Modified:
   trunk/dynamic-docs/changelog/mysqld.xml


Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml	2007-11-06 20:37:15 UTC (rev 8561)
+++ trunk/dynamic-docs/changelog/mysqld.xml	2007-11-06 22:34:45 UTC (rev 8562)
Changed blocks: 123, Lines Added: 198, Lines Deleted: 184; 36905 bytes

@@ -79776,8 +79776,6 @@
 
   </logentry>
 
-<!--  END CLUSTER FIXUPS  -->
-
   <logentry entrytype="bug">
 
     <tags>

@@ -80177,7 +80175,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="diskdata"/>
       <manual type="cluster"/>
     </tags>
 

@@ -80192,9 +80190,9 @@
     <message>
 
       <para>
-        (Disk Data): When restarting a data node following the creation
-        of a large number (~200) of Disk Data objects, the cluster could
-        not assign a node ID to the restarting node.
+        When restarting a data node following the creation of a large
+        number (~200) of Disk Data objects, the cluster could not assign
+        a node ID to the restarting node.
       </para>
 
     </message>

@@ -81783,6 +81781,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="gcc"/>
     </tags>

@@ -81798,7 +81797,8 @@
     <message>
 
       <para>
-        Cluster failed to build with <command>gcc</command> 4.0.
+        <literal>NDB</literal> failed to build with
+        <command>gcc</command> 4.0.
       </para>
 
     </message>

@@ -82314,7 +82314,6 @@
     <tags>
       <highlight type="cluster"/>
       <manual type="cluster"/>
-      <manual type="cluster"/>
       <manual type="TRUNCATE"/>
       <manual type="DROP TABLE"/>
     </tags>

@@ -84283,6 +84282,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="clusterreplication"/>
       <manual type="cluster"/>
     </tags>
 

@@ -84426,7 +84426,7 @@
         The cluster created a crashed replica of a table having an
         ordered index &mdash; or when logging was not enabled, of a
         table having a table or unique index &mdash; leading to a crash
-        of the cluster following 8 successibe restarts.
+        of the cluster following 8 successive restarts.
       </para>
 
     </message>

@@ -84562,8 +84562,8 @@
 
       <para>
         When a schema was detected to be corrupt, <command>ndb</command>
-        neglected to close it, resulting in a <quote>file already
-        open</quote> error if the schema was opened again later.
+        neglected to close it, resulting in a <errortext>file already
+        open</errortext> error if the schema was opened again later.
         written.
       </para>
 

@@ -85715,7 +85715,6 @@
       <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="ndb_restore"/>
-      <manual type="s"/>
       <manual type="skip-table-check"/>
     </tags>
 

@@ -86136,8 +86135,7 @@
     <message>
 
       <para>
-        (Cluster APIs): A call to
-        <literal>CHECK_TIMEDOUT_RET()</literal> in
+        A call to <literal>CHECK_TIMEDOUT_RET()</literal> in
         <filename>mgmapi.cpp</filename> should have been a call to
         <literal>DBUG_CHECK_TIMEDOUT_RET()</literal>.
       </para>

@@ -86410,6 +86408,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
     </tags>
 

@@ -86565,7 +86564,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="diskdata"/>
       <manual type="cluster"/>
     </tags>
 

@@ -86580,8 +86579,8 @@
     <message>
 
       <para>
-        (Disk Data): Trying to create Disk Data tables when running the
-        cluster in diskless mode would crash the cluster's data nodes.
+        Trying to create Disk Data tables when running the cluster in
+        diskless mode caused cluster data nodes to crash.
       </para>
 
       <note>

@@ -87742,8 +87741,8 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
-      <highlight type="cluster"/>
     </tags>
 
     <bugs>

@@ -88334,13 +88333,11 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="mysql"/>
       <manual type="ndbd"/>
-      <manual type="root"/>
       <manual type="mysqld"/>
-      <manual type="cluster"/>
-      <highlight type="cluster"/>
     </tags>
 
     <bugs>

@@ -89003,6 +89000,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="ndbrequire"/>
       <manual type="cluster"/>
       <manual type="PGMAN"/>

@@ -89273,14 +89271,15 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="ODirect"/>
       <manual type="cluster"/>
       <manual type="O_DIRECT"/>
     </tags>
 
     <versions>
+      <version ver="5.1.15-ndb-6.1.11"/>
       <version ver="5.1.19-ndb-6.2.3"/>
-      <version ver="5.1.15-ndb-6.1.11"/>
       <version ver="5.1.19-ndb-6.3.0"/>
     </versions>
 

@@ -90450,6 +90449,7 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="my.cnf"/>
     </tags>

@@ -90461,10 +90461,10 @@
     <message>
 
       <para>
-        Added <literal>[mysql_cluster]</literal> section to
-        <filename>my.cnf</filename> file for configuration settings
-        specific to MySQL Cluster. <literal>ndb-connectstring</literal>
-        variable moved here.
+        Added support for a <literal>[mysql_cluster]</literal> section
+        to the <filename>my.cnf</filename> file for configuration
+        settings specific to MySQL Cluster. The
+        <literal>ndb-connectstring</literal> variable was moved here.
       </para>
 
     </message>

@@ -90617,7 +90617,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="clusterapi"/>
       <manual type="libndbclient.so"/>
       <manual type="cluster"/>
     </tags>

@@ -90627,8 +90627,8 @@
     </bugs>
 
     <versions>
+      <version ver="4.1.23"/>
       <version ver="5.0.36"/>
-      <version ver="4.1.23"/>
       <version ver="5.0.37"/>
       <version ver="5.1.16"/>
     </versions>

@@ -90636,8 +90636,7 @@
     <message>
 
       <para>
-        (Cluster APIs): <filename>libndbclient.so</filename> was not
-        versioned.
+        <filename>libndbclient.so</filename> was not versioned.
       </para>
 
     </message>

@@ -91582,11 +91581,10 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="ndb_mgmd"/>
       <manual type="config.ini"/>
-      <manual type="cluster"/>
-      <highlight type="cluster"/>
     </tags>
 
     <bugs>

@@ -91601,7 +91599,7 @@
     <message>
 
       <para>
-        Placing multiple <literal>[TCP DEFAULT]</literal> sections in
+        Placing multiple <literal>[tcp default]</literal> sections in
         the cluster&apos;s <filename>config.ini</filename> file crashed
         <command>ndb_mgmd</command>. (The process now exits gracefully
         in such cases, with an appropriate error message.)

@@ -92434,8 +92432,9 @@
     <message>
 
       <para>
-        Wrong error message displayed when cluster management server
-        closed port while <command>mysqld</command> was connecting.
+        The wrong error message was displayed when the cluster
+        management server port was closed while a
+        <command>mysqld</command> process was trying to connect.
       </para>
 
     </message>

@@ -93302,6 +93301,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="mysqldump"/>
       <manual type="BIT"/>
       <manual type="cluster"/>

@@ -93730,7 +93730,7 @@
 
       <para>
         Using <literal>ORDER BY
-        <replaceable>primary_key_column</replaceable> </literal> when
+        <replaceable>primary_key_column</replaceable></literal> when
         selecting from a table having the primary key on a
         <literal>VARCHAR</literal> column caused a forced shutdown of
         the cluster.

@@ -93982,10 +93982,9 @@
   <logentry entrytype="feature">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="clusterreplication"/>
       <manual type="cluster"/>
       <manual type="replication"/>
-      <manual type="cluster"/>
     </tags>
 
     <versions>

@@ -94520,9 +94519,9 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="mysqldump"/>
-      <manual type="cluster"/>
     </tags>
 
     <bugs>

@@ -94548,6 +94547,7 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="DROP INDEX"/>
       <manual type="CREATE INDEX"/>

@@ -94560,9 +94560,9 @@
     <message>
 
       <para>
-        Added support for the <literal>CREATE INDEX</literal> and
-        <literal>DROP INDEX</literal> statements to the <literal>NDB
-        Cluster</literal> storage engine.
+        The <literal>NDB</literal> storage engine now supports the
+        <literal>CREATE INDEX</literal> and <literal>DROP
+        INDEX</literal> statements.
       </para>
 
     </message>

@@ -94597,9 +94597,8 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
-      <manual type="cluster"/>
-      <highlight type="cluster"/>
     </tags>
 
     <bugs>

@@ -95027,11 +95026,12 @@
     <message>
 
       <para>
-        Row-based replication was not being set up correctly if a backup
-        was already in progress. For example, connecting a
+        Row-based replication was not set up correctly if a backup was
+        already in progress. For example, connecting a
         <command>mysqld</command> instance to a cluster which was being
         backed up would result in the message <errortext>NDB: skipping
-        setup table test.t1</errortext> being written to the error log.
+        setup table <replaceable>tbl_name</replaceable></errortext>
+        being written to the error log.
       </para>
 
     </message>

@@ -95282,7 +95282,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="clusterreplication"/>
       <manual type="replication"/>
       <manual type="cluster"/>
       <manual type="binlog-do-db"/>

@@ -95300,9 +95300,9 @@
     <message>
 
       <para>
-        (Replication): Using the <option>--binlog-do-db</option> option
-        caused problems with <literal>CREATE TABLE</literal> on the
-        cluster acting as the replication master.
+        Using the <option>--binlog-do-db</option> option caused problems
+        with <literal>CREATE TABLE</literal> on the cluster acting as
+        the replication master.
       </para>
 
     </message>

@@ -95389,6 +95389,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
     </tags>
 

@@ -96640,6 +96641,8 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="importantchange"/>
+      <highlight type="clusterreplication"/>
       <manual type="cluster"/>
       <manual type="replication"/>
     </tags>

@@ -96654,7 +96657,8 @@
         Replication between MySQL Clusters is now supported. It is now
         also possible to replicate between a MySQL Cluster and a
         non-cluster database. See
-        <xref linkend="mysql-cluster-replication"/>.
+        <xref linkend="mysql-cluster-replication"/>, for more
+        information.
       </para>
 
     </message>

@@ -97131,6 +97135,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="partitioning"/>
       <manual type="cluster"/>
       <manual type="CREATE TABLE"/>

@@ -97147,11 +97152,10 @@
     <message>
 
       <para>
-        <literal>NDB</literal>: Specifying the wrong nodegroup in a
-        <literal>CREATE TABLE</literal> using partitioning would lead to
-        the table name being locked after the <literal>CREATE
-        TABLE</literal> statement failed (that is, the table name could
-        not be re-used).
+        Specifying the wrong nodegroup in a <literal>CREATE
+        TABLE</literal> statement using partitioning would lead to the
+        table name being locked after the statement failed (that is, the
+        table name could not be re-used).
       </para>
 
     </message>

@@ -97176,8 +97180,8 @@
     <message>
 
       <para>
-        A memory allocation failure in the cluster Subscription Manager
-        could cause the cluster to crash.
+        A memory allocation failure in <literal>SUMA</literal> (the
+        cluster Subscription Manager) could cause the cluster to crash.
       </para>
 
     </message>

@@ -97350,7 +97354,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="clusterapi"/>
       <manual type="cluster"/>
     </tags>
 

@@ -97373,7 +97377,7 @@
       <para>
         As part of the fix for this bug, two new NDB API methods were
         added to the <literal>NdbDictionary::Object::Table</literal>
-        class. See the MySQL Cluster API documentation for details.
+        class. See <xref linkend="ndb-api"/>, for details.
       </para>
 
     </message>

@@ -97413,7 +97417,7 @@
   <logentry entrytype="feature">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="clusterreplication"/>
       <highlight type="incompatiblechange"/>
       <manual type="replication"/>
       <manual type="cluster"/>

@@ -97826,6 +97830,7 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="clusterreplication"/>
       <highlight type="incompatiblechange"/>
       <manual type="replication"/>
       <manual type="cluster"/>

@@ -97960,7 +97965,7 @@
     <message>
 
       <para>
-        Restarting a failed node could crash the cluster.
+        Restarting a failed node could sometimes crash the cluster.
       </para>
 
     </message>

@@ -98270,6 +98275,7 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
     </tags>
 

@@ -98316,9 +98322,9 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="ndb_mgm"/>
-      <manual type="cluster"/>
     </tags>
 
     <bugs>

@@ -98335,10 +98341,10 @@
     <message>
 
       <para>
-        <literal>NDB</literal>: A cluster shutdown following the crash
-        of a data node would fail to terminate the remaining node
-        processes, even though <command>ndb_mgm</command> showed the
-        shutdown request as having been completed.
+        A cluster shutdown following the crash of a data node failed to
+        terminate any remaining node processes, even though
+        <command>ndb_mgm</command> showed the shutdown request as having
+        been completed.
       </para>
 
     </message>

@@ -98348,7 +98354,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="clusterapi"/>
       <manual type="cluster"/>
       <manual type="transactions"/>
     </tags>

@@ -98364,10 +98370,10 @@
     <message>
 
       <para>
-        (NDB API): When using the
-        <literal>NdbTransaction::execute()</literal> method, a very long
-        timeout (greater than 5 minutes) could result if the last data
-        node being polled was disconnected from the cluster.
+        When using the <literal>NdbTransaction::execute()</literal>
+        method, a very long timeout (greater than 5 minutes) could
+        result if the last data node being polled was disconnected from
+        the cluster.
       </para>
 
     </message>

@@ -98670,7 +98676,7 @@
     <message>
 
       <para>
-        Cluster backups would fail when there were more than 2048 schema
+        Cluster backups failed when there were more than 2048 schema
         objects in the cluster.
       </para>
 

@@ -98772,10 +98778,10 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="show"/>
       <manual type="ndb_mgm"/>
-      <highlight type="cluster"/>
     </tags>
 
     <bugs>

@@ -98789,7 +98795,7 @@
     <message>
 
       <para>
-        The <command>ndb_mgm</command> client&apos;
+        The <command>ndb_mgm</command> client&apos;s
         <literal>SHOW</literal> command displayed incorrect output after
         master data node failure.
       </para>

@@ -99613,6 +99619,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
     </tags>
 

@@ -100541,10 +100548,10 @@
     </bugs>
 
     <versions>
+      <version ver="4.1.22"/>
+      <version ver="5.0.30"/>
       <version ver="5.0.33"/>
       <version ver="5.1.12"/>
-      <version ver="5.0.30"/>
-      <version ver="4.1.22"/>
     </versions>
 
     <message>

@@ -100912,6 +100919,7 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="OFFLINE"/>
       <manual type="cluster"/>
       <manual type="ADD COLUMN"/>

@@ -101149,7 +101157,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="diskdata"/>
       <manual type="cluster"/>
       <manual type="INITIAL_SIZE"/>
     </tags>

@@ -101165,9 +101173,8 @@
     <message>
 
       <para>
-        (Disk Data): Use of a tablespace whose
-        <literal>INITIAL_SIZE</literal> was greater than 1 GB could
-        cause the cluster to crash.
+        Use of a tablespace whose <literal>INITIAL_SIZE</literal> was
+        greater than 1 GB could cause the cluster to crash.
       </para>
 
     </message>

@@ -101556,6 +101563,7 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="transactions"/>
       <manual type="DUMP"/>

@@ -102241,8 +102249,9 @@
 
       <para>
         It is now possible to perform a partial start of a cluster. That
-        is, it is now possible to bring up the cluster without running
-        ndbd &ddash;initial on all configured data nodes first.
+        is, it is now possible to bring up the cluster without first
+        running <command>ndbd <option>--initial</option></command> on
+        all configured data nodes.
       </para>
 
     </message>

@@ -102252,7 +102261,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="clusterreplication"/>
       <manual type="cluster"/>
       <manual type="replication"/>
     </tags>

@@ -103505,15 +103514,15 @@
     </bugs>
 
     <versions>
+      <version ver="5.0.34"/>
+      <version ver="5.0.37"/>
       <version ver="5.1.15"/>
-      <version ver="5.0.37"/>
-      <version ver="5.0.34"/>
     </versions>
 
     <message>
 
       <para>
-        Hosts in clusters with a large number of nodes could experience
+        Hosts in clusters with large numbers of nodes could experience
         excessive CPU usage while obtaining configuration data.
       </para>
 

@@ -103524,8 +103533,8 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
-      <manual type="cluster"/>
       <manual type="TRUNCATE"/>
       <manual type="DROP TABLE"/>
     </tags>

@@ -104181,6 +104190,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
     </tags>
 

@@ -104484,6 +104494,7 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="VARCHAR"/>
       <manual type="CHAR"/>

@@ -104500,11 +104511,11 @@
         are now variable-sized; that is, they now only allocate as much
         space as required to store the data. Previously, a
         <literal>VARCHAR(<replaceable>n</replaceable>)</literal> column
-        allocated n+2 bytes (aligned to 4 bytes), regardless if the
-        actual inserted value required that much space. (In other words,
-        a <literal>VARCHAR</literal> column always required the same,
-        fixed, amount of storage as a <literal>CHAR</literal> column of
-        the same size.)
+        allocated n+2 bytes (aligned to 4 bytes), regardless of whether
+        the actual inserted value required that much space. (In other
+        words, a <literal>VARCHAR</literal> column always required the
+        same, fixed, amount of storage as a <literal>CHAR</literal>
+        column of the same size.)
       </para>
 
     </message>

@@ -104514,6 +104525,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
     </tags>
 

@@ -104832,6 +104844,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
     </tags>
 

@@ -104847,9 +104860,9 @@
 
       <para>
         After putting the cluster in single user mode from one MySQL
-        server, trying to drop an NDB table from a second MySQL server
-        also connected to the cluster would cause the second MySQL
-        server to hang.
+        server, trying to drop an <literal>NDB</literal> table from a
+        second MySQL server connected to the same cluster would cause
+        the second MySQL server to hang.
       </para>
 
     </message>

@@ -105156,7 +105169,7 @@
 
   </logentry>
 
-  <logentry entrytype="feature">
+  <logentry entrytype="bug">
 
     <tags>
       <highlight type="cluster"/>

@@ -105243,6 +105256,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="ALTER TABLE"/>
     </tags>

@@ -105260,8 +105274,8 @@
 
       <para>
         The temporary tables created by an <literal>ALTER
-        TABLE</literal> on a cluster table were visible to all MySQL
-        servers.
+        TABLE</literal> on an <literal>NDB</literal> table were visible
+        to all SQL nodes in the cluster.
       </para>
 
     </message>

@@ -105959,7 +105973,8 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="diskdata"/>
+      <highlight type="clusterreplication"/>
       <manual type="replication"/>
       <manual type="cluster"/>
     </tags>

@@ -105975,8 +105990,8 @@
     <message>
 
       <para>
-        (Cluster Replication / Disk Data): An issue with replication of
-        Disk Data tables could in some cases lead to node failure.
+        An issue with replication of Disk Data tables could in some
+        cases lead to node failure.
       </para>
 
     </message>

@@ -106063,6 +106078,7 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
     </tags>
 

@@ -106075,8 +106091,8 @@
       <para>
         A single cluster can now support up to 255 API nodes, including
         MySQL servers acting as SQL nodes. See
-        <link linkend="mysql-cluster-limitations-exclusive-to-cluster">Issues
-        exclusive to MySQL Cluster</link> for more information.
+        <xref linkend="mysql-cluster-limitations-exclusive-to-cluster"/>,
+        for more information.
       </para>
 
     </message>

@@ -106526,9 +106542,9 @@
     </bugs>
 
     <versions>
+      <version ver="5.0.30"/>
       <version ver="5.0.33"/>
       <version ver="5.1.12"/>
-      <version ver="5.0.30"/>
     </versions>
 
     <message>

@@ -106681,7 +106697,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="diskdata"/>
       <manual type="cluster"/>
     </tags>
 

@@ -106696,9 +106712,9 @@
     <message>
 
       <para>
-        (Disk Data): Concurrent table schema operations and operations
-        on log files groups, tablespaces, data files, or undofiles could
-        lead to Cluster node failures.
+        Concurrent table schema operations and operations on log file
+        groups, tablespaces, data files, or undo files could lead to
+        data node failures.
       </para>
 
     </message>

@@ -106972,10 +106988,9 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="mysqld"/>
-      <manual type="cluster"/>
-      <highlight type="cluster"/>
     </tags>
 
     <bugs>

@@ -107086,7 +107101,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="diskdata"/>
       <manual type="cluster"/>
     </tags>
 

@@ -107101,9 +107116,9 @@
     <message>
 
       <para>
-        (Disk Data): When restoring from backup a cluster containing any
-        Disk Data tables with hidden primary keys, a node failure
-        resulted which could lead to a crash of the cluster.
+        When restoring from backup a cluster containing any Disk Data
+        tables with hidden primary keys, a node failure resulted which
+        could lead to a crash of the cluster.
       </para>
 
     </message>

@@ -107225,7 +107240,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="diskdata"/>
       <manual type="cluster"/>
     </tags>
 

@@ -107240,8 +107255,8 @@
     <message>
 
       <para>
-        (Disk Data): Extents that should have been available for re-use
-        following a DROP TABLE operation were not actually made
+        Extents that should have been available for re-use following a
+        <literal>DROP TABLE</literal> operation were not actually made
         available again until after the cluster performed a local
         checkpoint.
       </para>

@@ -107375,7 +107390,7 @@
       <para>
         A forced cluster shutdown occurred when the management daemon
         was restarted with a changed <filename>config.ini</filename>
-        file that added an API/SQL node.
+        file that added an API or SQL node.
       </para>
 
     </message>

@@ -108393,7 +108408,6 @@
     <tags>
       <highlight type="cluster"/>
       <manual type="cluster"/>
-      <manual type="cluster"/>
     </tags>
 
     <bugs>

@@ -108500,7 +108514,7 @@
     <tags>
       <highlight type="cluster"/>
       <manual type="cluster"/>
-      <manual type="mgm"/>
+      <manual type="ndb_mgm"/>
     </tags>
 
     <bugs>

@@ -108516,8 +108530,8 @@
     <message>
 
       <para>
-        The <command>mgm</command> client command <literal>ALL
-        CLUSTERLOG STATISTICS=15;</literal> had no effect.
+        The <command>ndb_mgm</command> client command <literal>ALL
+        CLUSTERLOG STATISTICS=15</literal> had no effect.
       </para>
 
     </message>

@@ -108661,7 +108675,7 @@
 
       <para>
         Connections between data nodes and management nodes were not
-        being closed following shutdown of <command>ndb_mgmd</command>.
+        closed following shutdown of <command>ndb_mgmd</command>.
       </para>
 
     </message>

@@ -108852,9 +108866,10 @@
 
   </logentry>
 
-  <logentry entrytype="bug">
+  <logentry entrytype="feature">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="mysqld"/>
     </tags>

@@ -108871,9 +108886,9 @@
     <message>
 
       <para>
-        Provide more informative error messages in clustered setting
-        when a query is issued against a table that has been modified by
-        another <command>mysqld</command> server.
+        More informative error messages are provided when a query is
+        issued against an <literal>NDB</literal> table that has been
+        modified by another <command>mysqld</command> server.
       </para>
 
     </message>

@@ -109285,8 +109300,8 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
-      <highlight type="cluster"/>
     </tags>
 
     <bugs>

@@ -109331,8 +109346,8 @@
 
       <para>
         Users who had the <literal>SHOW VIEW</literal> privilege for a
-        view and privileges on one of the view's base table could not
-        see records in <literal>INFORMATION_SCHEMA</literal> tables
+        view and privileges on one of the view&apos;s base tables could
+        not see records in <literal>INFORMATION_SCHEMA</literal> tables
         relating to the base table.
       </para>
 

@@ -109651,6 +109666,7 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="ndbd_redo_log_reader"/>
     </tags>

@@ -109816,7 +109832,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="clusterreplication"/>
       <manual type="replication"/>
       <manual type="cluster"/>
     </tags>

@@ -109832,8 +109848,8 @@
     <message>
 
       <para>
-        (Replication): Following a restart of the master cluster, the
-        latest GCI was set to 0 upon reconnection to the slave.
+        Following a restart of the master cluster, the latest GCI was
+        set to 0 upon reconnection to the slave.
       </para>
 
     </message>

@@ -109989,9 +110005,9 @@
 
       <para>
         A new <option>--nowait-nodes</option> startup option for
-        <command>ndbd</command> makes it possible to <quote>skip</quote>
-        specific nodes without waiting for them to start when starting
-        the cluster. See
+        <command>ndbd</command> makes it possible to skip specified
+        nodes without waiting for them to start when starting the
+        cluster. See
         <xref linkend="mysql-cluster-ndbd-command-options"/>.
       </para>
 

@@ -110161,6 +110177,7 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="clusterreplication"/>
       <manual type="Ndb_conflict_fn_old"/>
       <manual type="replication"/>
       <manual type="cluster"/>

@@ -110397,10 +110414,10 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="clusterreplication"/>
       <manual type="cluster"/>
       <manual type="replication"/>
       <manual type="binlog"/>
-      <highlight type="clusterreplication"/>
     </tags>
 
     <bugs>

@@ -110809,7 +110826,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="diskdata"/>
       <manual type="CREATE LOGFILE GROUP"/>
       <manual type="cluster"/>
     </tags>

@@ -110825,9 +110842,9 @@
     <message>
 
       <para>
-        (Disk Data): Issuing a <literal>CREATE LOGFILE GROUP</literal>
-        statement during the drop of an <literal>NDB</literal> table
-        would cause database corruption.
+        Issuing a <literal>CREATE LOGFILE GROUP</literal> statement
+        during the drop of an <literal>NDB</literal> table would cause
+        database corruption.
       </para>
 
     </message>

@@ -111050,8 +111067,8 @@
       <para>
         Unused open handlers for tables in which the metadata had
         changed were not properly closed. This could result in stale
-        results from Cluster tables following an <literal>ALTER
-        TABLE</literal>.
+        results from <literal>NDB</literal> tables following an
+        <literal>ALTER TABLE</literal> statement.
       </para>
 
     </message>

@@ -112503,9 +112520,9 @@
     </bugs>
 
     <versions>
-      <version ver="5.1.12"/>
       <version ver="4.1.21"/>
       <version ver="5.0.23"/>
+      <version ver="5.1.12"/>
     </versions>
 
     <message>

@@ -113460,6 +113477,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
     </tags>
 

@@ -114076,8 +114094,8 @@
 
       <para>
         An excessive number of <literal>ALTER TABLE</literal> operations
-        could cause the cluster to fail with NDB error code 773
-        (<errortext>Out of string memory, please modify
+        could cause the cluster to fail with <literal>NDB</literal>
+        error code 773 (<errortext>Out of string memory, please modify
         StringMemory</errortext>).
       </para>
 

@@ -115732,7 +115750,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="diskdata"/>
       <manual type="cluster"/>
     </tags>
 

@@ -115747,9 +115765,9 @@
     <message>
 
       <para>
-        (Disk Data): An issue with disk allocation could sometimes cause
-        a forced shutdown of the cluster when running a mix of memory
-        and Disk Data tables.
+        An issue with disk allocation could sometimes cause a forced
+        shutdown of the cluster when running a mix of memory and Disk
+        Data tables.
       </para>
 
     </message>

@@ -115940,9 +115958,9 @@
     </bugs>
 
     <versions>
-      <version ver="5.1.12"/>
       <version ver="4.1.21"/>
       <version ver="5.0.24"/>
+      <version ver="5.1.12"/>
     </versions>
 
     <message>

@@ -116020,16 +116038,16 @@
     </bugs>
 
     <versions>
-      <version ver="5.1.12"/>
       <version ver="4.1.21"/>
       <version ver="5.0.23"/>
+      <version ver="5.1.12"/>
     </versions>
 
     <message>
 
       <para>
-        The cluster's data nodes would fail while trying to load data
-        when <literal>NoOfFrangmentLogFiles</literal> was equal to 1.
+        The cluster's data nodes failed while trying to load data when
+        <literal>NoOfFrangmentLogFiles</literal> was set equal to 1.
       </para>
 
     </message>

@@ -117223,9 +117241,8 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
-      <manual type="cluster"/>
-      <highlight type="cluster"/>
     </tags>
 
     <bugs>

@@ -117795,15 +117812,15 @@
     </bugs>
 
     <versions>
+      <version ver="5.0.30"/>
       <version ver="5.1.15"/>
-      <version ver="5.0.30"/>
     </versions>
 
     <message>
 
       <para>
-        A potential memory leak in the <literal>NDB</literal> storage
-        engine's handling of file operations was uncovered.
+        The <literal>NDB</literal> storage engine could leak memory
+        during file operations.
       </para>
 
     </message>

@@ -117864,10 +117881,9 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="ndb_mgm"/>
-      <manual type="cluster"/>
-      <highlight type="cluster"/>
     </tags>
 
     <bugs>

@@ -118165,7 +118181,6 @@
   <logentry entrytype="feature">
 
     <tags>
-      <manual type="cluster"/>
       <manual type="InnoDB"/>
       <manual type="OPTIMIZE TABLE"/>
       <manual type="ANALYZE TABLE"/>

@@ -118564,12 +118579,11 @@
     <message>
 
       <para>
-        When a cluster node suffered a <quote>hard</quote> failure (such
-        as a power failure or loss of a network connection) TCP sockets
-        to the <quote>vanished</quote> node were maintained
-        indefinitely. Now socket-based transporters check for a response
-        and terminate the socket if there is no activity on the socket
-        after 2 hours.
+        When a cluster data node suffered a <quote>hard</quote> failure
+        (such as a power failure or loss of a network connection) TCP
+        sockets to the missing node were maintained indefinitely. Now
+        socket-based transporters check for a response and terminate the
+        socket if there is no activity on the socket after 2 hours.
       </para>
 
     </message>

@@ -118924,7 +118938,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
+      <highlight type="diskdata"/>
       <manual type="cluster"/>
     </tags>
 

@@ -118939,11 +118953,10 @@
     <message>
 
       <para>
-        (Disk Data): It was possible to execute a statement for creating
-        a Disk Data table that referred to a nonexistent tablespace, in
-        which case the table was an in-memory <literal>NDB</literal>
-        table. Such a statement instead now fails with an appropriate
-        error message.
+        It was possible to execute a statement for creating a Disk Data
+        table that referred to a nonexistent tablespace, in which case
+        the table was an in-memory <literal>NDB</literal> table. Such a
+        statement instead now fails with an appropriate error message.
       </para>
 
     </message>

@@ -118983,9 +118996,9 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="ndb_select_count"/>
-      <highlight type="clusterapi"/>
     </tags>
 
     <bugs>

@@ -118999,8 +119012,8 @@
     <message>
 
       <para>
-        Calling <literal>ndb_select_count()</literal> crashed the
-        cluster when running on Red Hat Enterprise 4/64-bit/Opteron.
+        Running <command>ndb_select_count</command> crashed the cluster
+        when running on Red Hat Enterprise 4/64-bit/Opteron.
       </para>
 
     </message>

@@ -119090,7 +119103,6 @@
   <logentry entrytype="bug">
 
     <tags>
-      <manual type="cluster"/>
       <manual type="VARCHAR"/>
       <manual type="CHAR"/>
       <manual type="InnoDB"/>

@@ -119365,6 +119377,7 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
       <manual type="MaxNoOfTables"/>
       <manual type="cluster"/>
     </tags>

@@ -119380,16 +119393,17 @@
     <message>
 
       <para>
-        <literal>NDB</literal>: Trying to use a greater number of tables
-        then specified by the value of <literal>MaxNoOfTables</literal>
-        caused table corruption such that data nodes could not be
-        restarted.
+        Trying to use a greater number of tables than specified by the
+        value of <literal>MaxNoOfTables</literal> caused table
+        corruption such that data nodes could not be restarted.
       </para>
 
     </message>
 
   </logentry>
 
+<!--  END CLUSTER FIXUPS  -->
+
   <logentry entrytype="bug">
 
     <tags>


Thread
svn commit - mysqldoc@docsrva: r8562 - trunk/dynamic-docs/changelogjon6 Nov