From: jon
Date: October 23 2007 12:36pm
Subject: svn commit - mysqldoc@docsrva: r8253 - trunk/dynamic-docs/changelog
List-Archive: http://lists.mysql.com/commits/36131
Message-Id: <200710231236.l9NCaKUU011233@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2007-10-23 14:36:20 +0200 (Tue, 23 Oct 2007)
New Revision: 8253

Log:

Cleaned up some old Cluster bugfix changelog entries (formatting 
inconsistent, etc.)



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


Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml	2007-10-23 12:20:20 UTC (rev 8252)
+++ trunk/dynamic-docs/changelog/mysqld.xml	2007-10-23 12:36:20 UTC (rev 8253)
Changed blocks: 12, Lines Added: 114, Lines Deleted: 56; 6373 bytes

@@ -12322,12 +12322,16 @@
 
     <message>
 
-      <para>
-        MySQL Cluster: <command>mysqld</command> processes would not
-        reconnect to cluster following restart of
-        <literal>ndb_mgmd</literal>.
-      </para>
+      <formalpara>
 
+        <title>MySQL Cluster</title>
+        <para>
+          <command>mysqld</command> processes did not reconnect to the
+          cluster following a restart of <command>ndb_mgmd</command>.
+        </para>
+
+      </formalpara>
+
     </message>
 
   </logentry>

@@ -12382,11 +12386,16 @@
 
     <message>
 
-      <para>
-        MySQL Cluster: A delete performed as part of a transaction
-        caused an erroneous result.
-      </para>
+      <formalpara>
 
+        <title>MySQL Cluster</title>
+        <para>
+          A <literal>DELETE</literal> performed as part of a transaction
+          caused an erroneous result.
+        </para>
+
+      </formalpara>
+
     </message>
 
   </logentry>

@@ -14935,11 +14944,16 @@
 
     <message>
 
-      <para>
-        MySQL Cluster: Setting TransactionInactiveTimeout= 0 did not
-        result in an infinite timeout.
-      </para>
+      <formalpara>
 
+        <title>MySQL Cluster</title>
+        <para>
+          Setting <literal>TransactionInactiveTimeout = 0</literal> did
+          not result in an infinite timeout.
+        </para>
+
+      </formalpara>
+
     </message>
 
   </logentry>

@@ -16961,11 +16975,15 @@
 
     <message>
 
-      <para>
-        MySQL Cluster: Fixed problem whereby data nodes would fail to
-        restart on 64-bit Solaris
-      </para>
+      <formalpara>
 
+        <title>MySQL Cluster</title>
+        <para>
+          Data nodes failed to restart on 64-bit Solaris
+        </para>
+
+      </formalpara>
+
     </message>
 
   </logentry>

@@ -26506,12 +26524,17 @@
 
     <message>
 
-      <para>
-        MySQL Cluster: When trying to open a table that could not be
-        discovered or unpacked, cluster would return error codes which
-        the MySQL server falsely interpreted as operating system errors.
-      </para>
+      <formalpara>
 
+        <title>MySQL Cluster</title>
+        <para>
+          When trying to open a table that could not be discovered or
+          unpacked, the cluster would return error codes which the MySQL
+          server falsely interpreted as operating system errors.
+        </para>
+
+      </formalpara>
+
     </message>
 
   </logentry>

@@ -62864,11 +62887,16 @@
 
     <message>
 
-      <para>
-        MySQL Cluster: Cluster would time out and crash after first
-        query on 64-bit Solaris 9.
-      </para>
+      <formalpara>
 
+        <title>MySQL Cluster</title>
+        <para>
+          The cluster would time out and crash after first query on
+          64-bit Solaris 9.
+        </para>
+
+      </formalpara>
+
     </message>
 
   </logentry>

@@ -72718,13 +72746,19 @@
 
     <message>
 
-      <para>
-        MySQL Cluster: Not allowing sufficient parallelism in cluster
-        configuration (for example, <literal>NoOfTransactions</literal>
-        too small) caused <literal>ndb_restore</literal> to fail without
-        providing any error messages.
-      </para>
+      <formalpara>
 
+        <title>MySQL Cluster</title>
+        <para>
+          Not allowing sufficient parallelism in the cluster&apos;s
+          configuration (for example, by setting
+          <literal>NoOfTransactions</literal> too small) caused
+          <command>ndb_restore</command> to fail without providing any
+          error messages.
+        </para>
+
+      </formalpara>
+
     </message>
 
   </logentry>

@@ -75297,12 +75331,17 @@
 
     <message>
 
-      <para>
-        MySQL Cluster: Insert records were incorrectly applied by
-        <literal>ndb_restore</literal>, thus making restoration from
-        backup inconsistent if the binlog contained inserts.
-      </para>
+      <formalpara>
 
+        <title>MySQL Cluster</title>
+        <para>
+          Insert records were incorrectly applied by
+          <command>ndb_restore</command>, thus making restoration from
+          backup inconsistent if the binlog contained inserts.
+        </para>
+
+      </formalpara>
+
     </message>
 
   </logentry>

@@ -81677,11 +81716,16 @@
 
     <message>
 
-      <para>
-        MySQL Cluster: When using dynamically allocated ports on Linux,
-        cluster would hang on initial startup.
-      </para>
+      <formalpara>
 
+        <title>MySQL Cluster</title>
+        <para>
+          When using dynamically allocated ports on Linux, the cluster
+          would hang on initial startup.
+        </para>
+
+      </formalpara>
+
     </message>
 
   </logentry>

@@ -98215,12 +98259,17 @@
 
     <message>
 
-      <para>
-        MySQL Cluster: <literal>ndb_mgm</literal> client
-        <literal>show</literal> command displayed incorrect output after
-        master data node failure.
-      </para>
+      <formalpara>
 
+        <title>MySQL Cluster</title>
+        <para>
+          The <literal>ndb_mgm</literal> client <literal>SHOW</literal>
+          command displayed incorrect output after master data node
+          failure.
+        </para>
+
+      </formalpara>
+
     </message>
 
   </logentry>

@@ -108437,12 +108486,17 @@
 
     <message>
 
-      <para>
-        MySQL Cluster: Connections between data nodes and management
-        nodes were not being closed following shutdown of
-        <literal>ndb_mgmd</literal>.
-      </para>
+      <formalpara>
 
+        <title>MySQL Cluster</title>
+        <para>
+          Connections between data nodes and management nodes were not
+          being closed following shutdown of
+          <command>ndb_mgmd</command>.
+        </para>
+
+      </formalpara>
+
     </message>
 
   </logentry>

@@ -119107,12 +119161,16 @@
 
     <message>
 
-      <para>
-        MySQL Cluster: Calling <literal>ndb_select_count()</literal>
-        crashed the cluster when running on Red Hat Enterprise
-        4/64-bit/Opteron.
-      </para>
+      <formalpara>
 
+        <title>MySQL Cluster</title>
+        <para>
+          Calling <literal>ndb_select_count()</literal> crashed the
+          cluster when running on Red Hat Enterprise 4/64-bit/Opteron.
+        </para>
+
+      </formalpara>
+
     </message>
 
   </logentry>