Author: jstephens
Date: 2007-04-25 10:00:40 +0200 (Wed, 25 Apr 2007)
New Revision: 6174
Log:
Fix entities
Change MCCGE sections titles (Stefan)
Put MCCGE sections after related mainline release sections
Modified:
trunk/refman-5.1/news-5.1-mccge.xml
Modified: trunk/refman-5.1/news-5.1-mccge.xml
===================================================================
--- trunk/refman-5.1/news-5.1-mccge.xml 2007-04-25 07:12:45 UTC (rev 6173)
+++ trunk/refman-5.1/news-5.1-mccge.xml 2007-04-25 08:00:40 UTC (rev 6174)
Changed blocks: 17, Lines Added: 1401, Lines Deleted: 1401; 117618 bytes
@@ -13,7 +13,7 @@
]>
<section id="news-5-1-x">
- <title>Changes in MySQL ¤t-series;</title>
+ <title>Changes in MySQL ¤t-series-mccge;</title>
<indexterm>
<primary>changes</primary>
@@ -27,7 +27,7 @@
<para>
For a full list of changes, please refer to the changelog sections
- for each individual MySQL ¤t-series; release.
+ for each individual MySQL ¤t-series-mccge; release.
</para>
<remark>
@@ -36,406 +36,10 @@
<filename>refman-common</filename> directory.
</remark>
- <section id="news-5-1-16-cge">
-
- <title>Changes in MySQL 5.1.16-Based ¤t-series; Releases</title>
-
- <para>
- This section contains change history information for
- ¤t-series; releases based on MySQL 5.1.15.
- </para>
-
- <section id="news-5-1-16-ndb-6-2-1">
-
- <title>Changes in release MySQL 5.1.16/NDB-6.2.1-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"/>. 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.16-ndb-6.2.0"/>.
- The file
- <filename>mysqlcom-5.1.16-ndb-6.2.0-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 Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.16/NDB-6.2.0, which includes all bugfixes and
- feature changes which were added in the mainline 5.1.16 release;
- information about these can be found in
- <xref linkend="news-5-1-16"/>.
- </para>
-
-<!--
- <important>
- <formalpara>
- <title>Upgrading to MySQL 5.1.16/NDB-6.2.1 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.3, 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 node 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.2.
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
- </formalpara>
- </important>
--->
-
-<!--
- <para>
- Functionality added or changed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- </para>
- </listitem>
-
- </itemizedlist>
--->
-
- <para>
- This release fixes the following bugs:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster APIs</emphasis>: An issue with
- the way in which the
- <literal>NdbDictionary::Dictionary::listEvents()</literal>
- method freed resources could sometimes lead to memory
- corruption. (Bug #27663)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster APIs</emphasis>: Using
- <literal>NdbBlob::writeData()</literal> to write data in the
- middle of an existing blob value (that is, updating the
- value) could overwrite some data past the end of the data to
- be changed. (Bug #27018)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>: Trying
- to replicate a large number of frequent updates with a
- relatively small relay log
- (<literal>max-relay-log-size</literal> set to 1M or less)
- could cause the slave to crash. (Bug #27529)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>: An SQL
- node acting as a replication master server could be a single
- point of failure; that is, if it failed, the replication
- slave had no way of knowing this, which could result in a
- mismatch of data between the master and the slave. (Bug
- #21494)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Memory usage of a <command>mysqld</command> process grew
- even while idle. (Bug #27560)
- </para>
- </listitem>
-
- <listitem>
- <para>
- The Cluster table handler did not set bits in null bytes
- correctly. (Bug #26591)
- </para>
- </listitem>
-
- <listitem>
- <para>
- When trying to create tables on an SQL node not connected to
- the cluster, a misleading error message <errortext>Table
- '<replaceable>tbl_name</replaceable>' already
- exists</errortext> was generated. The error now generated is
- <errortext>Could not connect to storage engine</errortext>.
- (Bug #18676)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Incorrect handling of fragmentation in a node takeover
- during a restart could cause stale data to be copied to the
- starting node, leading eventually to failure of the node.
- (Bug #27434)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Incorrect handling of fragmentation in a node takeover
- during a restart could cause stale data to be copied to the
- starting node, leading eventually to failure of the node.
- (Bug #27434)
- </para>
- </listitem>
-
- <listitem>
- <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. (Bug #27254)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqld</command> could crash shortly after a data
- node failure following certain DML operations. (Bug #27169)
- </para>
- </listitem>
-
- <listitem>
- <para>
- An incorrect assertion was made when sending a
- <literal>TCKEYFAILREF</literal> or
- <literal>TCKEYCONF</literal> message to a failed data node.
- (Bug #26814)
- </para>
- </listitem>
-
- </itemizedlist>
-
- </section>
-
- <section id="news-5-1-16-ndb-6-2-0">
-
- <title>Changes in release MySQL 5.1.16/NDB-6.2.0-beta (03 March 2007)</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"/>. 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.16-ndb-6.2.0"/>.
- The file
- <filename>mysqlcom-5.1.16-ndb-6.2.0-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 Beta release incorporates all bugfixes and feature changes
- which were added in MySQL 5.1.15/NDB-6.1.1 as well as in the
- mainline 5.1.16 release; information about these can be found in
- <xref linkend="news-5-1-15-ndb-6-1-1"/>, and in
- <xref linkend="news-5-1-16"/>.
- </para>
-
- <important>
- <formalpara>
- <title>Upgrading to MySQL 5.1.16/NDB-6.2.0 from a previous release</title>
-
-
-
- <para>
- This release is not binary compatible with previous MySQL
- ¤t-series; or mainline MySQL 5.1 releases. This means
- that:
-
- <itemizedlist>
-
- <listitem>
- <para>
- You cannot perform an online upgrade to this release
- from any of the MySQL ¤t-series; releases based
- on MySQL 5.1.14 or MySQL 5.1.15, or from 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>
- </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 any of the
- MySQL ¤t-series; releases based on MySQL 5.1.14
- or MySQL 5.1.15.
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
- </formalpara>
- </important>
-
- <para>
- Functionality added or changed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <formalpara>
- <title>Cluster APIs</title>
-
-
-
- <para>
- The <literal>Ndb::startTransaction()</literal> method now
- provides an alternative interface for starting a
- transaction. See
- <xref linkend="class-ndb-starttransaction"/>, for more
- information.
- </para>
- </formalpara>
- </listitem>
-
- <listitem>
- <formalpara>
- <title>Cluster APIs</title>
-
-
-
- <para>
- New methods have been added to the
- <literal>Ndb_cluster_connection</literal> class to
- faciliate iterating over existing <literal>Ndb</literal>
- objects. See
- <xref linkend="class-ndb-cluster-connection-get-next-ndb-object"/>,
- for more information.
- </para>
- </formalpara>
- </listitem>
-
- <listitem>
- <para>
- A new <literal>TcpBind_INADDR_ANY</literal> configuration
- parameter allows data nodes node to bind
- <literal>INADDR_ANY</literal> instead of a hostname or IP
- address in the <filename>config.ini</filename> file.
- </para>
- </listitem>
-
- <listitem>
- <para>
- A new <option>--ndb-wait-connected</option> option has been
- added for <command>mysqld</command>, which causes
- <command>mysqld</command> to wait for the specified amount
- of time to connect to the cluster before starting to accept
- MySQL client connections.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Memory allocation has been improved on 32-bit architectures
- that enables using close to 3GB for
- <literal>DataMemory</literal> and
- <literal>IndexMemory</literal> combined.
- </para>
- </listitem>
-
- <listitem>
- <para>
- It is now possible to disable arbitration by setting
- <literal>ArbitrationRank</literal> equal to
- <literal>0</literal> on all nodes.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- No new bugs were fixed in this release.
- </para>
-
- </section>
-
- </section>
-
<section id="news-5-1-16">
<title>Changes in release 5.1.16 (Not released separately for MySQL
- ¤t-series;)</title>
+ ¤t-series-mccge;)</title>
<para role="release-level">
This is a new Beta development release, fixing recently discovered
@@ -1306,104 +910,105 @@
</section>
- <section id="news-5-1-15-cge">
+ <section id="news-5-1-16-cge">
- <title>Changes in MySQL 5.1.15-Based ¤t-series; Releases</title>
+ <title>Changes in MySQL 5.1.16 Carrier Grade Edition</title>
<para>
This section contains change history information for
- ¤t-series; releases based on MySQL 5.1.15.
+ ¤t-series-mccge; releases based on MySQL 5.1.16.
</para>
- <section id="news-5-1-15-ndb-6-1-6">
+ <section id="news-5-1-16-ndb-6-2-1">
- <title>Changes in release MySQL 5.1.15/NDB-6.1.6-beta (Not yet released)</title>
+ <title>Changes in release MySQL 5.1.16-ndb-6.2.1-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.
+ previous ¤t-series-mccge; release.
</para>
-<!--
+<!--
<para>
- Like all releases for MySQL ¤t-series;, this is a
+ Like all releases for MySQL ¤t-series-mccge;, 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"/>. 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.5/"/>.
+ <ulink url="ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.16-ndb-6.2.0"/>.
The file
- <filename>mysqlcom-5.1.15-ndb-6.1.5-telco.tar.gz</filename> in
+ <filename>mysqlcom-5.1.16-ndb-6.2.0-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.
+ 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 Beta release 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, MySQL 5.1.15/NDB-6.1.3, MySQL
- 5.1.15/NDB-6.1.4, and MySQL 5.1.15/NDB-6.1.5. 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
- (see <xref linkend="news-5-1-15"/>).
+ made in MySQL 5.1.16/NDB-6.2.0, which includes all bugfixes and
+ feature changes which were added in the mainline 5.1.16 release;
+ information about these can be found in
+ <xref linkend="news-5-1-16"/>.
</para>
<!--
<important>
<formalpara>
- <title>Upgrading to MySQL 5.1.15/NDB-6.1.6 from a previous release</title>
+ <title>Upgrading to MySQL 5.1.16/NDB-6.2.1 from a previous release</title>
<para>
This release is not binary compatible with releases previous
- to MySQL 5.1.15/NDB-6.1.3. This means that:
+ 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,
- MySQL 5.1.15/NDB-6.1.2, 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.
+ 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.3, 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 node 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.3.
+ those compiled against MySQL 5.1.15/NDB-6.1.2.
</para>
</listitem>
</itemizedlist>
-
- This release is also not backwards compatible with MySQL
- -5.1.15/NDB-6.1.14 or any release previous to MySQL
- -5.1.15/NDB-6.1.14 due to changes in the
- <literal>mysql</literal> system database. See
- <citetitle>Functionality added or changed</citetitle> for more
- information.
</para>
</formalpara>
</important>
-->
-<!--
+<!--
<para>
Functionality added or changed:
</para>
@@ -1412,20 +1017,7 @@
<listitem>
<para>
- <emphasis role="bold">Incompatible change</emphasis>: The
- schema for the <literal>ndb_apply_status</literal> table in
- the <literal>mysql</literal> system database has changed. When
- upgrading to this release from a previous ¤t-series; or
- mainline MySQL 5.1 release, you must drop the
- <literal>mysql.ndb_apply_status</literal> table, then restart
- the server in order for the table to be re-created with the
- new schema.
</para>
-
- <para>
- See <xref linkend="mysql-cluster-replication-schema"/>, for
- additional information.
- </para>
</listitem>
</itemizedlist>
@@ -1436,44 +1028,6 @@
</para>
<itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>: It was
- possible for API nodes to begin interacting with the cluster
- subscription manager before they were fully connected to the
- cluster. (Bug #27651)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>: Under
- very high loads, checkpoints could be read or written with
- checkpoint indexes out of order. (Bug #27651)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Changes to a
- Disk Data table made as part of a transaction could not be
- seen by the client performing the changes until the
- transaction had been committed. (Bug #27757)
- </para>
- </listitem>
-
- <listitem>
- <para>
- An <literal>INSERT</literal> followed a delete
- <literal>DELETE</literal> on the same <literal>NDB</literal>
- table caused a memory leak. (Bug #27756)
- </para>
-
- <para>
- (This bug was introduced by the fix for Bug #20612.)
- </para>
- </listitem>
<listitem>
<para>
@@ -1487,6 +1041,16 @@
<listitem>
<para>
+ <emphasis role="bold">Cluster APIs</emphasis>: Using
+ <literal>NdbBlob::writeData()</literal> to write data in the
+ middle of an existing blob value (that is, updating the
+ value) could overwrite some data past the end of the data to
+ be changed. (Bug #27018)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<emphasis role="bold">Cluster Replication</emphasis>: Trying
to replicate a large number of frequent updates with a
relatively small relay log
@@ -1497,10 +1061,12 @@
<listitem>
<para>
- Under certain rare circumstances, <literal>DROP
- TABLE</literal> or <literal>TRUNCATE</literal> of an
- <literal>NDB</literal> table could cause a node failure or
- forced cluster shutdown. (Bug #27581)
+ <emphasis role="bold">Cluster Replication</emphasis>: An SQL
+ node acting as a replication master server could be a single
+ point of failure; that is, if it failed, the replication
+ slave had no way of knowing this, which could result in a
+ mismatch of data between the master and the slave. (Bug
+ #21494)
</para>
</listitem>
@@ -1513,120 +1079,89 @@
<listitem>
<para>
- A data node failing while another data node was restarting
- could leave the cluster in an inconsistent state. In certain
- rare cases, this could lead to a race condition and the
- eventual forced shutdown of the cluster. (Bug #27466)
+ The Cluster table handler did not set bits in null bytes
+ correctly. (Bug #26591)
</para>
</listitem>
<listitem>
<para>
- A data node failing while another data node was restarting
- could leave the cluster in an inconsistent state. In certain
- rare cases, this could lead to a race condition and the
- eventual forced shutdown of the cluster. (Bug #27466)
+ When trying to create tables on an SQL node not connected to
+ the cluster, a misleading error message <errortext>Table
+ '<replaceable>tbl_name</replaceable>' already
+ exists</errortext> was generated. The error now generated is
+ <errortext>Could not connect to storage engine</errortext>.
+ (Bug #18676)
</para>
</listitem>
<listitem>
<para>
- <command>mysqld</command> could crash shortly after a data
- node failure following certain DML operations. (Bug #27169)
+ Incorrect handling of fragmentation in a node takeover
+ during a restart could cause stale data to be copied to the
+ starting node, leading eventually to failure of the node.
+ (Bug #27434)
</para>
</listitem>
<listitem>
<para>
- <emphasis role="bold">Disk Data</emphasis>: <literal>DROP
- INDEX</literal> on a Disk Data table did not always move
- data from memory into the tablespace. (Bug #25877)
+ Incorrect handling of fragmentation in a node takeover
+ during a restart could cause stale data to be copied to the
+ starting node, leading eventually to failure of the node.
+ (Bug #27434)
</para>
</listitem>
<listitem>
<para>
- It was not possible to set
- <literal>LockPagesInMainMemory</literal> equal to
- <literal>0</literal>. (Bug #27291)
+ 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. (Bug #27254)
</para>
</listitem>
<listitem>
<para>
- A race condition could sometimes occur if the node acting as
- master failed while node IDs were still being allocated
- during startup. (Bug #27286)
+ <command>mysqld</command> could crash shortly after a data
+ node failure following certain DML operations. (Bug #27169)
</para>
</listitem>
<listitem>
<para>
- When a data node was taking over as the master node, a race
- condition could sometimes occur as the node was assuming
- responsibility for handling of global checkpoints. (Bug
- #27283)
+ An incorrect assertion was made when sending a
+ <literal>TCKEYFAILREF</literal> or
+ <literal>TCKEYCONF</literal> message to a failed data node.
+ (Bug #26814)
</para>
</listitem>
- <listitem>
- <para>
- A delete operation using a scan following by an insert using
- a scan could cause a data node to fail. (Bug #27203)
- </para>
- </listitem>
-
- <listitem>
- <para>
- The same failed request from an API node could be handled by
- the cluster multiple times, resulting in reduced
- performance. (Bug #27087)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqld</command> processes would sometimes crash
- under high load. (Bug #26825)
- </para>
-
- <para>
- This improves on and replaces the fix for this bug that was
- made in MySQL 5.1.15/NDB-6.1.5.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The failure of a data node while restarting could cause
- other data nodes to hang or crash. (Bug #27003)
- </para>
- </listitem>
-
</itemizedlist>
</section>
- <section id="news-5-1-15-ndb-6-1-5">
+ <section id="news-5-1-16-ndb-6-2-0">
- <title>Changes in release MySQL 5.1.15/NDB-6.1.5-beta (15 March 2007)</title>
+ <title>Changes in release MySQL 5.1.16-ndb-6.2.0-beta (03 March 2007)</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.
+ previous ¤t-series-mccge; release.
</para>
<para>
- Like all releases for MySQL ¤t-series;, this is a
+ Like all releases for MySQL ¤t-series-mccge;, 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"/>. 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.5/"/>.
+ <ulink url="ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.16-ndb-6.2.0"/>.
The file
- <filename>mysqlcom-5.1.15-ndb-6.1.5-telco.tar.gz</filename> in
+ <filename>mysqlcom-5.1.16-ndb-6.2.0-telco.tar.gz</filename> in
this directory contains the complete source archive.
</para>
@@ -1641,34 +1176,32 @@
<para>
This Beta release 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, MySQL 5.1.15/NDB-6.1.3, and MySQL
- 5.1.15/NDB-6.1.4. 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 (see
- <xref linkend="news-5-1-15"/>).
+ which were added in MySQL 5.1.15/NDB-6.1.1 as well as in the
+ mainline 5.1.16 release; information about these can be found in
+ <xref linkend="news-5-1-15-ndb-6-1-1"/>, and in
+ <xref linkend="news-5-1-16"/>.
</para>
<important>
<formalpara>
- <title>Upgrading to MySQL 5.1.15/NDB-6.1.5 from a previous release</title>
+ <title>Upgrading to MySQL 5.1.16/NDB-6.2.0 from a previous release</title>
-
<para>
- This release is not binary compatible with releases previous
- to MySQL 5.1.15/NDB-6.1.3. This means that:
+ This release is not binary compatible with previous MySQL
+ ¤t-series-mccge; or mainline MySQL 5.1 releases. 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,
- MySQL 5.1.15/NDB-6.1.2, 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.
+ from any of the MySQL ¤t-series-mccge; releases
+ based on MySQL 5.1.14 or MySQL 5.1.15, or from 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>
</listitem>
@@ -1676,20 +1209,15 @@
<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.3.
+ Cluster, including those compiled against any of the
+ MySQL ¤t-series-mccge; releases based on MySQL
+ 5.1.14 or MySQL 5.1.15.
</para>
</listitem>
</itemizedlist>
+ </para>
- This release is also not backwards compatible with MySQL
- -5.1.15/NDB-6.1.14 or any release previous to MySQL
- -5.1.15/NDB-6.1.14 due to changes in the
- <literal>mysql</literal> system database. See
- <citetitle>Functionality added or changed</citetitle> for
- more information.
- </para>
</formalpara>
</important>
@@ -1700,778 +1228,93 @@
<itemizedlist>
<listitem>
- <para>
- <emphasis role="bold">Incompatible change</emphasis>: The
- schema for the <literal>ndb_apply_status</literal> table in
- the <literal>mysql</literal> system database has changed.
- When upgrading to this release from a previous
- ¤t-series; or mainline MySQL 5.1 release, you must
- drop the <literal>mysql.ndb_apply_status</literal> table,
- then restart the server in order for the table to be
- re-created with the new schema.
- </para>
+ <formalpara>
- <para>
- See <xref linkend="mysql-cluster-replication-schema"/>, for
- additional information.
- </para>
- </listitem>
+ <title>Cluster APIs</title>
- </itemizedlist>
+ <para>
+ The <literal>Ndb::startTransaction()</literal> method now
+ provides an alternative interface for starting a
+ transaction. See
+ <xref linkend="class-ndb-starttransaction"/>, for more
+ information.
+ </para>
- <para>
- This release fixes the following bugs:
- </para>
-
- <itemizedlist>
-
- <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>
+ </formalpara>
</listitem>
<listitem>
- <para>
- Creating a table on one SQL node while in single user mode
- caused other SQL nodes to crash. (Bug #26997)
- </para>
- </listitem>
+ <formalpara>
- <listitem>
- <para>
- <command>mysqld</command> processes would sometimes crash
- under high load. (Bug #26825)
- </para>
- </listitem>
+ <title>Cluster APIs</title>
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: When creating a
- log file group, setting <literal>INITIAL_SIZE</literal> to
- less than <literal>UNDO_BUFFER_SIZE</literal> caused data
- nodes to crash. (Bug #25743)
- </para>
- </listitem>
+ <para>
+ New methods have been added to the
+ <literal>Ndb_cluster_connection</literal> class to
+ faciliate iterating over existing <literal>Ndb</literal>
+ objects. See
+ <xref linkend="class-ndb-cluster-connection-get-next-ndb-object"/>,
+ for more information.
+ </para>
- </itemizedlist>
-
- </section>
-
- <section id="news-5-1-15-ndb-6-1-4">
-
- <title>Changes in release MySQL 5.1.15/NDB-6.1.4-beta (09 March 2007 - testing
- only)</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"/>. 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.4/"/>.
- The file
- <filename>mysqlcom-5.1.15-ndb-6.1.4-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 Beta release 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
- (see <xref linkend="news-5-1-15"/>).
- </para>
-
- <important>
- <formalpara>
- <title>Upgrading to MySQL 5.1.15/NDB-6.1.4 from a previous release</title>
-
-
-
- <para>
- This release is not binary compatible with previous
- releases. 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,
- MySQL 5.1.15/NDB-6.1.2, 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>
- </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.3.
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
- </formalpara>
- </important>
-
- <para>
- Functionality added or changed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">NDB API</emphasis>: It is now possible
- to specify the transaction coordinator when starting a
- transaction. See
- <xref linkend="class-ndb-starttransaction"/>, for more
- information.
- </para>
+ </formalpara>
</listitem>
<listitem>
<para>
- <emphasis role="bold">NDB API</emphasis>: It is now possible
- to iterate over all existing <literal>Ndb</literal> objects
- using three new methods of the
- <literal>Ndb_cluster_connection</literal> class:
- <literal>lock_ndb_objects()</literal>,
- <literal>get_next_ndb_object()</literal>, and
- <literal>unlock_ndb_objects()</literal>. For more
- information about these methods and their use, see
- <xref linkend="class-ndb-cluster-connection-get-next-ndb-object"/>,
- in the MySQL Cluster API Guide.
+ A new <literal>TcpBind_INADDR_ANY</literal> configuration
+ parameter allows data nodes node to bind
+ <literal>INADDR_ANY</literal> instead of a hostname or IP
+ address in the <filename>config.ini</filename> file.
</para>
</listitem>
<listitem>
<para>
- A new option <option>--ndb-wait-connected</option> has been
- added for <command>mysqld</command>. It causes
- <command>mysqld</command> wait a specified amount of time to
- be connected to the cluster before starting to accept client
- connections. See
- <link linkend="optvar_ndb-wait-connected">here</link>, for
- more information.
+ A new <option>--ndb-wait-connected</option> option has been
+ added for <command>mysqld</command>, which causes
+ <command>mysqld</command> to wait for the specified amount
+ of time to connect to the cluster before starting to accept
+ MySQL client connections.
</para>
</listitem>
<listitem>
<para>
- Data node memory allocation has been improved. On 32-bit
- platforms, it should now be possible to use close to 3GB RAM
- for <literal>IndexMemory</literal> and
- <literal>DataMemory</literal> combined.
+ Memory allocation has been improved on 32-bit architectures
+ that enables using close to 3GB for
+ <literal>DataMemory</literal> and
+ <literal>IndexMemory</literal> combined.
</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>
- 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">
-
- <title>Changes in release MySQL 5.1.15/NDB-6.1.3-beta (25 February 2007)</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"/>. 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 Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14/NDB-6.1.0, MySQL 5.1.15/NDB-6.1.1, and
- MySQL 5.1.15/NDB-6.1.2. This version also incorporates all
- bugfixes and feature changes which were added in the mainline
- 5.1.15 release; information about these can be found in
- <xref linkend="news-5-1-15"/>.
- </para>
-
- <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.3, 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>--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.2.
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
- </formalpara>
- </important>
-
- <para>
- Functionality added or changed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- The <command>ndb_show_tables</command> utility now displays
- information about table events. (See
- <xref linkend="mysql-cluster-utilities-ndb-show-tables"/>.)
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <command>ndbd_redo_log_reader</command> utility is now
- part of the default build. For more information, see
- <xref linkend="mysql-cluster-utilities-ndbd-redo-log-reader"/>.
- </para>
- </listitem>
-
- <listitem>
- <para>
It is now possible to disable arbitration by setting
- <literal>ArbitrationRank=0</literal> on all management and
- SQL nodes.
+ <literal>ArbitrationRank</literal> equal to
+ <literal>0</literal> on all nodes.
</para>
</listitem>
- <listitem>
- <para>
- <emphasis role="bold">NDB API</emphasis>: A new
- <literal>listEvents()</literal> method has been added to the
- <literal>Dictionary</literal> class. See
- <xref linkend="class-dictionary-listevents"/>, for more
- information.
- </para>
- </listitem>
-
</itemizedlist>
<para>
- This release fixes the following bugs:
+ No new bugs were fixed in this release.
</para>
- <itemizedlist>
-
- <listitem>
- <para>
- <literal>NDB Cluster</literal>: An invalid pointer was
- returned following a <literal>FSCLOSECONF</literal> signal
- when accessing the REDO logs during a node restart or system
- restart. (Bug #26515)
- </para>
- </listitem>
-
- <listitem>
- <para>
- No appropriate error message was provided when there was
- insufficient REDO log file space for the cluster to start.
- (Bug #25801)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: 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>
- A memory allocation failure in the cluster Subscription
- Manager could cause the cluster to crash. (Bug #25239)
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <errorname>InvalidUndoBufferSize</errorname> error used
- the same error code (<errorcode>763</errorcode>) as the
- <errorname>IncompatibleVersions</errorname> error.
- <errorname>InvalidUndoBufferSize</errorname> now uses its
- own error code (<errorcode>779</errorcode>). (Bug #26490)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: 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>
- The failure of a data node when restarting it with
- <option>--initial</option> could lead to failures of
- subsequent data node restarts. (Bug #26481)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Takeover for local checkpointing due to multiple failures of
- master nodes was sometimes handled incorrectly. (Bug #26457)
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <literal>LockPagesInMemory</literal> parameter was not
- read until after distributed communication had already
- started between cluster nodes. When the value of this
- parameter was <literal>1</literal>, this could sometimes
- result in data node failure due to missed heartbeats. (Bug
- #26454)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Under some circumstances, following the restart of a
- management node, all cluster data nodes would connect to it
- normally, but some of them subsequently failed to log any
- events to the management node. (Bug #26293)
- </para>
- </listitem>
-
- <listitem>
- <para>
- An error was produced when <literal>SHOW TABLE
- STATUS</literal> was used on an <literal>NDB</literal> table
- that had no <literal>AUTO_INCREMENT</literal> column. (Bug
- #21033)
- </para>
-
- <note>
- <para>
- This improves on and supersedes an earlier fix that was
- made for this issue in MySQL 5.1.12.
- </para>
- </note>
- </listitem>
-
- </itemizedlist>
-
</section>
- <section id="news-5-1-15-ndb-6-1-2">
-
- <title>Changes in release MySQL 5.1.15/NDB-6.1.2-beta (07 February 2007)</title>
-
- <para role="release-level">
- This is a new Beta development release, fixing a recently
- discovered bug.
- </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"/>. 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.2"/>.
- The file
- <filename>mysqlcom-5.1.15-ndb-6.1.2-telco.tar.gz</filename> in
- this directory contains the complete source archive.
- </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"/>. 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.2"/>.
- The file
- <filename>mysqlcom-5.1.15-ndb-6.1.2-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 Beta release is a hotfix release, made to resolve a single
- critical issue which occurred in MySQL 5.1.15/NDB-6.1.1-beta. It
- incorporates all bugfixes and feature changes made in MySQL
- 5.1.14/NDB-6.1.0 and MySQL 5.1.15/NDB-6.1.1. This version also
- incorporates all bugfixes and feature changes which were added
- in the mainline 5.1.15 release; information about these can be
- found in <xref linkend="news-5-1-15"/>.
- </para>
-
- <important>
- <formalpara>
- <title>Upgrading to MySQL 5.1.15/NDB-6.1.2 from a previous release</title>
-
-
-
- <para>
- This release is not binary compatible with any previous
- releases. 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. You must
- shut down the cluster, replace all binaries, then
- restart the cluster.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You must recompile any MySQL Cluster API applications
- used with a previous version of MySQL Cluster. This
- includes all NDB API and MGM API applications.
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
- </formalpara>
- </important>
-
- <para>
- This release fixes a single critical bug:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Using node IDs greater than 48 could sometimes lead to
- incorrect memory access and a subsequent forced shutdown of
- the cluster. (Bug #26267)
- </para>
- </listitem>
-
- </itemizedlist>
-
- </section>
-
- <section id="news-5-1-15-ndb-6-1-1">
-
- <title>Changes in release MySQL 5.1.15/NDB-6.1.1-beta (01 February 2007)</title>
-
- <para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
- </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"/>. 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.1"/>.
- The file
- <filename>mysqlcom-5.1.15-ndb-6.1.1-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 section documents all changes and bug fixes that have been
- applied in this Beta release since the release of MySQL Cluster
- 5.1.14/NDB-6.1.0. This version also incorporates all bugfixes
- and feature changes which were added in the mainline 5.1.15
- release; information about these can be found in
- <xref linkend="news-5-1-15"/>.
- </para>
-
- <important>
- <formalpara>
- <title>Upgrading to MySQL 5.1.15/NDB-6.1.1 from a previous release</title>
-
-
-
- <para>
- This release is not binary compatible with any previous
- releases. This means that:
-
- <itemizedlist>
-
- <listitem>
- <para>
- You cannot perform an online upgrade to this release
- from either MySQL 5.1.14/NDB-6.1.0 or from any of the
- mainline MySQL 5.1 releases. You must shut down the
- cluster, replace all binaries, then restart the
- cluster.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You must recompile any MySQL Cluster API applications
- used with a previous version of MySQL Cluster. This
- includes all NDB API and MGM API applications.
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
- </formalpara>
- </important>
-
- <para>
- Functionality added or changed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <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.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <literal>LockPagesInMainMemory</literal> configuration
- parameter has changed its type and possible values. For more
- information, see
- <literal><link linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory">LockPagesInMainMemory</link></literal>.
- (Bug #25686)
- </para>
-
- <para>
- <emphasis role="bold">Important</emphasis>: The values
- <literal>true</literal> and <literal>false</literal> are no
- longer accepted for this parameter. If you were using this
- parameter and had it set to <literal>false</literal> in a
- previous release, you must change it to
- <literal>0</literal>. If you had this parameter set to
- <literal>true</literal>, you should instead use
- <literal>1</literal> to obtain the same behavior as
- previously, or <literal>2</literal> to take advantage of new
- functionality introduced with this release described in the
- section cited above.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- A memory leak could cause problems during a node or cluster
- shutdown or failure. (Bug #25997)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- Certain errors in replication setups could lead to
- subsequent node failures. (Bug #25755)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Hosts in clusters with a large number of nodes could
- experience excessive CPU usage while obtaining configuration
- data. (Bug #25711)
- </para>
- </listitem>
-
- <listitem>
- <para>
- When stopping and restarting multiple data nodes, the last
- node to be restarted would sometimes hang in Phase 100. (Bug
- #19645)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster APIs</emphasis> /
- <emphasis role="bold">Disk Data</emphasis>: A delete and a
- read peformed in the same operation could cause one or more
- of the cluster's data nodes to crash. This could occur when
- the operation affected more than 5 columns concurrently, or
- when one or more of the columns was of the VARCHAR type and
- was stored on disk. (Bug #25794)
- </para>
- </listitem>
-
- <listitem>
- <para>
- An element could sometimes be inserted twice into the hash
- table, causing a data node to crash. (Bug #25286)
- </para>
- </listitem>
-
- </itemizedlist>
-
- </section>
-
</section>
<section id="news-5-1-15">
<title>Changes in release 5.1.15 (Not released separately for MySQL
- ¤t-series;)</title>
+ ¤t-series-mccge;)</title>
<para>
This section documents all changes and bug fixes that were applied
in MySQL 5.1.15 and subsequently incorporated into MySQL
- 5.1.15/NDB-6.1.1 and later ¤t-series; releases.
+ 5.1.15/NDB-6.1.1 and later ¤t-series-mccge; releases.
</para>
<para>
@@ -2592,12 +1435,12 @@
<listitem>
<para>
- In MySQL ¤t-series;, <literal>InnoDB</literal> rolls
- back only the last statement on a transaction timeout. A new
- option, <option>--innodb_rollback_on_timeout</option>, causes
- <literal>InnoDB</literal> to abort and roll back the entire
- transaction if a transaction timeout occurs (the same behavior
- as in MySQL 4.1). (Bug #24200)
+ In MySQL ¤t-series-mccge;, <literal>InnoDB</literal>
+ rolls back only the last statement on a transaction timeout. A
+ new option, <option>--innodb_rollback_on_timeout</option>,
+ causes <literal>InnoDB</literal> to abort and roll back the
+ entire transaction if a transaction timeout occurs (the same
+ behavior as in MySQL 4.1). (Bug #24200)
</para>
</listitem>
@@ -3782,59 +2625,485 @@
</section>
- <section id="news-5-1-14-cge">
+ <section id="news-5-1-15-cge">
- <title>Changes in MySQL 5.1.14-Based ¤t-series; Releases</title>
+ <title>Changes in MySQL 5.1.15 Carrier Grade Edition</title>
<para>
This section contains change history information for
- ¤t-series; releases based on MySQL 5.1.14.
+ ¤t-series-mccge; releases based on MySQL 5.1.15.
</para>
- <section id="news-5-1-14-ndb-6-1-0">
+ <section id="news-5-1-15-ndb-6-1-6">
- <title>Changes in release MySQL 5.1.14/NDB-6.1.0-beta (20 December 2006)</title>
+ <title>Changes in release MySQL 5.1.15-ndb-6.1.6-beta (Not yet released)</title>
<para role="release-level">
This is a new Beta development release, fixing recently
- discovered bugs.
+ discovered bugs and incorporating improvements made since the
+ previous ¤t-series-mccge; release.
</para>
+<!--
<para>
- Like all releases for MySQL ¤t-series;, this is a
+ Like all releases for MySQL ¤t-series-mccge;, 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"/>. 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.5/"/>.
+ The file
+ <filename>mysqlcom-5.1.15-ndb-6.1.5-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 Beta release 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, MySQL 5.1.15/NDB-6.1.3, MySQL
+ 5.1.15/NDB-6.1.4, and MySQL 5.1.15/NDB-6.1.5. 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
+ (see <xref linkend="news-5-1-15"/>).
+ </para>
+
+<!--
+ <important>
+ <formalpara>
+ <title>Upgrading to MySQL 5.1.15/NDB-6.1.6 from a previous release</title>
+
+
+
+ <para>
+ This release is not binary compatible with releases previous
+ to MySQL 5.1.15/NDB-6.1.3. 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,
+ MySQL 5.1.15/NDB-6.1.2, 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>
+ </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.3.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ This release is also not backwards compatible with MySQL
+ -5.1.15/NDB-6.1.14 or any release previous to MySQL
+ -5.1.15/NDB-6.1.14 due to changes in the
+ <literal>mysql</literal> system database. See
+ <citetitle>Functionality added or changed</citetitle> for more
+ information.
+ </para>
+ </formalpara>
+ </important>
+-->
+
+<!--
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Incompatible change</emphasis>: The
+ schema for the <literal>ndb_apply_status</literal> table in
+ the <literal>mysql</literal> system database has changed. When
+ upgrading to this release from a previous ¤t-series-mccge; or
+ mainline MySQL 5.1 release, you must drop the
+ <literal>mysql.ndb_apply_status</literal> table, then restart
+ the server in order for the table to be re-created with the
+ new schema.
+ </para>
+
+ <para>
+ See <xref linkend="mysql-cluster-replication-schema"/>, for
+ additional information.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+-->
+
+ <para>
+ This release fixes the following bugs:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Cluster Replication</emphasis>: It was
+ possible for API nodes to begin interacting with the cluster
+ subscription manager before they were fully connected to the
+ cluster. (Bug #27651)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Cluster Replication</emphasis>: Under
+ very high loads, checkpoints could be read or written with
+ checkpoint indexes out of order. (Bug #27651)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Disk Data</emphasis>: Changes to a
+ Disk Data table made as part of a transaction could not be
+ seen by the client performing the changes until the
+ transaction had been committed. (Bug #27757)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An <literal>INSERT</literal> followed a delete
+ <literal>DELETE</literal> on the same <literal>NDB</literal>
+ table caused a memory leak. (Bug #27756)
+ </para>
+
+ <para>
+ (This bug was introduced by the fix for Bug #20612.)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Cluster APIs</emphasis>: An issue with
+ the way in which the
+ <literal>NdbDictionary::Dictionary::listEvents()</literal>
+ method freed resources could sometimes lead to memory
+ corruption. (Bug #27663)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Cluster Replication</emphasis>: Trying
+ to replicate a large number of frequent updates with a
+ relatively small relay log
+ (<literal>max-relay-log-size</literal> set to 1M or less)
+ could cause the slave to crash. (Bug #27529)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Under certain rare circumstances, <literal>DROP
+ TABLE</literal> or <literal>TRUNCATE</literal> of an
+ <literal>NDB</literal> table could cause a node failure or
+ forced cluster shutdown. (Bug #27581)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Memory usage of a <command>mysqld</command> process grew
+ even while idle. (Bug #27560)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A data node failing while another data node was restarting
+ could leave the cluster in an inconsistent state. In certain
+ rare cases, this could lead to a race condition and the
+ eventual forced shutdown of the cluster. (Bug #27466)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A data node failing while another data node was restarting
+ could leave the cluster in an inconsistent state. In certain
+ rare cases, this could lead to a race condition and the
+ eventual forced shutdown of the cluster. (Bug #27466)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqld</command> could crash shortly after a data
+ node failure following certain DML operations. (Bug #27169)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Disk Data</emphasis>: <literal>DROP
+ INDEX</literal> on a Disk Data table did not always move
+ data from memory into the tablespace. (Bug #25877)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ It was not possible to set
+ <literal>LockPagesInMainMemory</literal> equal to
+ <literal>0</literal>. (Bug #27291)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A race condition could sometimes occur if the node acting as
+ master failed while node IDs were still being allocated
+ during startup. (Bug #27286)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When a data node was taking over as the master node, a race
+ condition could sometimes occur as the node was assuming
+ responsibility for handling of global checkpoints. (Bug
+ #27283)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A delete operation using a scan following by an insert using
+ a scan could cause a data node to fail. (Bug #27203)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The same failed request from an API node could be handled by
+ the cluster multiple times, resulting in reduced
+ performance. (Bug #27087)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqld</command> processes would sometimes crash
+ under high load. (Bug #26825)
+ </para>
+
+ <para>
+ This improves on and replaces the fix for this bug that was
+ made in MySQL 5.1.15/NDB-6.1.5.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The failure of a data node while restarting could cause
+ other data nodes to hang or crash. (Bug #27003)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="news-5-1-15-ndb-6-1-5">
+
+ <title>Changes in release MySQL 5.1.15-ndb-6.1.5-beta (15 March 2007)</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-mccge; release.
+ </para>
+
+ <para>
+ Like all releases for MySQL ¤t-series-mccge;, 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"/>. 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.14-ndb-6.1.0"/>.
- There are two version of the source archive in this directory:
+ <ulink url="ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.15-ndb-6.1.5/"/>.
+ The file
+ <filename>mysqlcom-5.1.15-ndb-6.1.5-telco.tar.gz</filename> in
+ this directory contains the complete source archive.
+ </para>
- <itemizedlist>
+ <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>
- <listitem>
- <para>
- <filename>mysql-5.1.14-ndb-6.1.0-telco.tar.gz</filename>:
- This is the GPL version. Customers who are using MySQL
- ¤t-series; under a commercial licence must
- <emphasis>not</emphasis> use this version in a production
- setting.
- </para>
- </listitem>
+ <para>
+ This Beta release 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, MySQL 5.1.15/NDB-6.1.3, and MySQL
+ 5.1.15/NDB-6.1.4. 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 (see
+ <xref linkend="news-5-1-15"/>).
+ </para>
- <listitem>
- <para>
- <filename>mysqlcom-5.1.14-ndb-6.1.0-telco.tar.gz</filename>:
- This is the commercial version. Customers who are using
- MySQL ¤t-series; under a commercial licence
- <emphasis>must</emphasis> use this version in any setting
- covered under their licence agreement with MySQL AB.
- </para>
- </listitem>
+ <important>
+ <formalpara>
- </itemizedlist>
+ <title>Upgrading to MySQL 5.1.15/NDB-6.1.5 from a previous release</title>
+
+ <para>
+ This release is not binary compatible with releases previous
+ to MySQL 5.1.15/NDB-6.1.3. 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,
+ MySQL 5.1.15/NDB-6.1.2, 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>
+ </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.3.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ This release is also not backwards compatible with MySQL
+ -5.1.15/NDB-6.1.14 or any release previous to MySQL
+ -5.1.15/NDB-6.1.14 due to changes in the
+ <literal>mysql</literal> system database. See
+ <citetitle>Functionality added or changed</citetitle> for
+ more information.
+ </para>
+
+ </formalpara>
+ </important>
+
+ <para>
+ Functionality added or changed:
</para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Incompatible change</emphasis>: The
+ schema for the <literal>ndb_apply_status</literal> table in
+ the <literal>mysql</literal> system database has changed.
+ When upgrading to this release from a previous
+ ¤t-series-mccge; or mainline MySQL 5.1 release, you
+ must drop the <literal>mysql.ndb_apply_status</literal>
+ table, then restart the server in order for the table to be
+ re-created with the new schema.
+ </para>
+
+ <para>
+ See <xref linkend="mysql-cluster-replication-schema"/>, for
+ additional information.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ This release fixes the following bugs:
+ </para>
+
+ <itemizedlist>
+
+ <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>
+ Creating a table on one SQL node while in single user mode
+ caused other SQL nodes to crash. (Bug #26997)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqld</command> processes would sometimes crash
+ under high load. (Bug #26825)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Disk Data</emphasis>: When creating a
+ log file group, setting <literal>INITIAL_SIZE</literal> to
+ less than <literal>UNDO_BUFFER_SIZE</literal> caused data
+ nodes to crash. (Bug #25743)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="news-5-1-15-ndb-6-1-4">
+
+ <title>Changes in release MySQL 5.1.15-ndb-6.1.4-beta (09 March 2007 - testing
+ only)</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-mccge; release.
+ </para>
+
+ <para>
+ Like all releases for MySQL ¤t-series-mccge;, 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"/>. 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.4/"/>.
+ The file
+ <filename>mysqlcom-5.1.15-ndb-6.1.4-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
@@ -3845,11 +3114,51 @@
</para>
<para>
- This section documents all changes and bug fixes that have been
- applied in this Beta release since MySQL ¤t-series;
- diverged from MySQL 5.1.14 standard.
+ This Beta release 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
+ (see <xref linkend="news-5-1-15"/>).
</para>
+ <important>
+ <formalpara>
+
+ <title>Upgrading to MySQL 5.1.15/NDB-6.1.4 from a previous release</title>
+
+ <para>
+ This release is not binary compatible with previous
+ releases. 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,
+ MySQL 5.1.15/NDB-6.1.2, 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>
+ </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.3.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ </formalpara>
+ </important>
+
<para>
Functionality added or changed:
</para>
@@ -3858,144 +3167,625 @@
<listitem>
<para>
- Support was added for a new
- <literal>MemReportFrequency</literal> configuration
- parameter that provides for periodic reports of memory
- usage. See
- <xref linkend="mysql-cluster-config-params-mgm"/>, for
- information about using this parameter.
+ <emphasis role="bold">NDB API</emphasis>: It is now possible
+ to specify the transaction coordinator when starting a
+ transaction. See
+ <xref linkend="class-ndb-starttransaction"/>, for more
+ information.
</para>
</listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">NDB API</emphasis>: It is now possible
+ to iterate over all existing <literal>Ndb</literal> objects
+ using three new methods of the
+ <literal>Ndb_cluster_connection</literal> class:
+ <literal>lock_ndb_objects()</literal>,
+ <literal>get_next_ndb_object()</literal>, and
+ <literal>unlock_ndb_objects()</literal>. For more
+ information about these methods and their use, see
+ <xref linkend="class-ndb-cluster-connection-get-next-ndb-object"/>,
+ in the MySQL Cluster API Guide.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A new option <option>--ndb-wait-connected</option> has been
+ added for <command>mysqld</command>. It causes
+ <command>mysqld</command> wait a specified amount of time to
+ be connected to the cluster before starting to accept client
+ connections. See
+ <link linkend="optvar_ndb-wait-connected">here</link>, for
+ more information.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Data node memory allocation has been improved. On 32-bit
+ platforms, it should now be possible to use close to 3GB RAM
+ for <literal>IndexMemory</literal> and
+ <literal>DataMemory</literal> combined.
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
- Bugs fixed:
+ This release fixes the following bugs:
</para>
<itemizedlist>
<listitem>
<para>
- <emphasis role="bold">NDB API</emphasis>: A unique index
- lookup on a non-existent tuple could lead to a data node
- timeout (error 4012). (Bug #25059)
+ 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>
- A <literal>SELECT</literal> statement performing a primary
- key lookup on a table with a <literal>VARCHAR</literal>
- primary key, and where a <literal>BLOB</literal> or
- <literal>TEXT</literal> column was among the columns
- selected, would produce an empty result set. (Bug #19956)
+ 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>
- <emphasis role="bold">NDB API</emphasis>: 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. (Bug #24949)
+ 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">
+
+ <title>Changes in release MySQL 5.1.15-ndb-6.1.3-beta (25 February 2007)</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-mccge; release.
+ </para>
+
+ <para>
+ Like all releases for MySQL ¤t-series-mccge;, 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"/>. 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 Beta release incorporates all bugfixes and feature changes
+ made in MySQL 5.1.14/NDB-6.1.0, MySQL 5.1.15/NDB-6.1.1, and
+ MySQL 5.1.15/NDB-6.1.2. This version also incorporates all
+ bugfixes and feature changes which were added in the mainline
+ 5.1.15 release; information about these can be found in
+ <xref linkend="news-5-1-15"/>.
+ </para>
+
+ <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.3, 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>--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.2.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ </formalpara>
+ </important>
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
<listitem>
<para>
- <emphasis role="bold">Disk Data</emphasis>: A
- <literal>MEDIUMTEXT</literal> column of a Disk Data table
- was stored in memory rather than on disk, even if the column
- was not indexed. (Bug #25001)
+ The <command>ndb_show_tables</command> utility now displays
+ information about table events. (See
+ <xref linkend="mysql-cluster-utilities-ndb-show-tables"/>.)
</para>
</listitem>
<listitem>
<para>
- Under certain rare circumstances, local checkpoints were not
- performed properly, leading to an inability to restart one
- or more data nodes. (Bug #24664)
+ The <command>ndbd_redo_log_reader</command> utility is now
+ part of the default build. For more information, see
+ <xref linkend="mysql-cluster-utilities-ndbd-redo-log-reader"/>.
</para>
</listitem>
<listitem>
<para>
- <emphasis role="bold">Disk Data</emphasis>: Performing a
- node restart with a newly dropped Disk Data table could lead
- to failure of the node during the restart. (Bug #24917)
+ It is now possible to disable arbitration by setting
+ <literal>ArbitrationRank=0</literal> on all management and
+ SQL nodes.
</para>
</listitem>
<listitem>
<para>
- <emphasis role="bold">Disk Data</emphasis>: Repeated
- <literal>CREATE</literal>, <literal>DROP</literal>, or
- <literal>TRUNCATE</literal> in various combinations with
- system restarts between these operations could lead to the
- eventual failure of a system restart. (Bug #21948)
+ <emphasis role="bold">NDB API</emphasis>: A new
+ <literal>listEvents()</literal> method has been added to the
+ <literal>Dictionary</literal> class. See
+ <xref linkend="class-dictionary-listevents"/>, for more
+ information.
</para>
</listitem>
+ </itemizedlist>
+
+ <para>
+ This release fixes the following bugs:
+ </para>
+
+ <itemizedlist>
+
<listitem>
<para>
- <emphasis role="bold">Disk Data</emphasis>: Extents that
- should have been available for re-use following a DROP TABLE
- operation were not actually made available again until after
- the cluster performed a local checkpoint. (Bug #17605)
+ <literal>NDB Cluster</literal>: An invalid pointer was
+ returned following a <literal>FSCLOSECONF</literal> signal
+ when accessing the REDO logs during a node restart or system
+ restart. (Bug #26515)
</para>
</listitem>
<listitem>
<para>
- When a data node was shut down using the management client
- <literal>STOP</literal> command, a connection event
- (<literal>NDB_LE_Connected</literal>) was logged instead of
- a disconnection event
- (<literal>NDB_LE_Disconnected</literal>). (Bug #22773)
+ No appropriate error message was provided when there was
+ insufficient REDO log file space for the cluster to start.
+ (Bug #25801)
</para>
</listitem>
<listitem>
<para>
- <emphasis role="bold">Disk Data</emphasis>: 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. (Bug #24166)
+ <emphasis role="bold">Disk Data</emphasis>: 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>
- <emphasis role="bold">NDB API</emphasis>: Invoking the
- <literal>NdbTransaction::execute()</literal> method using
- execution type <literal>Commit</literal> and abort option
- <literal>AO_IgnoreError</literal> could lead to a crash of
- the transaction coordinator (<literal>DBTC</literal>). (Bug
- #25090)
+ A memory allocation failure in the cluster Subscription
+ Manager could cause the cluster to crash. (Bug #25239)
</para>
</listitem>
<listitem>
<para>
- <emphasis role="bold">NDB API</emphasis>: Due to an error in
- the computation of table fragment arrays, some transactions
- might not be executed from the correct starting point. (Bug
- #24914)
+ The <errorname>InvalidUndoBufferSize</errorname> error used
+ the same error code (<errorcode>763</errorcode>) as the
+ <errorname>IncompatibleVersions</errorname> error.
+ <errorname>InvalidUndoBufferSize</errorname> now uses its
+ own error code (<errorcode>779</errorcode>). (Bug #26490)
</para>
</listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Disk Data</emphasis>: 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>
+ The failure of a data node when restarting it with
+ <option>--initial</option> could lead to failures of
+ subsequent data node restarts. (Bug #26481)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Takeover for local checkpointing due to multiple failures of
+ master nodes was sometimes handled incorrectly. (Bug #26457)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>LockPagesInMemory</literal> parameter was not
+ read until after distributed communication had already
+ started between cluster nodes. When the value of this
+ parameter was <literal>1</literal>, this could sometimes
+ result in data node failure due to missed heartbeats. (Bug
+ #26454)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Under some circumstances, following the restart of a
+ management node, all cluster data nodes would connect to it
+ normally, but some of them subsequently failed to log any
+ events to the management node. (Bug #26293)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An error was produced when <literal>SHOW TABLE
+ STATUS</literal> was used on an <literal>NDB</literal> table
+ that had no <literal>AUTO_INCREMENT</literal> column. (Bug
+ #21033)
+ </para>
+
+ <note>
+ <para>
+ This improves on and supersedes an earlier fix that was
+ made for this issue in MySQL 5.1.12.
+ </para>
+ </note>
+ </listitem>
+
</itemizedlist>
</section>
+ <section id="news-5-1-15-ndb-6-1-2">
+
+ <title>Changes in release MySQL 5.1.15-ndb-6.1.2-beta (07 February 2007)</title>
+
+ <para role="release-level">
+ This is a new Beta development release, fixing a recently
+ discovered bug.
+ </para>
+
+ <para>
+ Like all releases for MySQL ¤t-series-mccge;, 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"/>. 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.2"/>.
+ The file
+ <filename>mysqlcom-5.1.15-ndb-6.1.2-telco.tar.gz</filename> in
+ this directory contains the complete source archive.
+ </para>
+
+ <para>
+ Like all releases for MySQL ¤t-series-mccge;, 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"/>. 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.2"/>.
+ The file
+ <filename>mysqlcom-5.1.15-ndb-6.1.2-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 Beta release is a hotfix release, made to resolve a single
+ critical issue which occurred in MySQL 5.1.15/NDB-6.1.1-beta. It
+ incorporates all bugfixes and feature changes made in MySQL
+ 5.1.14/NDB-6.1.0 and MySQL 5.1.15/NDB-6.1.1. This version also
+ incorporates all bugfixes and feature changes which were added
+ in the mainline 5.1.15 release; information about these can be
+ found in <xref linkend="news-5-1-15"/>.
+ </para>
+
+ <important>
+ <formalpara>
+
+ <title>Upgrading to MySQL 5.1.15/NDB-6.1.2 from a previous release</title>
+
+ <para>
+ This release is not binary compatible with any previous
+ releases. 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. You must
+ shut down the cluster, replace all binaries, then
+ restart the cluster.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ You must recompile any MySQL Cluster API applications
+ used with a previous version of MySQL Cluster. This
+ includes all NDB API and MGM API applications.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ </formalpara>
+ </important>
+
+ <para>
+ This release fixes a single critical bug:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Using node IDs greater than 48 could sometimes lead to
+ incorrect memory access and a subsequent forced shutdown of
+ the cluster. (Bug #26267)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="news-5-1-15-ndb-6-1-1">
+
+ <title>Changes in release MySQL 5.1.15-ndb-6.1.1-beta (01 February 2007)</title>
+
+ <para role="release-level">
+ This is a new Beta development release, fixing recently
+ discovered bugs.
+ </para>
+
+ <para>
+ Like all releases for MySQL ¤t-series-mccge;, 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"/>. 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.1"/>.
+ The file
+ <filename>mysqlcom-5.1.15-ndb-6.1.1-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 section documents all changes and bug fixes that have been
+ applied in this Beta release since the release of MySQL Cluster
+ 5.1.14/NDB-6.1.0. This version also incorporates all bugfixes
+ and feature changes which were added in the mainline 5.1.15
+ release; information about these can be found in
+ <xref linkend="news-5-1-15"/>.
+ </para>
+
+ <important>
+ <formalpara>
+
+ <title>Upgrading to MySQL 5.1.15/NDB-6.1.1 from a previous release</title>
+
+ <para>
+ This release is not binary compatible with any previous
+ releases. This means that:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ You cannot perform an online upgrade to this release
+ from either MySQL 5.1.14/NDB-6.1.0 or from any of the
+ mainline MySQL 5.1 releases. You must shut down the
+ cluster, replace all binaries, then restart the
+ cluster.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ You must recompile any MySQL Cluster API applications
+ used with a previous version of MySQL Cluster. This
+ includes all NDB API and MGM API applications.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ </formalpara>
+ </important>
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <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.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>LockPagesInMainMemory</literal> configuration
+ parameter has changed its type and possible values. For more
+ information, see
+ <literal><link linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory">LockPagesInMainMemory</link></literal>.
+ (Bug #25686)
+ </para>
+
+ <para>
+ <emphasis role="bold">Important</emphasis>: The values
+ <literal>true</literal> and <literal>false</literal> are no
+ longer accepted for this parameter. If you were using this
+ parameter and had it set to <literal>false</literal> in a
+ previous release, you must change it to
+ <literal>0</literal>. If you had this parameter set to
+ <literal>true</literal>, you should instead use
+ <literal>1</literal> to obtain the same behavior as
+ previously, or <literal>2</literal> to take advantage of new
+ functionality introduced with this release described in the
+ section cited above.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ A memory leak could cause problems during a node or cluster
+ shutdown or failure. (Bug #25997)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Cluster Replication</emphasis>:
+ Certain errors in replication setups could lead to
+ subsequent node failures. (Bug #25755)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Hosts in clusters with a large number of nodes could
+ experience excessive CPU usage while obtaining configuration
+ data. (Bug #25711)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When stopping and restarting multiple data nodes, the last
+ node to be restarted would sometimes hang in Phase 100. (Bug
+ #19645)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Cluster APIs</emphasis> /
+ <emphasis role="bold">Disk Data</emphasis>: A delete and a
+ read peformed in the same operation could cause one or more
+ of the cluster's data nodes to crash. This could occur when
+ the operation affected more than 5 columns concurrently, or
+ when one or more of the columns was of the VARCHAR type and
+ was stored on disk. (Bug #25794)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An element could sometimes be inserted twice into the hash
+ table, causing a data node to crash. (Bug #25286)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
</section>
<section id="news-5-1-14">
<title>Changes in release 5.1.14 (Not released separately for MySQL
- ¤t-series;)</title>
+ ¤t-series-mccge;)</title>
<para role="release-level">
This is a new Beta development release, fixing recently discovered
@@ -4913,6 +4703,216 @@
</section>
+ <section id="news-5-1-14-cge">
+
+ <title>Changes in MySQL 5.1.14 Carrier Grade Edition</title>
+
+ <para>
+ This section contains change history information for
+ ¤t-series-mccge; releases based on MySQL 5.1.14.
+ </para>
+
+ <section id="news-5-1-14-ndb-6-1-0">
+
+ <title>Changes in release MySQL 5.1.14-ndb-6.1.0-beta (20 December 2006)</title>
+
+ <para role="release-level">
+ This is a new Beta development release, fixing recently
+ discovered bugs.
+ </para>
+
+ <para>
+ Like all releases for MySQL ¤t-series-mccge;, 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"/>. 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.14-ndb-6.1.0"/>.
+ There are two version of the source archive in this directory:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <filename>mysql-5.1.14-ndb-6.1.0-telco.tar.gz</filename>:
+ This is the GPL version. Customers who are using MySQL
+ ¤t-series-mccge; under a commercial licence must
+ <emphasis>not</emphasis> use this version in a production
+ setting.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>mysqlcom-5.1.14-ndb-6.1.0-telco.tar.gz</filename>:
+ This is the commercial version. Customers who are using
+ MySQL ¤t-series-mccge; under a commercial licence
+ <emphasis>must</emphasis> use this version in any setting
+ covered under their licence agreement with MySQL AB.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </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 section documents all changes and bug fixes that have been
+ applied in this Beta release since MySQL ¤t-series-mccge;
+ diverged from MySQL 5.1.14 standard.
+ </para>
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Support was added for a new
+ <literal>MemReportFrequency</literal> configuration
+ parameter that provides for periodic reports of memory
+ usage. See
+ <xref linkend="mysql-cluster-config-params-mgm"/>, for
+ information about using this parameter.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">NDB API</emphasis>: A unique index
+ lookup on a non-existent tuple could lead to a data node
+ timeout (error 4012). (Bug #25059)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>SELECT</literal> statement performing a primary
+ key lookup on a table with a <literal>VARCHAR</literal>
+ primary key, and where a <literal>BLOB</literal> or
+ <literal>TEXT</literal> column was among the columns
+ selected, would produce an empty result set. (Bug #19956)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">NDB API</emphasis>: 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. (Bug #24949)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Disk Data</emphasis>: A
+ <literal>MEDIUMTEXT</literal> column of a Disk Data table
+ was stored in memory rather than on disk, even if the column
+ was not indexed. (Bug #25001)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Under certain rare circumstances, local checkpoints were not
+ performed properly, leading to an inability to restart one
+ or more data nodes. (Bug #24664)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Disk Data</emphasis>: Performing a
+ node restart with a newly dropped Disk Data table could lead
+ to failure of the node during the restart. (Bug #24917)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Disk Data</emphasis>: Repeated
+ <literal>CREATE</literal>, <literal>DROP</literal>, or
+ <literal>TRUNCATE</literal> in various combinations with
+ system restarts between these operations could lead to the
+ eventual failure of a system restart. (Bug #21948)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Disk Data</emphasis>: Extents that
+ should have been available for re-use following a DROP TABLE
+ operation were not actually made available again until after
+ the cluster performed a local checkpoint. (Bug #17605)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When a data node was shut down using the management client
+ <literal>STOP</literal> command, a connection event
+ (<literal>NDB_LE_Connected</literal>) was logged instead of
+ a disconnection event
+ (<literal>NDB_LE_Disconnected</literal>). (Bug #22773)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Disk Data</emphasis>: 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. (Bug #24166)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">NDB API</emphasis>: Invoking the
+ <literal>NdbTransaction::execute()</literal> method using
+ execution type <literal>Commit</literal> and abort option
+ <literal>AO_IgnoreError</literal> could lead to a crash of
+ the transaction coordinator (<literal>DBTC</literal>). (Bug
+ #25090)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">NDB API</emphasis>: Due to an error in
+ the computation of table fragment arrays, some transactions
+ might not be executed from the correct starting point. (Bug
+ #24914)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ </section>
+
<section id="news-5-1-13">
<title>Changes in release 5.1.13 (Not released)</title>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6174 - trunk/refman-5.1 | jon | 25 Apr |
