Author: jstephens
Date: 2008-05-22 20:18:17 +0200 (Thu, 22 May 2008)
New Revision: 10824
Log:
Reverted rev 10655 (conversion of NDB-6.1 changelog to static format)
(Yes, MC, it *was* a stupid idea...)
Modified:
trunk/dynamic-docs/changelog/mysqld-versions.xml
trunk/it/refman-5.1/Makefile.depends
trunk/it/refman-5.1/mysql-cluster-news-core.xml
trunk/pt/refman-5.1/Makefile.depends
trunk/pt/refman-5.1/mysql-cluster-news-core.xml
trunk/refman-5.1-maria/Makefile.depends
trunk/refman-5.1/Makefile.depends
trunk/refman-5.1/mysql-cluster-news-core.xml
Modified: trunk/dynamic-docs/changelog/mysqld-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-versions.xml 2008-05-22 18:17:36 UTC (rev 10823)
+++ trunk/dynamic-docs/changelog/mysqld-versions.xml 2008-05-22 18:18:17 UTC (rev 10824)
Changed blocks: 1, Lines Added: 24, Lines Deleted: 0; 2528 bytes
@@ -81,7 +81,31 @@
<versionentry ver="5.1.16" reldate="26 February 2007"/>
<versionentry ver="5.1.16" subver="ndb-6.2.0" reldate="03 March 2007"/>
<versionentry ver="5.1.15" reldate="25 January 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.23" reldate="20 November 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.22" reldate="19 October 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.21" reldate="01 October 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.20" reldate="14 September 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.19" reldate="01 August 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.18" reldate="Not released"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.17" reldate="03 July 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.16" reldate="29 June 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.15" reldate="20 June 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.14" reldate="19 June 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.13" reldate="15 June 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.12" reldate="13 June 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.11" reldate="06 June 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.10" reldate="30 May 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.9" reldate="24 May 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.8" reldate="05 May 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.7" reldate="05 May 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.6" reldate="Not released"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.5" reldate="15 March 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.4" reldate="09 March 2007)"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.3" reldate="25 February 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.2" reldate="07 February 2007"/>
+ <versionentry ver="5.1.15" subver="ndb-6.1.1" reldate="01 February 2007"/>
<versionentry ver="5.1.14" reldate="05 December 2006"/>
+ <versionentry ver="5.1.14" subver="ndb-6.1.0" reldate="20 December 2006"/>
<versionentry ver="5.1.13" reldate="Not released"/>
<versionentry ver="5.1.12" reldate="24 October 2006"/>
<versionentry ver="5.1.11" reldate="26 May 2006"/>
Modified: trunk/it/refman-5.1/Makefile.depends
===================================================================
--- trunk/it/refman-5.1/Makefile.depends 2008-05-22 18:17:36 UTC (rev 10823)
+++ trunk/it/refman-5.1/Makefile.depends 2008-05-22 18:18:17 UTC (rev 10824)
Changed blocks: 5, Lines Added: 5, Lines Deleted: 0; 2569 bytes
@@ -735,6 +735,7 @@
../../refman-5.1/metadata/mysql-cluster-news-core.idmap \
../../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../../refman-5.1/metadata/mysql-cluster-process-management.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../../refman-5.1/metadata/mysql-cluster-replication.idmap \
../../refman-5.1/metadata/mysql-cluster-upgrade-downgrade.idmap \
../../refman-5.1/metadata/mysql-cluster-utilities.idmap \
@@ -1790,6 +1791,7 @@
../../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../../refman-5.1/metadata/mysql-cluster-overview.idmap \
../../refman-5.1/metadata/mysql-cluster-process-management.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../../refman-5.1/metadata/mysql-cluster-replication.idmap \
../../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../../refman-5.1/metadata/mysql-cluster-security.idmap \
@@ -2169,6 +2171,7 @@
../../refman-5.1/metadata/dba-core.idmap \
../../refman-5.1/metadata/mysql-cluster-backup.idmap \
../../refman-5.1/metadata/mysql-cluster-multi-computer.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../../refman-5.1/metadata/mysql-cluster-replication.idmap \
../../refman-5.1/metadata/mysql-cluster-upgrade-downgrade.idmap \
../../refman-5.1/metadata/news-5.1-core.idmap \
@@ -2205,6 +2208,7 @@
../../refman-5.1/metadata/mysql-cluster-news-core.idmap \
../../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../../refman-5.1/metadata/mysql-cluster-process-management.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../../refman-5.1/metadata/mysql-cluster-replication.idmap \
../../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../../refman-5.1/metadata/partitioning.idmap \
@@ -2390,6 +2394,7 @@
../../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../../refman-5.1/metadata/mysql-cluster-overview.idmap \
../../refman-5.1/metadata/mysql-cluster-process-management.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../../refman-5.1/metadata/mysql-cluster-replication.idmap \
../../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../../refman-5.1/metadata/mysql-cluster-security.idmap \
Modified: trunk/it/refman-5.1/mysql-cluster-news-core.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-news-core.xml 2008-05-22 18:17:36 UTC (rev 10823)
+++ trunk/it/refman-5.1/mysql-cluster-news-core.xml 2008-05-22 18:18:17 UTC (rev 10824)
Changed blocks: 25, Lines Added: 48, Lines Deleted: 1515; 59936 bytes
@@ -1436,7 +1436,7 @@
<section id="mysql-cluster-news-5-1-15-ndb-6-1-23">
- <title>Changes in MySQL 5.1.15-ndb-6.1.23 (20 November 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.23:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating a bugfix
@@ -1472,34 +1472,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A node
- failure during a local checkpoint could lead to a subsequent
- failure of the cluster during a system restart. (Bug #31257)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A cluster restart could sometimes fail due to an issue with
- table IDs. (Bug #30975)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-22">
- <title>Changes in MySQL 5.1.15-ndb-6.1.22 (19 October 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.22:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating a bugfix
@@ -1534,34 +1513,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A node
- failure during a local checkpoint could lead to a subsequent
- failure of the cluster during a system restart. (Bug #31257)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A cluster restart could sometimes fail due to an issue with
- table IDs. (Bug #30975)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-21">
- <title>Changes in MySQL 5.1.15-ndb-6.1.21 (01 October 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.21:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating recent
@@ -1596,34 +1554,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A node
- failure during a local checkpoint could lead to a subsequent
- failure of the cluster during a system restart. (Bug #31257)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A cluster restart could sometimes fail due to an issue with
- table IDs. (Bug #30975)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-20">
- <title>Changes in MySQL 5.1.15-ndb-6.1.20 (14 September 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.20:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating a bugfix
@@ -1657,34 +1594,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A node
- failure during a local checkpoint could lead to a subsequent
- failure of the cluster during a system restart. (Bug #31257)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A cluster restart could sometimes fail due to an issue with
- table IDs. (Bug #30975)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-19">
- <title>Changes in MySQL 5.1.15-ndb-6.1.19 (01 August 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.19:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating recent
@@ -1718,38 +1634,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.19:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Whenever a
- TCP send buffer is over 80% full, temporary error 1218
- (<errortext>Send Buffers overloaded in NDB
- kernel</errortext>) is now returned. See
- <link linkend="mysql-cluster-param-tcp-definition-sendbuffermemory">SendBufferMemory</link>
- for more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- An <literal>INFO</literal> event is now sent if the time
- between global checkpoints is excessive, or if <literal>DUMP
- 7901</literal> is issued in the management client.
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-18">
- <title>Changes in MySQL 5.1.15-ndb-6.1.18 (Not released)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.18:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -1780,52 +1671,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.18:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: When
- restarting a data node, queries could hang during that
- node's start phase 5, and continue only after the node had
- entered phase 6. (Bug #29364)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Disk data
- meta-information that existed in <command>ndbd</command>
- might not be visible to <command>mysqld</command>. (Bug
- #28720)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: The number of
- free extents was incorrectly reported for some tablespaces.
- (Bug #28642)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Storage engine error conditions in row-based replication
- were not correctly reported to the user. (Bug #29570)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-17">
- <title>Changes in MySQL 5.1.15-ndb-6.1.17 (03 July 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.17:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -1858,44 +1710,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.17:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- Batching of updates on cluster replication slaves, enabled
- using the <option>--slave-allow-batching</option> option for
- <command>mysqld</command>.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Replica redo
- logs were inconsistently handled during a system restart.
- (Bug #29354)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-16">
- <title>Changes in MySQL 5.1.15-ndb-6.1.16 (29 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.16:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -1927,63 +1748,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.16:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: When a node
- failed to respond to a <literal>COPY_GCI</literal> signal as
- part of a global checkpoint, the master node was killed
- instead of the node that actually failed. (Bug #29331)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: An invalid
- comparison made during <literal>REDO</literal> validation
- that could lead to an <errortext>Error while reading REDO
- log</errortext> condition. (Bug #29118)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: The wrong
- data pages were sometimes invalidated following a global
- checkpoint. (Bug #29067)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: If at least
- 2 files were involved in <literal>REDO</literal>
- invalidation, then file 0 of page 0 was not updated and so
- pointed to an invalid part of the redo log. (Bug #29057)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: When dropping a
- page, the stack's bottom entry could sometime be left
- <quote>cold</quote> rather than <quote>hot</quote>,
- violating the rules for stack pruning. (Bug #29176)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-15">
- <title>Changes in MySQL 5.1.15-ndb-6.1.15 (20 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.15:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing a recently
@@ -2015,27 +1786,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.15:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Memory
- corruption could occur due to a problem in the
- <literal>DBTUP</literal> kernel block. (Bug #29229)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-14">
- <title>Changes in MySQL 5.1.15-ndb-6.1.14 (19 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.14:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating bugfixes
@@ -2066,31 +1823,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.14:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: In the event
- that two data nodes in the same node group and participating
- in a GCP crashed before they had written their respective
- <filename>P0.sysfile</filename> files,
- <literal>QMGR</literal> could refuse to start, issuing an
- invalid <errortext>Insufficient nodes for
- restart</errortext> error instead. (Bug #29167)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-13">
- <title>Changes in MySQL 5.1.15-ndb-6.1.13 (15 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.13:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2122,27 +1861,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.13:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- Read ahead was implemented for backups of Disk Data tables,
- resulting in a 10 to 15% increase in backup speed of Disk
- Data tables. (Bug #29099)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-12">
- <title>Changes in MySQL 5.1.15-ndb-6.1.12 (13 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.12:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2173,54 +1898,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.12:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: New cluster
- management client <literal>DUMP</literal> commands were
- added to aid in tracking transactions, scan operations, and
- locks. See
- <xref linkend="ndb-internals-dump-command-2350"></xref>,
- <xref linkend="ndb-internals-dump-command-2352"></xref>, and
- <xref linkend="ndb-internals-dump-command-2550"></xref>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Backup dump output was extended to provide more information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: It is now
- possible to set the maximum size of the allocation unit for
- table memory using the <literal>MaxAllocate</literal>
- configuration parameter. (Bug #29044)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-11">
- <title>Changes in MySQL 5.1.15-ndb-6.1.11 (06 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.11:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2251,85 +1935,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.11:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Important Change</emphasis>:
- <emphasis role="bold">MySQL Cluster</emphasis>: The
- <literal>TimeBetweenWatchdogCheckInitial</literal>
- configuration parameter was added to allow setting of a
- separate watchdog timeout for memory allocation during
- startup of the data nodes. See
- <xref linkend="mysql-cluster-ndbd-definition"></xref>, for
- more information. (Bug #28899)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A new
- configuration parameter <literal>ODirect</literal> causes
- <literal>NDB</literal> to attempt using
- <literal>O_DIRECT</literal> writes for LCP, backups, and
- redo logs, often lowering CPU usage.
- </para>
- </listitem>
-
- <listitem>
- <para>
- It is now possible to set the size of redo log files
- (fragment log files) using the
- <literal>FragmentLogFileSize</literal> configuration
- parameter.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Having large
- amounts of memory locked caused swapping to disk. (Bug
- #28751)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: LCP files
- were not removed following an initial system restart. (Bug
- #28726)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Repeated
- <literal>INSERT</literal> and <literal>DELETE</literal>
- operations on a Disk Data table having one or more large
- <literal>VARCHAR</literal> columns could cause data nodes to
- fail. (Bug #20612)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-10">
- <title>Changes in MySQL 5.1.15-ndb-6.1.10 (30 May 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.10:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2359,110 +1971,13 @@
(see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.10:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A new
- <literal>times</literal> printout was added in the
- <command>ndbd</command> watchdog thread.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Some
- unneeded printouts in the <command>ndbd</command> out file
- were removed.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The names of some log and other files were changed to avoid
- issues with the <command>tar</command> command's
- 99-character filename limit.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A regression
- in the heartbeat monitoring code could lead to node failure
- under high load. This issue affected MySQL 5.1.19 and MySQL
- 5.1.15-ndb-6.1.10 only. (Bug #28783)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A corrupt
- schema file could cause a <errortext>File already
- open</errortext> error. (Bug #28770)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Setting
- <literal>InitialNoOpenFiles</literal> equal to
- <literal>MaxNoOfOpenFiles</literal> caused an error. This
- was due to the fact that the actual value of
- <literal>MaxNoOfOpenFiles</literal> as used by the cluster
- was offset by 1 from the value set in
- <filename>config.ini</filename>. (Bug #28749)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A race
- condition could result when non-master nodes (in addition to
- the master node) tried to update active status due to a
- local checkpoint (that is, between
- <literal>NODE_FAILREP</literal> and
- <literal>COPY_GCIREQ</literal> events). Now only the master
- updates the active status. (Bug #28717)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A fast
- global checkpoint under high load with high usage of the
- redo buffer caused data nodes to fail. (Bug #28653)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: When loading
- data into a cluster following a version upgrade, the data
- nodes could forcibly shut down due to page and buffer
- management failures (that is, <literal>ndbrequire</literal>
- failures in <literal>PGMAN</literal>). (Bug #28525)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-9">
- <title>Changes in MySQL 5.1.15-ndb-6.1.9 (24 May 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.9:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2482,36 +1997,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.9:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: When an API
- node sent more than 1024 signals in a single batch,
- <literal>NDB</literal> would process only the first 1024 of
- these, and then hang. (Bug #28443)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: The cluster
- backup process scanned in <literal>ACC</literal> index
- order, which had bad effects for disk data. (Bug #28593)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-8">
- <title>Changes in MySQL 5.1.15-ndb-6.1.8 (05 May 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.8:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2540,63 +2032,13 @@
(see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.8:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Local
- checkpoint files relating to dropped <literal>NDB</literal>
- tables were not removed. (Bug #28348)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Repeated
- insertion of data generated by <command>mysqldump</command>
- into <literal>NDB</literal> tables could eventually lead to
- failure of the cluster. (Bug #27437)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Extremely large
- inserts into Disk Data tables could lead to data node
- failure in some circumstances. (Bug #27942)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster API</emphasis>: In a
- multi-operation transaction, a delete operation followed by
- the insertion of an implicit <literal>NULL</literal> failed
- to overwrite an existing value. (Bug #20535)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Setting <literal>MaxNoOfTables</literal> very low and
- relative to <literal>DataMemory</literal> caused
- <errortext>Out of memory in Ndb Kernel</errortext> errors
- when inserting relatively small amounts of data into NDB
- tables. (Bug #24173)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-7">
- <title>Changes in MySQL 5.1.15-ndb-6.1.7 (05 May 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.7:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2658,206 +2100,13 @@
</para>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.7:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- <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
- &mccge-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"></xref>,
- for additional information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: The cluster
- waited 30 seconds instead of 30 milliseconds before reading
- table statistics. (Bug #28093)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Under
- certain rare circumstances, <command>ndbd</command> could
- get caught in an infinite loop when one transaction took a
- read lock and then a second transaction attempted to obtain
- a write lock on the same tuple in the lock queue. (Bug
- #28073)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Under some
- circumstances, a node restart could fail to update the
- Global Checkpoint Index (GCI). (Bug #28023)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Under
- certain rare circumstances performing a <literal>DROP
- TABLE</literal> or <literal>TRUNCATE</literal> on an
- <literal>NDB</literal> table could cause a node failure or
- forced cluster shutdown. (Bug #27581)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Memory usage
- of a <command>mysqld</command> process grew even while idle.
- (Bug #27560)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Performing a
- delete followed by an insert during a local checkpoint could
- cause a <errortext>Rowid already allocated</errortext>
- error. (Bug #27205)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Replication</emphasis>: Some queries
- that updated multiple tables were not backed up correctly.
- (Bug #27748)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- <emphasis role="bold">Disk Data</emphasis>: An issue with
- replication of Disk Data tables could in some cases lead to
- node failure. (Bug #28161)
- </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>
- <emphasis role="bold">Disk Data</emphasis>: When restarting
- a data node following the creation of a large number of Disk
- Data objects (approximately 200 such objects), the cluster
- could not assign a node ID to the restarting node. (Bug
- #25741)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Changing a
- column specification or issuing a
- <literal>TRUNCATE</literal> statement on a Disk Data table
- caused the table to become an in-memory table.
- </para>
-
- <para>
- This fix supersedes an incomplete fix that was made for this
- issue in MySQL 5.1.15. (Bug #24667, Bug #25296)
- </para>
- </listitem>
-
- <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 #27728)
- </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">Cluster API</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>
- An <literal>INSERT</literal> followed by a delete
- <literal>DELETE</literal> on the same <literal>NDB</literal>
- table caused a memory leak. (Bug #27756)
- </para>
-
- <para>
- This regression was introduced by Bug #20612
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqldump</command> could not dump log tables. (Bug
- #26121)
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <option>--with-readline</option> option for
- <command>configure</command> did not work for commercial
- source packages, but no error message was printed to that
- effect. Now a message is printed. (Bug #25530)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-6">
- <title>Changes in MySQL 5.1.15-ndb-6.1.6 (Not released)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.6:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2885,164 +2134,13 @@
(see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.6:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- <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
- &mccge-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"></xref>,
- for additional information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: It was not
- possible to set <literal>LockPagesInMainMemory</literal>
- equal to <literal>0</literal>. (Bug #27291)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>:
- <command>mysqld</command> could crash shortly after a data
- node failure following certain DML operations. (Bug #27169)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: The failure
- of a data node while restarting could cause other data nodes
- to hang or crash. (Bug #27003)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>:
- <command>mysqld</command> processes would sometimes crash
- under high load.
- </para>
-
- <note>
- <para>
- This fix improves on and replaces a fix for this bug that
- was made in MySQL 5.1.15-ndb-6.1.5.
- </para>
- </note>
-
- <para>
- (Bug #26825)
- </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>
- <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 API</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 API</emphasis>: A delete
- operation using a scan followed by an insert using a scan
- could cause a data node to fail. (Bug #27203)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-5">
- <title>Changes in MySQL 5.1.15-ndb-6.1.5 (15 March 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.5:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3114,92 +2212,13 @@
</formalpara>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.5:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- <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
- &mccge-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"></xref>,
- for additional information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Creating a
- table on one SQL node while in single user mode caused other
- SQL nodes to crash. (Bug #26997)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>:
- <command>mysqld</command> processes would sometimes crash
- under high load.
- </para>
-
- <note>
- <para>
- This fix was reverted in MySQL 5.1.15-ndb-6.1.6.
- </para>
- </note>
-
- <para>
- (Bug #26825)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <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="mysql-cluster-news-5-1-15-ndb-6-1-4">
- <title>Changes in MySQL 5.1.15-ndb-6.1.4 (09 March 2007))</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.4:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3268,125 +2287,13 @@
</formalpara>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.4:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: An
- <option>--ndb-wait-connected</option> 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 accepting client
- connections. See
- <link linkend="option_mysqld_ndb_wait_connected">here</link>,
- for more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster API</emphasis>: It is now
- possible to specify the transaction coordinator when
- starting a transaction. See
- <xref linkend="class-ndb-starttransaction"></xref>, for more
- information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster 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:
-
- <itemizedlist>
-
- <listitem>
- <para>
- <literal>lock_ndb_objects()</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>get_next_ndb_object()</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>unlock_ndb_objects()</literal>
- </para>
- </listitem>
-
- </itemizedlist>
-
- For more information about these methods and their use, see
- <xref linkend="class-ndb-cluster-connection-get-next-ndb-object"></xref>,
- in the MySQL Cluster API Guide.
- </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:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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 regression was introduced by Bug #14612
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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="mysql-cluster-news-5-1-15-ndb-6-1-3">
- <title>Changes in MySQL 5.1.15-ndb-6.1.3 (25 February 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.3:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3463,180 +2370,13 @@
</formalpara>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.3:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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"></xref>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster API</emphasis>: A new
- <literal>listEvents()</literal> method has been added to the
- <literal>Dictionary</literal> class. See
- <xref linkend="class-dictionary-listevents"></xref>, for
- more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <command>ndb_show_tables</command> utility now displays
- information about table events. See
- <xref linkend="mysql-cluster-utilities-ndb-show-tables"></xref>,
- for more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- It is now possible to disable arbitration by setting
- <literal>ArbitrationRank=0</literal> on all management and
- SQL nodes.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: Takeover for
- local checkpointing due to multiple failures of master nodes
- was sometimes incorrectly handled. (Bug #26457)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: The
- <literal>LockPagesInMainMemory</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>
- <emphasis role="bold">MySQL Cluster</emphasis>: Under some
- circumstances, following the restart of a management node,
- all 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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">MySQL Cluster</emphasis>: A memory
- allocation failure in <literal>SUMA</literal> (the cluster
- Subscription Manager) could cause the cluster to crash. (Bug
- #25239)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: The message
- <errortext>Error 0 in readAutoIncrementValue(): no
- Error</errortext> was written to the error log whenever
- <literal>SHOW TABLE STATUS</literal> was performed on a
- Cluster table that did not have an
- <literal>AUTO_INCREMENT</literal> column.
- </para>
-
- <note>
- <para>
- This improves on and supersedes an earlier fix that was
- made for this issue in MySQL 5.1.12.
- </para>
- </note>
-
- <para>
- (Bug #21033)
- </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>
- <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>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-2">
- <title>Changes in MySQL 5.1.15-ndb-6.1.2 (07 February 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.2:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing a recently
@@ -3710,28 +2450,13 @@
</formalpara>
</important>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.2:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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="mysql-cluster-news-5-1-15-ndb-6-1-1">
- <title>Changes in MySQL 5.1.15-ndb-6.1.1 (01 February 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.1:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3792,63 +2517,13 @@
</formalpara>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.1:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A single
- cluster can now support up to 255 API nodes, including MySQL
- servers acting as SQL nodes. See
- <xref linkend="mysql-cluster-limitations-exclusive-to-cluster"></xref>,
- for more information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster API</emphasis>:
- <emphasis role="bold">Disk Data</emphasis>: A delete and a
- read performed in the same operation could cause one or more
- 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 <literal>VARCHAR</literal>
- type and was stored on disk. (Bug #25794)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A memory leak could cause problems during a node or cluster
- shutdown or failure. (Bug #25997)
- </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 id="mysql-cluster-news-5-1-14-ndb-6-1-0">
- <title>Changes in MySQL 5.1.14-ndb-6.1.0 (20 December 2006)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.14-ndb-6.1.0:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3871,150 +2546,8 @@
from MySQL 5.1.14 standard.
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.14-ndb-6.1.0:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A new
- configuration parameter
- <literal>MemReportFrequency</literal> allows for additional
- control of data node memory usage. Previously, only warnings
- at predetermined percentages of memory allocation were
- given; setting this parameter allows for that behavior to be
- overridden. For more information, see
- <xref linkend="mysql-cluster-ndbd-definition"></xref>.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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">MySQL Cluster</emphasis>:
- <literal>SELECT</literal> statements with a
- <literal>BLOB</literal> or <literal>TEXT</literal> column in
- the selected column list and a <literal>WHERE</literal>
- condition including a primary key lookup on a
- <literal>VARCHAR</literal> primary key produced empty result
- sets. (Bug #19956)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>:
- <literal>MEDIUMTEXT</literal> columns of Disk Data tables
- were stored in memory rather than on disk, even if the
- columns were not indexed. (Bug #25001)
- </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>: 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">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
- <literal>DROP TABLE</literal> operation were not actually
- made available again until after the cluster had performed a
- local checkpoint. (Bug #17605)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster 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">Cluster 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>
- <emphasis role="bold">Cluster 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">Cluster API</emphasis>: Due to an
- error in the computation of table fragment arrays, some
- transactions were not executed from the correct starting
- point. (Bug #24914)
- </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>
-
- </itemizedlist>
-
</section>
</section>
Modified: trunk/pt/refman-5.1/Makefile.depends
===================================================================
--- trunk/pt/refman-5.1/Makefile.depends 2008-05-22 18:17:36 UTC (rev 10823)
+++ trunk/pt/refman-5.1/Makefile.depends 2008-05-22 18:18:17 UTC (rev 10824)
Changed blocks: 5, Lines Added: 5, Lines Deleted: 0; 2569 bytes
@@ -735,6 +735,7 @@
../../refman-5.1/metadata/mysql-cluster-news-core.idmap \
../../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../../refman-5.1/metadata/mysql-cluster-process-management.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../../refman-5.1/metadata/mysql-cluster-replication.idmap \
../../refman-5.1/metadata/mysql-cluster-upgrade-downgrade.idmap \
../../refman-5.1/metadata/mysql-cluster-utilities.idmap \
@@ -1790,6 +1791,7 @@
../../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../../refman-5.1/metadata/mysql-cluster-overview.idmap \
../../refman-5.1/metadata/mysql-cluster-process-management.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../../refman-5.1/metadata/mysql-cluster-replication.idmap \
../../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../../refman-5.1/metadata/mysql-cluster-security.idmap \
@@ -2169,6 +2171,7 @@
../../refman-5.1/metadata/dba-core.idmap \
../../refman-5.1/metadata/mysql-cluster-backup.idmap \
../../refman-5.1/metadata/mysql-cluster-multi-computer.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../../refman-5.1/metadata/mysql-cluster-replication.idmap \
../../refman-5.1/metadata/mysql-cluster-upgrade-downgrade.idmap \
../../refman-5.1/metadata/news-5.1-core.idmap \
@@ -2205,6 +2208,7 @@
../../refman-5.1/metadata/mysql-cluster-news-core.idmap \
../../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../../refman-5.1/metadata/mysql-cluster-process-management.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../../refman-5.1/metadata/mysql-cluster-replication.idmap \
../../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../../refman-5.1/metadata/partitioning.idmap \
@@ -2390,6 +2394,7 @@
../../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../../refman-5.1/metadata/mysql-cluster-overview.idmap \
../../refman-5.1/metadata/mysql-cluster-process-management.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../../refman-5.1/metadata/mysql-cluster-replication.idmap \
../../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../../refman-5.1/metadata/mysql-cluster-security.idmap \
Modified: trunk/pt/refman-5.1/mysql-cluster-news-core.xml
===================================================================
--- trunk/pt/refman-5.1/mysql-cluster-news-core.xml 2008-05-22 18:17:36 UTC (rev 10823)
+++ trunk/pt/refman-5.1/mysql-cluster-news-core.xml 2008-05-22 18:18:17 UTC (rev 10824)
Changed blocks: 25, Lines Added: 48, Lines Deleted: 1515; 59936 bytes
@@ -1436,7 +1436,7 @@
<section id="mysql-cluster-news-5-1-15-ndb-6-1-23">
- <title>Changes in MySQL 5.1.15-ndb-6.1.23 (20 November 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.23:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating a bugfix
@@ -1472,34 +1472,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A node
- failure during a local checkpoint could lead to a subsequent
- failure of the cluster during a system restart. (Bug #31257)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A cluster restart could sometimes fail due to an issue with
- table IDs. (Bug #30975)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-22">
- <title>Changes in MySQL 5.1.15-ndb-6.1.22 (19 October 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.22:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating a bugfix
@@ -1534,34 +1513,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A node
- failure during a local checkpoint could lead to a subsequent
- failure of the cluster during a system restart. (Bug #31257)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A cluster restart could sometimes fail due to an issue with
- table IDs. (Bug #30975)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-21">
- <title>Changes in MySQL 5.1.15-ndb-6.1.21 (01 October 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.21:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating recent
@@ -1596,34 +1554,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A node
- failure during a local checkpoint could lead to a subsequent
- failure of the cluster during a system restart. (Bug #31257)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A cluster restart could sometimes fail due to an issue with
- table IDs. (Bug #30975)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-20">
- <title>Changes in MySQL 5.1.15-ndb-6.1.20 (14 September 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.20:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating a bugfix
@@ -1657,34 +1594,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A node
- failure during a local checkpoint could lead to a subsequent
- failure of the cluster during a system restart. (Bug #31257)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A cluster restart could sometimes fail due to an issue with
- table IDs. (Bug #30975)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-19">
- <title>Changes in MySQL 5.1.15-ndb-6.1.19 (01 August 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.19:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating recent
@@ -1718,38 +1634,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.19:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Whenever a
- TCP send buffer is over 80% full, temporary error 1218
- (<errortext>Send Buffers overloaded in NDB
- kernel</errortext>) is now returned. See
- <link linkend="mysql-cluster-param-tcp-definition-sendbuffermemory">SendBufferMemory</link>
- for more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- An <literal>INFO</literal> event is now sent if the time
- between global checkpoints is excessive, or if <literal>DUMP
- 7901</literal> is issued in the management client.
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-18">
- <title>Changes in MySQL 5.1.15-ndb-6.1.18 (Not released)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.18:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -1780,52 +1671,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.18:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: When
- restarting a data node, queries could hang during that
- node's start phase 5, and continue only after the node had
- entered phase 6. (Bug #29364)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Disk data
- meta-information that existed in <command>ndbd</command>
- might not be visible to <command>mysqld</command>. (Bug
- #28720)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: The number of
- free extents was incorrectly reported for some tablespaces.
- (Bug #28642)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Storage engine error conditions in row-based replication
- were not correctly reported to the user. (Bug #29570)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-17">
- <title>Changes in MySQL 5.1.15-ndb-6.1.17 (03 July 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.17:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -1858,44 +1710,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.17:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- Batching of updates on cluster replication slaves, enabled
- using the <option>--slave-allow-batching</option> option for
- <command>mysqld</command>.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Replica redo
- logs were inconsistently handled during a system restart.
- (Bug #29354)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-16">
- <title>Changes in MySQL 5.1.15-ndb-6.1.16 (29 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.16:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -1927,63 +1748,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.16:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: When a node
- failed to respond to a <literal>COPY_GCI</literal> signal as
- part of a global checkpoint, the master node was killed
- instead of the node that actually failed. (Bug #29331)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: An invalid
- comparison made during <literal>REDO</literal> validation
- that could lead to an <errortext>Error while reading REDO
- log</errortext> condition. (Bug #29118)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: The wrong
- data pages were sometimes invalidated following a global
- checkpoint. (Bug #29067)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: If at least
- 2 files were involved in <literal>REDO</literal>
- invalidation, then file 0 of page 0 was not updated and so
- pointed to an invalid part of the redo log. (Bug #29057)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: When dropping a
- page, the stack's bottom entry could sometime be left
- <quote>cold</quote> rather than <quote>hot</quote>,
- violating the rules for stack pruning. (Bug #29176)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-15">
- <title>Changes in MySQL 5.1.15-ndb-6.1.15 (20 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.15:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing a recently
@@ -2015,27 +1786,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.15:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Memory
- corruption could occur due to a problem in the
- <literal>DBTUP</literal> kernel block. (Bug #29229)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-14">
- <title>Changes in MySQL 5.1.15-ndb-6.1.14 (19 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.14:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating bugfixes
@@ -2066,31 +1823,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.14:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: In the event
- that two data nodes in the same node group and participating
- in a GCP crashed before they had written their respective
- <filename>P0.sysfile</filename> files,
- <literal>QMGR</literal> could refuse to start, issuing an
- invalid <errortext>Insufficient nodes for
- restart</errortext> error instead. (Bug #29167)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-13">
- <title>Changes in MySQL 5.1.15-ndb-6.1.13 (15 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.13:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2122,27 +1861,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.13:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- Read ahead was implemented for backups of Disk Data tables,
- resulting in a 10 to 15% increase in backup speed of Disk
- Data tables. (Bug #29099)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-12">
- <title>Changes in MySQL 5.1.15-ndb-6.1.12 (13 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.12:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2173,54 +1898,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.12:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: New cluster
- management client <literal>DUMP</literal> commands were
- added to aid in tracking transactions, scan operations, and
- locks. See
- <xref linkend="ndb-internals-dump-command-2350"></xref>,
- <xref linkend="ndb-internals-dump-command-2352"></xref>, and
- <xref linkend="ndb-internals-dump-command-2550"></xref>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Backup dump output was extended to provide more information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: It is now
- possible to set the maximum size of the allocation unit for
- table memory using the <literal>MaxAllocate</literal>
- configuration parameter. (Bug #29044)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-11">
- <title>Changes in MySQL 5.1.15-ndb-6.1.11 (06 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.11:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2251,85 +1935,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.11:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Important Change</emphasis>:
- <emphasis role="bold">MySQL Cluster</emphasis>: The
- <literal>TimeBetweenWatchdogCheckInitial</literal>
- configuration parameter was added to allow setting of a
- separate watchdog timeout for memory allocation during
- startup of the data nodes. See
- <xref linkend="mysql-cluster-ndbd-definition"></xref>, for
- more information. (Bug #28899)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A new
- configuration parameter <literal>ODirect</literal> causes
- <literal>NDB</literal> to attempt using
- <literal>O_DIRECT</literal> writes for LCP, backups, and
- redo logs, often lowering CPU usage.
- </para>
- </listitem>
-
- <listitem>
- <para>
- It is now possible to set the size of redo log files
- (fragment log files) using the
- <literal>FragmentLogFileSize</literal> configuration
- parameter.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Having large
- amounts of memory locked caused swapping to disk. (Bug
- #28751)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: LCP files
- were not removed following an initial system restart. (Bug
- #28726)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Repeated
- <literal>INSERT</literal> and <literal>DELETE</literal>
- operations on a Disk Data table having one or more large
- <literal>VARCHAR</literal> columns could cause data nodes to
- fail. (Bug #20612)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-10">
- <title>Changes in MySQL 5.1.15-ndb-6.1.10 (30 May 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.10:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2359,110 +1971,13 @@
(see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.10:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A new
- <literal>times</literal> printout was added in the
- <command>ndbd</command> watchdog thread.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Some
- unneeded printouts in the <command>ndbd</command> out file
- were removed.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The names of some log and other files were changed to avoid
- issues with the <command>tar</command> command's
- 99-character filename limit.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A regression
- in the heartbeat monitoring code could lead to node failure
- under high load. This issue affected MySQL 5.1.19 and MySQL
- 5.1.15-ndb-6.1.10 only. (Bug #28783)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A corrupt
- schema file could cause a <errortext>File already
- open</errortext> error. (Bug #28770)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Setting
- <literal>InitialNoOpenFiles</literal> equal to
- <literal>MaxNoOfOpenFiles</literal> caused an error. This
- was due to the fact that the actual value of
- <literal>MaxNoOfOpenFiles</literal> as used by the cluster
- was offset by 1 from the value set in
- <filename>config.ini</filename>. (Bug #28749)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A race
- condition could result when non-master nodes (in addition to
- the master node) tried to update active status due to a
- local checkpoint (that is, between
- <literal>NODE_FAILREP</literal> and
- <literal>COPY_GCIREQ</literal> events). Now only the master
- updates the active status. (Bug #28717)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A fast
- global checkpoint under high load with high usage of the
- redo buffer caused data nodes to fail. (Bug #28653)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: When loading
- data into a cluster following a version upgrade, the data
- nodes could forcibly shut down due to page and buffer
- management failures (that is, <literal>ndbrequire</literal>
- failures in <literal>PGMAN</literal>). (Bug #28525)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-9">
- <title>Changes in MySQL 5.1.15-ndb-6.1.9 (24 May 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.9:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2482,36 +1997,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.9:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: When an API
- node sent more than 1024 signals in a single batch,
- <literal>NDB</literal> would process only the first 1024 of
- these, and then hang. (Bug #28443)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: The cluster
- backup process scanned in <literal>ACC</literal> index
- order, which had bad effects for disk data. (Bug #28593)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-8">
- <title>Changes in MySQL 5.1.15-ndb-6.1.8 (05 May 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.8:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2540,63 +2032,13 @@
(see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.8:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Local
- checkpoint files relating to dropped <literal>NDB</literal>
- tables were not removed. (Bug #28348)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Repeated
- insertion of data generated by <command>mysqldump</command>
- into <literal>NDB</literal> tables could eventually lead to
- failure of the cluster. (Bug #27437)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Extremely large
- inserts into Disk Data tables could lead to data node
- failure in some circumstances. (Bug #27942)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster API</emphasis>: In a
- multi-operation transaction, a delete operation followed by
- the insertion of an implicit <literal>NULL</literal> failed
- to overwrite an existing value. (Bug #20535)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Setting <literal>MaxNoOfTables</literal> very low and
- relative to <literal>DataMemory</literal> caused
- <errortext>Out of memory in Ndb Kernel</errortext> errors
- when inserting relatively small amounts of data into NDB
- tables. (Bug #24173)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-7">
- <title>Changes in MySQL 5.1.15-ndb-6.1.7 (05 May 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.7:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2658,206 +2100,13 @@
</para>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.7:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- <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
- &mccge-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"></xref>,
- for additional information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: The cluster
- waited 30 seconds instead of 30 milliseconds before reading
- table statistics. (Bug #28093)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Under
- certain rare circumstances, <command>ndbd</command> could
- get caught in an infinite loop when one transaction took a
- read lock and then a second transaction attempted to obtain
- a write lock on the same tuple in the lock queue. (Bug
- #28073)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Under some
- circumstances, a node restart could fail to update the
- Global Checkpoint Index (GCI). (Bug #28023)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Under
- certain rare circumstances performing a <literal>DROP
- TABLE</literal> or <literal>TRUNCATE</literal> on an
- <literal>NDB</literal> table could cause a node failure or
- forced cluster shutdown. (Bug #27581)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Memory usage
- of a <command>mysqld</command> process grew even while idle.
- (Bug #27560)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Performing a
- delete followed by an insert during a local checkpoint could
- cause a <errortext>Rowid already allocated</errortext>
- error. (Bug #27205)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Replication</emphasis>: Some queries
- that updated multiple tables were not backed up correctly.
- (Bug #27748)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- <emphasis role="bold">Disk Data</emphasis>: An issue with
- replication of Disk Data tables could in some cases lead to
- node failure. (Bug #28161)
- </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>
- <emphasis role="bold">Disk Data</emphasis>: When restarting
- a data node following the creation of a large number of Disk
- Data objects (approximately 200 such objects), the cluster
- could not assign a node ID to the restarting node. (Bug
- #25741)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Changing a
- column specification or issuing a
- <literal>TRUNCATE</literal> statement on a Disk Data table
- caused the table to become an in-memory table.
- </para>
-
- <para>
- This fix supersedes an incomplete fix that was made for this
- issue in MySQL 5.1.15. (Bug #24667, Bug #25296)
- </para>
- </listitem>
-
- <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 #27728)
- </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">Cluster API</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>
- An <literal>INSERT</literal> followed by a delete
- <literal>DELETE</literal> on the same <literal>NDB</literal>
- table caused a memory leak. (Bug #27756)
- </para>
-
- <para>
- This regression was introduced by Bug #20612
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqldump</command> could not dump log tables. (Bug
- #26121)
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <option>--with-readline</option> option for
- <command>configure</command> did not work for commercial
- source packages, but no error message was printed to that
- effect. Now a message is printed. (Bug #25530)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-6">
- <title>Changes in MySQL 5.1.15-ndb-6.1.6 (Not released)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.6:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2885,164 +2134,13 @@
(see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.6:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- <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
- &mccge-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"></xref>,
- for additional information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: It was not
- possible to set <literal>LockPagesInMainMemory</literal>
- equal to <literal>0</literal>. (Bug #27291)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>:
- <command>mysqld</command> could crash shortly after a data
- node failure following certain DML operations. (Bug #27169)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: The failure
- of a data node while restarting could cause other data nodes
- to hang or crash. (Bug #27003)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>:
- <command>mysqld</command> processes would sometimes crash
- under high load.
- </para>
-
- <note>
- <para>
- This fix improves on and replaces a fix for this bug that
- was made in MySQL 5.1.15-ndb-6.1.5.
- </para>
- </note>
-
- <para>
- (Bug #26825)
- </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>
- <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 API</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 API</emphasis>: A delete
- operation using a scan followed by an insert using a scan
- could cause a data node to fail. (Bug #27203)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-5">
- <title>Changes in MySQL 5.1.15-ndb-6.1.5 (15 March 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.5:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3114,92 +2212,13 @@
</formalpara>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.5:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- <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
- &mccge-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"></xref>,
- for additional information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Creating a
- table on one SQL node while in single user mode caused other
- SQL nodes to crash. (Bug #26997)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>:
- <command>mysqld</command> processes would sometimes crash
- under high load.
- </para>
-
- <note>
- <para>
- This fix was reverted in MySQL 5.1.15-ndb-6.1.6.
- </para>
- </note>
-
- <para>
- (Bug #26825)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <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="mysql-cluster-news-5-1-15-ndb-6-1-4">
- <title>Changes in MySQL 5.1.15-ndb-6.1.4 (09 March 2007))</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.4:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3268,125 +2287,13 @@
</formalpara>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.4:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: An
- <option>--ndb-wait-connected</option> 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 accepting client
- connections. See
- <link linkend="option_mysqld_ndb_wait_connected">here</link>,
- for more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster API</emphasis>: It is now
- possible to specify the transaction coordinator when
- starting a transaction. See
- <xref linkend="class-ndb-starttransaction"></xref>, for more
- information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster 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:
-
- <itemizedlist>
-
- <listitem>
- <para>
- <literal>lock_ndb_objects()</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>get_next_ndb_object()</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>unlock_ndb_objects()</literal>
- </para>
- </listitem>
-
- </itemizedlist>
-
- For more information about these methods and their use, see
- <xref linkend="class-ndb-cluster-connection-get-next-ndb-object"></xref>,
- in the MySQL Cluster API Guide.
- </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:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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 regression was introduced by Bug #14612
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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="mysql-cluster-news-5-1-15-ndb-6-1-3">
- <title>Changes in MySQL 5.1.15-ndb-6.1.3 (25 February 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.3:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3463,180 +2370,13 @@
</formalpara>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.3:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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"></xref>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster API</emphasis>: A new
- <literal>listEvents()</literal> method has been added to the
- <literal>Dictionary</literal> class. See
- <xref linkend="class-dictionary-listevents"></xref>, for
- more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <command>ndb_show_tables</command> utility now displays
- information about table events. See
- <xref linkend="mysql-cluster-utilities-ndb-show-tables"></xref>,
- for more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- It is now possible to disable arbitration by setting
- <literal>ArbitrationRank=0</literal> on all management and
- SQL nodes.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: Takeover for
- local checkpointing due to multiple failures of master nodes
- was sometimes incorrectly handled. (Bug #26457)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: The
- <literal>LockPagesInMainMemory</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>
- <emphasis role="bold">MySQL Cluster</emphasis>: Under some
- circumstances, following the restart of a management node,
- all 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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">MySQL Cluster</emphasis>: A memory
- allocation failure in <literal>SUMA</literal> (the cluster
- Subscription Manager) could cause the cluster to crash. (Bug
- #25239)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: The message
- <errortext>Error 0 in readAutoIncrementValue(): no
- Error</errortext> was written to the error log whenever
- <literal>SHOW TABLE STATUS</literal> was performed on a
- Cluster table that did not have an
- <literal>AUTO_INCREMENT</literal> column.
- </para>
-
- <note>
- <para>
- This improves on and supersedes an earlier fix that was
- made for this issue in MySQL 5.1.12.
- </para>
- </note>
-
- <para>
- (Bug #21033)
- </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>
- <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>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-2">
- <title>Changes in MySQL 5.1.15-ndb-6.1.2 (07 February 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.2:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing a recently
@@ -3710,28 +2450,13 @@
</formalpara>
</important>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.2:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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="mysql-cluster-news-5-1-15-ndb-6-1-1">
- <title>Changes in MySQL 5.1.15-ndb-6.1.1 (01 February 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.1:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3792,63 +2517,13 @@
</formalpara>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.1:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A single
- cluster can now support up to 255 API nodes, including MySQL
- servers acting as SQL nodes. See
- <xref linkend="mysql-cluster-limitations-exclusive-to-cluster"></xref>,
- for more information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster API</emphasis>:
- <emphasis role="bold">Disk Data</emphasis>: A delete and a
- read performed in the same operation could cause one or more
- 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 <literal>VARCHAR</literal>
- type and was stored on disk. (Bug #25794)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A memory leak could cause problems during a node or cluster
- shutdown or failure. (Bug #25997)
- </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 id="mysql-cluster-news-5-1-14-ndb-6-1-0">
- <title>Changes in MySQL 5.1.14-ndb-6.1.0 (20 December 2006)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.14-ndb-6.1.0:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3871,150 +2546,8 @@
from MySQL 5.1.14 standard.
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.14-ndb-6.1.0:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A new
- configuration parameter
- <literal>MemReportFrequency</literal> allows for additional
- control of data node memory usage. Previously, only warnings
- at predetermined percentages of memory allocation were
- given; setting this parameter allows for that behavior to be
- overridden. For more information, see
- <xref linkend="mysql-cluster-ndbd-definition"></xref>.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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">MySQL Cluster</emphasis>:
- <literal>SELECT</literal> statements with a
- <literal>BLOB</literal> or <literal>TEXT</literal> column in
- the selected column list and a <literal>WHERE</literal>
- condition including a primary key lookup on a
- <literal>VARCHAR</literal> primary key produced empty result
- sets. (Bug #19956)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>:
- <literal>MEDIUMTEXT</literal> columns of Disk Data tables
- were stored in memory rather than on disk, even if the
- columns were not indexed. (Bug #25001)
- </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>: 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">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
- <literal>DROP TABLE</literal> operation were not actually
- made available again until after the cluster had performed a
- local checkpoint. (Bug #17605)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster 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">Cluster 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>
- <emphasis role="bold">Cluster 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">Cluster API</emphasis>: Due to an
- error in the computation of table fragment arrays, some
- transactions were not executed from the correct starting
- point. (Bug #24914)
- </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>
-
- </itemizedlist>
-
</section>
</section>
Modified: trunk/refman-5.1/Makefile.depends
===================================================================
--- trunk/refman-5.1/Makefile.depends 2008-05-22 18:17:36 UTC (rev 10823)
+++ trunk/refman-5.1/Makefile.depends 2008-05-22 18:18:17 UTC (rev 10824)
Changed blocks: 5, Lines Added: 5, Lines Deleted: 0; 2455 bytes
@@ -730,6 +730,7 @@
../refman-5.1/metadata/mysql-cluster-news-core.idmap \
../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../refman-5.1/metadata/mysql-cluster-process-management.idmap \
+ ../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../refman-5.1/metadata/mysql-cluster-replication.idmap \
../refman-5.1/metadata/mysql-cluster-upgrade-downgrade.idmap \
../refman-5.1/metadata/mysql-cluster-utilities.idmap \
@@ -1761,6 +1762,7 @@
../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../refman-5.1/metadata/mysql-cluster-overview.idmap \
../refman-5.1/metadata/mysql-cluster-process-management.idmap \
+ ../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../refman-5.1/metadata/mysql-cluster-replication.idmap \
../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../refman-5.1/metadata/mysql-cluster-security.idmap \
@@ -2141,6 +2143,7 @@
../refman-5.1/metadata/dba-core.idmap \
../refman-5.1/metadata/mysql-cluster-backup.idmap \
../refman-5.1/metadata/mysql-cluster-multi-computer.idmap \
+ ../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../refman-5.1/metadata/mysql-cluster-replication.idmap \
../refman-5.1/metadata/mysql-cluster-upgrade-downgrade.idmap \
../refman-5.1/metadata/news-5.1-core.idmap \
@@ -2177,6 +2180,7 @@
../refman-5.1/metadata/mysql-cluster-news-core.idmap \
../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../refman-5.1/metadata/mysql-cluster-process-management.idmap \
+ ../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../refman-5.1/metadata/mysql-cluster-replication.idmap \
../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../refman-5.1/metadata/partitioning.idmap \
@@ -2362,6 +2366,7 @@
../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../refman-5.1/metadata/mysql-cluster-overview.idmap \
../refman-5.1/metadata/mysql-cluster-process-management.idmap \
+ ../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../refman-5.1/metadata/mysql-cluster-replication.idmap \
../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../refman-5.1/metadata/mysql-cluster-security.idmap \
Modified: trunk/refman-5.1/mysql-cluster-news-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-news-core.xml 2008-05-22 18:17:36 UTC (rev 10823)
+++ trunk/refman-5.1/mysql-cluster-news-core.xml 2008-05-22 18:18:17 UTC (rev 10824)
Changed blocks: 25, Lines Added: 48, Lines Deleted: 1515; 59927 bytes
@@ -1463,7 +1463,7 @@
<section id="mysql-cluster-news-5-1-15-ndb-6-1-23">
- <title>Changes in MySQL 5.1.15-ndb-6.1.23 (20 November 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.23:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating a bugfix
@@ -1499,34 +1499,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A node
- failure during a local checkpoint could lead to a subsequent
- failure of the cluster during a system restart. (Bug #31257)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A cluster restart could sometimes fail due to an issue with
- table IDs. (Bug #30975)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-22">
- <title>Changes in MySQL 5.1.15-ndb-6.1.22 (19 October 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.22:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating a bugfix
@@ -1561,34 +1540,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A node
- failure during a local checkpoint could lead to a subsequent
- failure of the cluster during a system restart. (Bug #31257)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A cluster restart could sometimes fail due to an issue with
- table IDs. (Bug #30975)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-21">
- <title>Changes in MySQL 5.1.15-ndb-6.1.21 (01 October 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.21:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating recent
@@ -1623,34 +1581,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A node
- failure during a local checkpoint could lead to a subsequent
- failure of the cluster during a system restart. (Bug #31257)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A cluster restart could sometimes fail due to an issue with
- table IDs. (Bug #30975)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-20">
- <title>Changes in MySQL 5.1.15-ndb-6.1.20 (14 September 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.20:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating a bugfix
@@ -1684,34 +1621,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A node
- failure during a local checkpoint could lead to a subsequent
- failure of the cluster during a system restart. (Bug #31257)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A cluster restart could sometimes fail due to an issue with
- table IDs. (Bug #30975)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-19">
- <title>Changes in MySQL 5.1.15-ndb-6.1.19 (01 August 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.19:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating recent
@@ -1745,38 +1661,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.19:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Whenever a
- TCP send buffer is over 80% full, temporary error 1218
- (<errortext>Send Buffers overloaded in NDB
- kernel</errortext>) is now returned. See
- <link linkend="mysql-cluster-param-tcp-definition-sendbuffermemory">SendBufferMemory</link>
- for more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- An <literal>INFO</literal> event is now sent if the time
- between global checkpoints is excessive, or if <literal>DUMP
- 7901</literal> is issued in the management client.
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-18">
- <title>Changes in MySQL 5.1.15-ndb-6.1.18 (Not released)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.18:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -1807,52 +1698,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.18:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: When
- restarting a data node, queries could hang during that
- node's start phase 5, and continue only after the node had
- entered phase 6. (Bug #29364)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Disk data
- meta-information that existed in <command>ndbd</command>
- might not be visible to <command>mysqld</command>. (Bug
- #28720)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: The number of
- free extents was incorrectly reported for some tablespaces.
- (Bug #28642)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Storage engine error conditions in row-based replication
- were not correctly reported to the user. (Bug #29570)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-17">
- <title>Changes in MySQL 5.1.15-ndb-6.1.17 (03 July 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.17:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -1885,44 +1737,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.17:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- Batching of updates on cluster replication slaves, enabled
- using the <option>--slave-allow-batching</option> option for
- <command>mysqld</command>.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Replica redo
- logs were inconsistently handled during a system restart.
- (Bug #29354)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-16">
- <title>Changes in MySQL 5.1.15-ndb-6.1.16 (29 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.16:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -1954,63 +1775,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.16:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: When a node
- failed to respond to a <literal>COPY_GCI</literal> signal as
- part of a global checkpoint, the master node was killed
- instead of the node that actually failed. (Bug #29331)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: An invalid
- comparison made during <literal>REDO</literal> validation
- that could lead to an <errortext>Error while reading REDO
- log</errortext> condition. (Bug #29118)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: The wrong
- data pages were sometimes invalidated following a global
- checkpoint. (Bug #29067)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: If at least
- 2 files were involved in <literal>REDO</literal>
- invalidation, then file 0 of page 0 was not updated and so
- pointed to an invalid part of the redo log. (Bug #29057)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: When dropping a
- page, the stack's bottom entry could sometime be left
- <quote>cold</quote> rather than <quote>hot</quote>,
- violating the rules for stack pruning. (Bug #29176)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-15">
- <title>Changes in MySQL 5.1.15-ndb-6.1.15 (20 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.15:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing a recently
@@ -2042,27 +1813,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.15:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Memory
- corruption could occur due to a problem in the
- <literal>DBTUP</literal> kernel block. (Bug #29229)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-14">
- <title>Changes in MySQL 5.1.15-ndb-6.1.14 (19 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.14:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, incorporating bugfixes
@@ -2093,31 +1850,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.14:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: In the event
- that two data nodes in the same node group and participating
- in a GCP crashed before they had written their respective
- <filename>P0.sysfile</filename> files,
- <literal>QMGR</literal> could refuse to start, issuing an
- invalid <errortext>Insufficient nodes for
- restart</errortext> error instead. (Bug #29167)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-13">
- <title>Changes in MySQL 5.1.15-ndb-6.1.13 (15 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.13:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2149,27 +1888,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.13:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- Read ahead was implemented for backups of Disk Data tables,
- resulting in a 10 to 15% increase in backup speed of Disk
- Data tables. (Bug #29099)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-12">
- <title>Changes in MySQL 5.1.15-ndb-6.1.12 (13 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.12:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2200,54 +1925,13 @@
5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.12:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: New cluster
- management client <literal>DUMP</literal> commands were
- added to aid in tracking transactions, scan operations, and
- locks. See
- <xref linkend="ndb-internals-dump-command-2350"></xref>,
- <xref linkend="ndb-internals-dump-command-2352"></xref>, and
- <xref linkend="ndb-internals-dump-command-2550"></xref>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Backup dump output was extended to provide more information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: It is now
- possible to set the maximum size of the allocation unit for
- table memory using the <literal>MaxAllocate</literal>
- configuration parameter. (Bug #29044)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-11">
- <title>Changes in MySQL 5.1.15-ndb-6.1.11 (06 June 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.11:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2278,85 +1962,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.11:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Important Change</emphasis>:
- <emphasis role="bold">MySQL Cluster</emphasis>: The
- <literal>TimeBetweenWatchdogCheckInitial</literal>
- configuration parameter was added to allow setting of a
- separate watchdog timeout for memory allocation during
- startup of the data nodes. See
- <xref linkend="mysql-cluster-ndbd-definition"></xref>, for
- more information. (Bug #28899)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A new
- configuration parameter <literal>ODirect</literal> causes
- <literal>NDB</literal> to attempt using
- <literal>O_DIRECT</literal> writes for LCP, backups, and
- redo logs, often lowering CPU usage.
- </para>
- </listitem>
-
- <listitem>
- <para>
- It is now possible to set the size of redo log files
- (fragment log files) using the
- <literal>FragmentLogFileSize</literal> configuration
- parameter.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Having large
- amounts of memory locked caused swapping to disk. (Bug
- #28751)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: LCP files
- were not removed following an initial system restart. (Bug
- #28726)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Repeated
- <literal>INSERT</literal> and <literal>DELETE</literal>
- operations on a Disk Data table having one or more large
- <literal>VARCHAR</literal> columns could cause data nodes to
- fail. (Bug #20612)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-10">
- <title>Changes in MySQL 5.1.15-ndb-6.1.10 (30 May 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.10:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2386,110 +1998,13 @@
(see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.10:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A new
- <literal>times</literal> printout was added in the
- <command>ndbd</command> watchdog thread.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Some
- unneeded printouts in the <command>ndbd</command> out file
- were removed.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The names of some log and other files were changed to avoid
- issues with the <command>tar</command> command's
- 99-character filename limit.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A regression
- in the heartbeat monitoring code could lead to node failure
- under high load. This issue affected MySQL 5.1.19 and MySQL
- 5.1.15-ndb-6.1.10 only. (Bug #28783)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A corrupt
- schema file could cause a <errortext>File already
- open</errortext> error. (Bug #28770)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Setting
- <literal>InitialNoOpenFiles</literal> equal to
- <literal>MaxNoOfOpenFiles</literal> caused an error. This
- was due to the fact that the actual value of
- <literal>MaxNoOfOpenFiles</literal> as used by the cluster
- was offset by 1 from the value set in
- <filename>config.ini</filename>. (Bug #28749)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A race
- condition could result when non-master nodes (in addition to
- the master node) tried to update active status due to a
- local checkpoint (that is, between
- <literal>NODE_FAILREP</literal> and
- <literal>COPY_GCIREQ</literal> events). Now only the master
- updates the active status. (Bug #28717)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A fast
- global checkpoint under high load with high usage of the
- redo buffer caused data nodes to fail. (Bug #28653)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: When loading
- data into a cluster following a version upgrade, the data
- nodes could forcibly shut down due to page and buffer
- management failures (that is, <literal>ndbrequire</literal>
- failures in <literal>PGMAN</literal>). (Bug #28525)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-9">
- <title>Changes in MySQL 5.1.15-ndb-6.1.9 (24 May 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.9:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2509,36 +2024,13 @@
<xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.9:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: When an API
- node sent more than 1024 signals in a single batch,
- <literal>NDB</literal> would process only the first 1024 of
- these, and then hang. (Bug #28443)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: The cluster
- backup process scanned in <literal>ACC</literal> index
- order, which had bad effects for disk data. (Bug #28593)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-8">
- <title>Changes in MySQL 5.1.15-ndb-6.1.8 (05 May 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.8:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2567,63 +2059,13 @@
(see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.8:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Local
- checkpoint files relating to dropped <literal>NDB</literal>
- tables were not removed. (Bug #28348)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Repeated
- insertion of data generated by <command>mysqldump</command>
- into <literal>NDB</literal> tables could eventually lead to
- failure of the cluster. (Bug #27437)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Extremely large
- inserts into Disk Data tables could lead to data node
- failure in some circumstances. (Bug #27942)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster API</emphasis>: In a
- multi-operation transaction, a delete operation followed by
- the insertion of an implicit <literal>NULL</literal> failed
- to overwrite an existing value. (Bug #20535)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Setting <literal>MaxNoOfTables</literal> very low and
- relative to <literal>DataMemory</literal> caused
- <errortext>Out of memory in Ndb Kernel</errortext> errors
- when inserting relatively small amounts of data into NDB
- tables. (Bug #24173)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-7">
- <title>Changes in MySQL 5.1.15-ndb-6.1.7 (05 May 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.7:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2685,206 +2127,13 @@
</para>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.7:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- <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
- &mccge-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"></xref>,
- for additional information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: The cluster
- waited 30 seconds instead of 30 milliseconds before reading
- table statistics. (Bug #28093)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Under
- certain rare circumstances, <command>ndbd</command> could
- get caught in an infinite loop when one transaction took a
- read lock and then a second transaction attempted to obtain
- a write lock on the same tuple in the lock queue. (Bug
- #28073)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Under some
- circumstances, a node restart could fail to update the
- Global Checkpoint Index (GCI). (Bug #28023)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Under
- certain rare circumstances performing a <literal>DROP
- TABLE</literal> or <literal>TRUNCATE</literal> on an
- <literal>NDB</literal> table could cause a node failure or
- forced cluster shutdown. (Bug #27581)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Memory usage
- of a <command>mysqld</command> process grew even while idle.
- (Bug #27560)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Performing a
- delete followed by an insert during a local checkpoint could
- cause a <errortext>Rowid already allocated</errortext>
- error. (Bug #27205)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Replication</emphasis>: Some queries
- that updated multiple tables were not backed up correctly.
- (Bug #27748)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- <emphasis role="bold">Disk Data</emphasis>: An issue with
- replication of Disk Data tables could in some cases lead to
- node failure. (Bug #28161)
- </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>
- <emphasis role="bold">Disk Data</emphasis>: When restarting
- a data node following the creation of a large number of Disk
- Data objects (approximately 200 such objects), the cluster
- could not assign a node ID to the restarting node. (Bug
- #25741)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>: Changing a
- column specification or issuing a
- <literal>TRUNCATE</literal> statement on a Disk Data table
- caused the table to become an in-memory table.
- </para>
-
- <para>
- This fix supersedes an incomplete fix that was made for this
- issue in MySQL 5.1.15. (Bug #24667, Bug #25296)
- </para>
- </listitem>
-
- <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 #27728)
- </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">Cluster API</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>
- An <literal>INSERT</literal> followed by a delete
- <literal>DELETE</literal> on the same <literal>NDB</literal>
- table caused a memory leak. (Bug #27756)
- </para>
-
- <para>
- This regression was introduced by Bug #20612
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqldump</command> could not dump log tables. (Bug
- #26121)
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <option>--with-readline</option> option for
- <command>configure</command> did not work for commercial
- source packages, but no error message was printed to that
- effect. Now a message is printed. (Bug #25530)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-6">
- <title>Changes in MySQL 5.1.15-ndb-6.1.6 (Not released)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.6:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -2912,164 +2161,13 @@
(see <xref linkend="news-5-1-15"/>).
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.6:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- <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
- &mccge-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"></xref>,
- for additional information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: It was not
- possible to set <literal>LockPagesInMainMemory</literal>
- equal to <literal>0</literal>. (Bug #27291)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>:
- <command>mysqld</command> could crash shortly after a data
- node failure following certain DML operations. (Bug #27169)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: The failure
- of a data node while restarting could cause other data nodes
- to hang or crash. (Bug #27003)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>:
- <command>mysqld</command> processes would sometimes crash
- under high load.
- </para>
-
- <note>
- <para>
- This fix improves on and replaces a fix for this bug that
- was made in MySQL 5.1.15-ndb-6.1.5.
- </para>
- </note>
-
- <para>
- (Bug #26825)
- </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>
- <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 API</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 API</emphasis>: A delete
- operation using a scan followed by an insert using a scan
- could cause a data node to fail. (Bug #27203)
- </para>
- </listitem>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-5">
- <title>Changes in MySQL 5.1.15-ndb-6.1.5 (15 March 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.5:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3141,92 +2239,13 @@
</formalpara>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.5:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster Replication</emphasis>:
- <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
- &mccge-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"></xref>,
- for additional information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: Creating a
- table on one SQL node while in single user mode caused other
- SQL nodes to crash. (Bug #26997)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>:
- <command>mysqld</command> processes would sometimes crash
- under high load.
- </para>
-
- <note>
- <para>
- This fix was reverted in MySQL 5.1.15-ndb-6.1.6.
- </para>
- </note>
-
- <para>
- (Bug #26825)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <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="mysql-cluster-news-5-1-15-ndb-6-1-4">
- <title>Changes in MySQL 5.1.15-ndb-6.1.4 (09 March 2007))</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.4:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3295,125 +2314,13 @@
</formalpara>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.4:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: An
- <option>--ndb-wait-connected</option> 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 accepting client
- connections. See
- <link linkend="option_mysqld_ndb_wait_connected">here</link>,
- for more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster API</emphasis>: It is now
- possible to specify the transaction coordinator when
- starting a transaction. See
- <xref linkend="class-ndb-starttransaction"></xref>, for more
- information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster 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:
-
- <itemizedlist>
-
- <listitem>
- <para>
- <literal>lock_ndb_objects()</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>get_next_ndb_object()</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>unlock_ndb_objects()</literal>
- </para>
- </listitem>
-
- </itemizedlist>
-
- For more information about these methods and their use, see
- <xref linkend="class-ndb-cluster-connection-get-next-ndb-object"></xref>,
- in the MySQL Cluster API Guide.
- </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:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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 regression was introduced by Bug #14612
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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="mysql-cluster-news-5-1-15-ndb-6-1-3">
- <title>Changes in MySQL 5.1.15-ndb-6.1.3 (25 February 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.3:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3490,180 +2397,13 @@
</formalpara>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.3:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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"></xref>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster API</emphasis>: A new
- <literal>listEvents()</literal> method has been added to the
- <literal>Dictionary</literal> class. See
- <xref linkend="class-dictionary-listevents"></xref>, for
- more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <command>ndb_show_tables</command> utility now displays
- information about table events. See
- <xref linkend="mysql-cluster-utilities-ndb-show-tables"></xref>,
- for more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- It is now possible to disable arbitration by setting
- <literal>ArbitrationRank=0</literal> on all management and
- SQL nodes.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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">MySQL Cluster</emphasis>: 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: Takeover for
- local checkpointing due to multiple failures of master nodes
- was sometimes incorrectly handled. (Bug #26457)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: The
- <literal>LockPagesInMainMemory</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>
- <emphasis role="bold">MySQL Cluster</emphasis>: Under some
- circumstances, following the restart of a management node,
- all 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>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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">MySQL Cluster</emphasis>: A memory
- allocation failure in <literal>SUMA</literal> (the cluster
- Subscription Manager) could cause the cluster to crash. (Bug
- #25239)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: The message
- <errortext>Error 0 in readAutoIncrementValue(): no
- Error</errortext> was written to the error log whenever
- <literal>SHOW TABLE STATUS</literal> was performed on a
- Cluster table that did not have an
- <literal>AUTO_INCREMENT</literal> column.
- </para>
-
- <note>
- <para>
- This improves on and supersedes an earlier fix that was
- made for this issue in MySQL 5.1.12.
- </para>
- </note>
-
- <para>
- (Bug #21033)
- </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>
- <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>
-
- </itemizedlist>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-2">
- <title>Changes in MySQL 5.1.15-ndb-6.1.2 (07 February 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.2:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing a recently
@@ -3737,28 +2477,13 @@
</formalpara>
</important>
- <para>
- Bugs fixed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.2:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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="mysql-cluster-news-5-1-15-ndb-6-1-1">
- <title>Changes in MySQL 5.1.15-ndb-6.1.1 (01 February 2007)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.1:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3819,63 +2544,13 @@
</formalpara>
</important>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.1:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A single
- cluster can now support up to 255 API nodes, including MySQL
- servers acting as SQL nodes. See
- <xref linkend="mysql-cluster-limitations-exclusive-to-cluster"></xref>,
- for more information.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster API</emphasis>:
- <emphasis role="bold">Disk Data</emphasis>: A delete and a
- read performed in the same operation could cause one or more
- 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 <literal>VARCHAR</literal>
- type and was stored on disk. (Bug #25794)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A memory leak could cause problems during a node or cluster
- shutdown or failure. (Bug #25997)
- </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 id="mysql-cluster-news-5-1-14-ndb-6-1-0">
- <title>Changes in MySQL 5.1.14-ndb-6.1.0 (20 December 2006)</title>
+ <title condition="dynamic:changelog:vertitle" role="5.1.14-ndb-6.1.0:mysqld:all"/>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -3898,150 +2573,8 @@
from MySQL 5.1.14 standard.
</para>
- <para>
- Functionality added or changed:
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.14-ndb-6.1.0:mysqld:all"/>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: A new
- configuration parameter
- <literal>MemReportFrequency</literal> allows for additional
- control of data node memory usage. Previously, only warnings
- at predetermined percentages of memory allocation were
- given; setting this parameter allows for that behavior to be
- overridden. For more information, see
- <xref linkend="mysql-cluster-ndbd-definition"></xref>.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis role="bold">MySQL Cluster</emphasis>: 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">MySQL Cluster</emphasis>:
- <literal>SELECT</literal> statements with a
- <literal>BLOB</literal> or <literal>TEXT</literal> column in
- the selected column list and a <literal>WHERE</literal>
- condition including a primary key lookup on a
- <literal>VARCHAR</literal> primary key produced empty result
- sets. (Bug #19956)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Disk Data</emphasis>:
- <literal>MEDIUMTEXT</literal> columns of Disk Data tables
- were stored in memory rather than on disk, even if the
- columns were not indexed. (Bug #25001)
- </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>: 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">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
- <literal>DROP TABLE</literal> operation were not actually
- made available again until after the cluster had performed a
- local checkpoint. (Bug #17605)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <emphasis role="bold">Cluster 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">Cluster 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>
- <emphasis role="bold">Cluster 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">Cluster API</emphasis>: Due to an
- error in the computation of table fragment arrays, some
- transactions were not executed from the correct starting
- point. (Bug #24914)
- </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>
-
- </itemizedlist>
-
</section>
</section>
Modified: trunk/refman-5.1-maria/Makefile.depends
===================================================================
--- trunk/refman-5.1-maria/Makefile.depends 2008-05-22 18:17:36 UTC (rev 10823)
+++ trunk/refman-5.1-maria/Makefile.depends 2008-05-22 18:18:17 UTC (rev 10824)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 634 bytes
@@ -416,6 +416,7 @@
../ndbapi/metadata/ndbapi.idmap \
../quick-guides/metadata/reservedwords-core.idmap \
../refman-5.1-maria/metadata/se-maria.idmap \
+ ../refman-5.1/metadata/mysql-cluster-replication-conflict-resolution.idmap \
../refman-5.1/metadata/storage-engines.idmap \
../refman-6.0/metadata/dba-core.idmap \
../refman-6.0/metadata/manual.idmap \
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10824 - in trunk: dynamic-docs/changelog it/refman-5.1 pt/refman-5.1 refman-5.1 refman-5.1-maria | jon | 22 May |
