Author: jstephens
Date: 2007-03-09 03:05:40 +0100 (Fri, 09 Mar 2007)
New Revision: 5260
Log:
Documenting Cluster bugfixes.
Cluster/General: Bug #26663, Bug #26720, Bug #26739, Bug #26741
Disk Data: Bug #26487, Bug #26514
Modified:
branches/telcos/refman-5.1/news-5.1.xml
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.1/news-5.1.xml
Modified: branches/telcos/refman-5.1/news-5.1.xml
===================================================================
--- branches/telcos/refman-5.1/news-5.1.xml 2007-03-08 22:16:17 UTC (rev 5259)
+++ branches/telcos/refman-5.1/news-5.1.xml 2007-03-09 02:05:40 UTC (rev 5260)
Changed blocks: 1, Lines Added: 169, Lines Deleted: 0; 6214 bytes
@@ -35,6 +35,175 @@
<filename>TEMPLATE.news.xml</filename> template in the
<filename>refman-common</filename> directory.
</remark>
+
+ <section id="news-5-1-15-ndb-6-1-4">
+
+ <title>Changes in release MySQL 5.1.15/NDB-6.1.4-beta (Not yet
+ released)</title>
+
+ <para role="release-level">
+ This is a new Beta development release, fixing recently discovered
+ bugs and incorporating improvements made since the previous
+ ¤t-series; release.
+ </para>
+
+ <para>
+ Like all releases for MySQL ¤t-series;, this is a
+ source-only release which you must compile and install using the
+ instructions found in <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>.
+ <remark role="TODO">
+ [js] Update/uncomment following when release is available:
+ </remark>
+ <!--You can download the
+ source code archive for this release from the MySQL FTP site at
+ <ulink url="ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.15-ndb-6.1.3"/>.
+ The file
+ <filename>mysqlcom-5.1.15-ndb-6.1.3-telco.tar.gz</filename> in
+ this directory contains the complete source archive.-->
+ </para>
+
+ <para role="release-non-production">
+ <emphasis role="bold">NOTE</emphasis>: Although MySQL has worked
+ very hard to ensure a high level of quality, protect your data by
+ making a backup as you would for any software beta release. Please
+ refer to our bug database at <ulink url="http://bugs.mysql.com/"/>
+ for more details about the individual bugs fixed in this version.
+ </para>
+
+ <para>
+ This is the fifth MySQL ¤t-series; Beta release. It
+ incorporates all bugfixes and feature changes made in MySQL
+ 5.1.14/NDB-6.1.0, MySQL 5.1.15/NDB-6.1.1, MySQL 5.1.15/NDB-6.1.2,
+ and MySQL 5.1.15/NDB-6.1.3. This version also incorporates all
+ bugfixes and feature changes which were added in the mainline
+ MySQL 5.1 releases up to and including 5.1.15; information about
+ these can be found in <xref linkend="news-5-1-15"/>.
+ </para>
+
+ <remark role="TODO">
+ [js] Update and uncomment following when release is available and
+ devs have provided appropriate info.
+ </remark>
+
+<!--
+ <important>
+ <formalpara>
+ <title>Upgrading to MySQL 5.1.15/NDB-6.1.3 from a previous release</title>
+
+
+
+ <para>
+ This release is not binary compatible with releases previous
+ to MySQL 5.1.15/NDB-6.1.2. This means that:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ You cannot perform an online upgrade to this release
+ from MySQL 5.1.14/NDB-6.1.0, MySQL 5.1.15/NDB-6.1.1, or
+ any of the mainline MySQL 5.1 releases. When upgrading
+ from one of these versions, you must shut down the
+ cluster, replace all binaries, then restart the cluster.
+ </para>
+
+ <para>
+ However, you <emphasis>can</emphasis> perform an online
+ upgrade of a Cluster running MySQL 5.1.15/NDB-6.1.2 to
+ MySQL 5.1.15/NDB-6.1.13, using the rolling upgrade
+ procedure described in
+ <xref linkend="mysql-cluster-rolling-restart"/>. You
+ should replace all binaries for all data nodes,
+ management nodes, and SQL nodes as part of this process.
+ When upgrading the data nodes, you will need to restart
+ each data with the <option>&ddash;initial</option> option.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ You must recompile all NDB API and MGM API applications
+ used with a previous version of MySQL Cluster, including
+ those compiled against MySQL 5.1.15/NDB-6.1.13.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+ </formalpara>
+ </important>
+-->
+
+ <remark role="TODO">
+ [js] Uncomment following when there are functional changes to
+ report.
+ </remark>
+
+<!--
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+
+ </para>
+ </listitem>
+
+
+ </itemizedlist>
+-->
+
+ <para>
+ This release fixes the following bugs:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Using only the <option>--print_data</option> option (and no other options) with
+ <command>ndb_restore</command> caused
+ <command>ndb_restore</command> to fail. (Bug# 26741)
+ </para>
+
+ <para>
+ This bug was introduced by the fix for Bug #14612.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An inadvertent use of unaligned data caused
+ <command>ndb_restore</command> to fail on some 64-bit
+ platforms, including Sparc and Itanium-2. (Bug #26739)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An infinite loop in an internal logging function could cause
+ trace logs to fill up with <errortext>Unknown Signal
+ type</errortext> error messages and thus grow to
+ unreasonable sizes. (Bug #26720)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Assigning a node ID greater than 63 to an SQL node caused an
+ out of bounds error in <command>mysqld</command>. It should
+ now be possible to assign to SQL nodes node IDs up to 255.
+ (Bug # 26663)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
<section id="news-5-1-15-ndb-6-1-3">
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-08 22:16:17 UTC (rev 5259)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-09 02:05:40 UTC (rev 5260)
Changed blocks: 2, Lines Added: 20, Lines Deleted: 3; 1437 bytes
@@ -21,9 +21,9 @@
</indexterm>
<para>
- This section documents all changes and bug fixes as of the first
- MySQL Enterprise Server release (5.0.28) that are made available
- through hot-fixes, and through service packs.
+ This section documents all changes and bug fixes, beginning with the
+ first MySQL Enterprise Server release (5.0.28), that are made
+ available through hot-fixes, and through service packs.
</para>
<para>
@@ -77,6 +77,23 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: An inadvertent use of
+ unaligned data caused <command>ndb_restore</command> to fail
+ on some 64-bit platforms, including Sparc and Itanium-2. (Bug #26739)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: An infinite loop in an
+ internal logging function could cause trace logs to fill up
+ with <errortext>Unknown Signal type</errortext> error messages
+ and thus grow to unreasonable sizes. (Bug #26720)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-03-08 22:16:17 UTC (rev 5259)
+++ trunk/refman-5.1/news-5.1.xml 2007-03-09 02:05:40 UTC (rev 5260)
Changed blocks: 2, Lines Added: 47, Lines Deleted: 0; 2068 bytes
@@ -92,6 +92,45 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): A memory overflow
+ could occur with tables having a large amount of data stored
+ on disk, or with queries using a very high degree of
+ parallelism on Disk Data tables. (Bug #26514)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): Use of a
+ tablespace whose <literal>INITIAL_SIZE</literal> was greater
+ than 1 GB could cause the cluster to crash. (Bug #26487)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Using only the
+ <option>--print_data</option> option (and no other options) with
+ <command>ndb_restore</command> caused
+ <command>ndb_restore</command> to fail. (Bug# 26741)
+ </para>
+
+ <para>
+ This bug was introduced by the fix for Bug #14612.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: An infinite loop in an
+ internal logging function could cause trace logs to fill up
+ with <errortext>Unknown Signal type</errortext> error messages
+ and thus grow to unreasonable sizes. (Bug #26720)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -372,6 +411,14 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: An inadvertent use of
+ unaligned data caused <command>ndb_restore</command> to fail
+ on some 64-bit platforms, including Sparc and Itanium-2. (Bug #26739)
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5260 - branches/telcos/refman-5.1 trunk/refman-5.0 trunk/refman-5.1 | jon | 9 Mar |
