Author: jstephens
Date: 2008-05-23 17:40:20 +0200 (Fri, 23 May 2008)
New Revision: 10832
Log:
CGE is dead - long live Cluster!
Removed:
trunk/it/refman-5.1/mysql-cluster-cge-building-tmp.xml
trunk/it/refman-5.1/mysql-cluster-cge.xml
trunk/pt/refman-5.1/mysql-cluster-cge-building-tmp.xml
trunk/pt/refman-5.1/mysql-cluster-cge.xml
trunk/refman-5.1/dba-core-new-tmp.xml
trunk/refman-5.1/mysql-cluster-cge-building-tmp.xml
trunk/refman-5.1/mysql-cluster-cge.xml
trunk/refman-6.0/mysql-cluster-cge.xml
Renamed/Moved:
trunk/refman-5.1/mysql-cluster-cge-building.TEMP (from rev 10828, trunk/refman-5.1/mysql-cluster-cge-building-tmp.xml)
Modified:
trunk/common/phrases.ent
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/dynamic-docs/changelog/mysqld-versions.xml
trunk/dynamic-docs/changelog/mysqld.xml
trunk/it/refman-5.1/Makefile.depends
trunk/it/refman-5.1/introduction.xml
trunk/it/refman-5.1/mysql-cluster-backup.xml
trunk/it/refman-5.1/mysql-cluster-configuration.xml
trunk/it/refman-5.1/mysql-cluster-disk-data.xml
trunk/it/refman-5.1/mysql-cluster-glossary.xml
trunk/it/refman-5.1/mysql-cluster-interconnects.xml
trunk/it/refman-5.1/mysql-cluster-limitations.xml
trunk/it/refman-5.1/mysql-cluster-management.xml
trunk/it/refman-5.1/mysql-cluster-multi-computer.xml
trunk/it/refman-5.1/mysql-cluster-news-core.xml
trunk/it/refman-5.1/mysql-cluster-optvar-core.xml
trunk/it/refman-5.1/mysql-cluster-process-management.xml
trunk/it/refman-5.1/mysql-cluster-replication.xml
trunk/it/refman-5.1/mysql-cluster-roadmap.xml
trunk/it/refman-5.1/mysql-cluster-upgrade-downgrade.xml
trunk/it/refman-5.1/mysql-cluster-utilities.xml
trunk/it/refman-5.1/mysql-cluster.xml
trunk/it/refman-5.1/news-5.1-core.xml
trunk/it/refman-5.1/sql-syntax.xml
trunk/ndbapi/class-dictionary.xml
trunk/ndbapi/class-ndb-cluster-connection.xml
trunk/ndbapi/class-ndb.xml
trunk/ndbapi/class-ndbeventoperation.xml
trunk/ndbapi/class-ndbindexscanoperation.xml
trunk/ndbapi/class-ndbscanoperation.xml
trunk/ndbapi/class-ndbtransaction.xml
trunk/ndbapi/interface-ndbrecord.xml
trunk/ndbapi/ndb-examples.xml
trunk/ndbapi/ndb-internals.xml
trunk/ndbapi/struct-indexbound.xml
trunk/ndbapi/struct-recordspecification.xml
trunk/pt/refman-5.1/Makefile.depends
trunk/pt/refman-5.1/introduction.xml
trunk/pt/refman-5.1/mysql-cluster-backup.xml
trunk/pt/refman-5.1/mysql-cluster-configuration.xml
trunk/pt/refman-5.1/mysql-cluster-disk-data.xml
trunk/pt/refman-5.1/mysql-cluster-glossary.xml
trunk/pt/refman-5.1/mysql-cluster-interconnects.xml
trunk/pt/refman-5.1/mysql-cluster-limitations.xml
trunk/pt/refman-5.1/mysql-cluster-management.xml
trunk/pt/refman-5.1/mysql-cluster-multi-computer.xml
trunk/pt/refman-5.1/mysql-cluster-news-core.xml
trunk/pt/refman-5.1/mysql-cluster-optvar-core.xml
trunk/pt/refman-5.1/mysql-cluster-process-management.xml
trunk/pt/refman-5.1/mysql-cluster-replication.xml
trunk/pt/refman-5.1/mysql-cluster-roadmap.xml
trunk/pt/refman-5.1/mysql-cluster-upgrade-downgrade.xml
trunk/pt/refman-5.1/mysql-cluster-utilities.xml
trunk/pt/refman-5.1/mysql-cluster.xml
trunk/pt/refman-5.1/news-5.1-core.xml
trunk/pt/refman-5.1/sql-syntax.xml
trunk/refman-5.1-maria/Makefile.depends
trunk/refman-5.1/Makefile.depends
trunk/refman-5.1/introduction.xml
trunk/refman-5.1/mysql-cluster-backup.xml
trunk/refman-5.1/mysql-cluster-changelog-TEMPLATE.xml
trunk/refman-5.1/mysql-cluster-configuration.xml
trunk/refman-5.1/mysql-cluster-disk-data.xml
trunk/refman-5.1/mysql-cluster-limitations.xml
trunk/refman-5.1/mysql-cluster-management.xml
trunk/refman-5.1/mysql-cluster-multi-computer.xml
trunk/refman-5.1/mysql-cluster-news-core.xml
trunk/refman-5.1/mysql-cluster-optvar-core.xml
trunk/refman-5.1/mysql-cluster-process-management.xml
trunk/refman-5.1/mysql-cluster-replication.xml
trunk/refman-5.1/mysql-cluster-roadmap.xml
trunk/refman-5.1/mysql-cluster-upgrade-downgrade.xml
trunk/refman-5.1/mysql-cluster-utilities.xml
trunk/refman-5.1/mysql-cluster.xml
trunk/refman-5.1/news-5.1-core.xml
trunk/refman-5.1/sql-syntax.xml
trunk/refman-6.0/mysql-cluster-backup.xml
trunk/refman-6.0/mysql-cluster-configuration.xml
trunk/refman-6.0/mysql-cluster-limitations.xml
trunk/refman-6.0/mysql-cluster-multi-computer.xml
trunk/refman-6.0/mysql-cluster-roadmap.xml
trunk/refman-6.0/mysql-cluster-upgrade-downgrade.xml
trunk/refman-6.0/mysql-cluster-utilities.xml
trunk/refman-6.0/mysql-cluster.xml
trunk/refman-common/urls.ent
trunk/tools/MySQL/DynXML/Changelog.pm
Modified: trunk/common/phrases.ent
===================================================================
--- trunk/common/phrases.ent 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/common/phrases.ent 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 11; 3299 bytes
@@ -13,14 +13,9 @@
<!ENTITY questions 'Questions'>
<!ENTITY questionsandanswers 'Questions and Answers'>
-<!-- Specific to MCCGE, used in 5.1 Manual and Cluster API docs -->
-<!ENTITY mccge-series "MySQL Cluster ¤t-series; Carrier Grade Edition">
-<!ENTITY mccge-current-6.2 "5.1.24-ndb-6.2.16"><!-- Current MySQL CGE 6.2 version - update with new releases -->
-<!ENTITY mccge-current-6.3 "5.1.24-ndb-6.3.14-beta"><!-- Current MySQL CGE 6.3 version - update with new releases -->
-<!ENTITY mccge-warning-section '<formalpara role="mysql-cluster-warning"><title>&mccge-series;</title><para>The information in this section applies to users of &mccge-series; only. For more information about &mccge-series;, see <xref linkend="mysql-cluster-cge"/>.</para></formalpara>'>
-<!ENTITY mccge-warning-begin '<formalpara role="mysql-cluster-warning"><title>&mccge-series;</title><para>The following information applies to users of &mccge-series; only. For more information about &mccge-series;, see <xref linkend="mysql-cluster-cge"/>.</para></formalpara>'>
-<!ENTITY mccge-warning-end-api '<para role="mysql-cluster-warning">The following information applies to all MySQL Cluster API users.</para>'>
-<!ENTITY mccge-warning-end-cluster '<para role="mysql-cluster-warning">The following information applies to all MySQL Cluster users.</para>'>
-<!ENTITY mccge-warning-end-all '<para role="mysql-cluster-warning">The following information applies to all MySQL users.</para>'>
-<!ENTITY mccge-warning-section-unsupported '<formalpara role="mysql-cluster-warning"><title>&mccge-series;</title><para>The information in this section does not apply to users of &mccge-series;. For more information about &mccge-series;, see <xref linkend="mysql-cluster-cge"/>.</para></formalpara>'>
-<!ENTITY mccge-warning-unsupported-begin '<formalpara role="mysql-cluster-warning"><title>&mccge-series;</title><para>The following information does not apply to users of &mccge-series;. For more information about &mccge-series;, see <xref linkend="mysql-cluster-cge"/>.</para></formalpara>'>
+<!-- Specific to MySQL Cluster, used in 5.1 Manual and Cluster API docs -->
+<!ENTITY mysql-cluster-current-6.2 "5.1.24-ndb-6.2.16"><!-- Current MySQL NDB 6.2 version - update with new releases -->
+<!ENTITY mysql-cluster-current-6.3 "5.1.24-ndb-6.3.15-beta"><!-- Current MySQL NDB 6.3 version - update with new releases -->
+<!ENTITY mysql-cluster-warning-section '<formalpara role="mysql-cluster-warning"><title>MySQL Cluster</title><para>The information in this section applies to users of MySQL Cluster only. For more information, see <xref linkend="mysql-cluster"/>.</para></formalpara>'>
+<!ENTITY mysql-cluster-warning-begin '<formalpara role="mysql-cluster-warning"><title>MySQL Cluster</title><para>The following information applies to users of MySQL Cluster only. For more information, see <xref linkend="mysql-cluster"/>.</para></formalpara>'>
+<!ENTITY mysql-cluster-warning-end '<para role="mysql-cluster-warning">The following information applies to all MySQL users.</para>'>
\ No newline at end of file
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 10, Lines Added: 22, Lines Deleted: 30; 5469 bytes
@@ -332,17 +332,13 @@
included in 5.1 mainline sources is no longer guaranteed to be
maintained or supported. Those using MySQL Cluster in MySQL
5.1.23 and earlier MySQL 5.1 mainline releases should upgrade to
- &mccge-series; 6.2.15 when this becomes available. Sources for
- &mccge-series; are available under GPL, and both commercial and
- GPL binaries for supported platforms are expected for
- &mccge-series; 6.2.15 and later &mccge-series; releases.
+ MySQL Cluster NDB 6.2.15 when this becomes available. Sources
+ for MySQL Cluster NDB 6.x are available under GPL, and both
+ commercial and GPL binaries for supported platforms are expected
+ for MySQL Cluster NDB 6.2.15 and later MySQL Cluster NDB 6.x
+ releases.
</para>
- <para>
- For more information about &mccge-series;, see
- <xref linkend="mysql-cluster-cge"/>.
- </para>
-
</message>
<message ver="6.0.5">
@@ -354,17 +350,13 @@
included in 6.0 mainline sources is no longer guaranteed to be
maintained or supported. Those using MySQL Cluster in MySQL
6.0.4 and earlier MySQL 6.0 mainline releases should upgrade to
- &mccge-series; 6.2.15 when this becomes available. Sources for
- &mccge-series; are available under GPL, and both commercial and
- GPL binaries for supported platforms are expected for
- &mccge-series; 6.2.15 and later &mccge-series; releases.
+ MySQL Cluster NDB 6.2.15 when this becomes available. Sources
+ for MySQL Cluster NDB 6.x are available under GPL, and both
+ commercial and GPL binaries for supported platforms are expected
+ for MySQL Cluster NDB 6.2.15 and later MySQL Cluster NDB 6.x
+ releases.
</para>
- <para>
- For more information about &mccge-series;, see
- <ulink url="&base-url-refman;/5.1/en/mysql-cluster-cge.html"/>.
- </para>
-
</message>
</logentry>
@@ -553,7 +545,7 @@
<para>
<literal>NdbScanFilter::getNdbOperation()</literal>, which was
- inadvertently removed in mysql-5.1.23-ndb-6.3.11, has been
+ inadvertently removed in MySQL Cluster NDB 6.3.11, has been
restored.
</para>
@@ -607,7 +599,7 @@
<para>
Node or system restarts could fail due an unitialized variable
in the <literal>DTUP</literal> kernel block. This issue was
- found in mysql-5.1.23-ndb-6.3.11.
+ found in MySQL Cluster NDB 6.3.11.
</para>
</message>
@@ -4495,8 +4487,8 @@
<para>
Due to the reduction of the number of local checkpoints from 3
- to 2 in MySQL 5.1.23-ndb-6.3.8, a data node using ndbd from
- MySQL 5.1.23-ndb-6.3.8 or later started using a filesystem from
+ to 2 in MySQL Cluster NDB 6.3.8, a data node using ndbd from
+ MySQL Cluster NDB 6.3.8 or later started using a filesystem from
an earlier version could incorrectly invalidate local
checkpoints too early during the startup process, causing the
node to fail.
@@ -4702,7 +4694,7 @@
<para>
Cluster failures could sometimes occur when performing more than
three parallel takeovers during node restarts or system
- restarts. This affected &mccge-series;
+ restarts. This affected MySQL Cluster NDB
6.3.<replaceable>x</replaceable> releases only.
</para>
@@ -5085,7 +5077,7 @@
<message>
<para>
- Beginning with this version, &mccge-series;
+ Beginning with this version, MySQL Cluster NDB
6.3.<replaceable>x</replaceable> releases once again include the
<literal>InnoDB</literal> storage engine. In order to enable
<literal>InnoDB</literal>, you must configure the build using
@@ -6122,7 +6114,7 @@
<para>
<literal>DROP TABLE</literal> did not free all data memory. This
- bug was observed in MySQL 5.1.23-ndb-6.3.7 only.
+ bug was observed in MySQL Cluster NDB 6.3.7 only.
</para>
</message>
@@ -6154,7 +6146,7 @@
API applications built against a MySQL Cluster version that did
not support micro-GCPs accessing a later version that supported
micro-GCPs. This issue was observed while upgrading from MySQL
- 5.1.15-ndb-6.1.23 to MySQL 5.1.23-ndb-6.2.10 when the API
+ Cluster NDB 6.1.23 to MySQL Cluster NDB 6.2.10 when the API
application built against the earlier version attempted to
access a data node already running the later version, even after
disabling micro-GCPs by setting
@@ -7227,10 +7219,10 @@
</para>
<para>
- A workaround when restoring to &mccge-series; releases
- supporting micro-GCPs previous to MySQL 5.1.23-ndb-6.3.8 is to
- perform a 32-bit shift on the <literal>epoch</literal> column
- values to reduce them to their proper size.
+ A workaround when restoring to MySQL Cluster releases supporting
+ micro-GCPs previous to MySQL Cluster NDB 6.3.8 is to perform a
+ 32-bit shift on the <literal>epoch</literal> column values to
+ reduce them to their proper size.
</para>
</message>
Modified: trunk/dynamic-docs/changelog/mysqld-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-versions.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/dynamic-docs/changelog/mysqld-versions.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 905 bytes
@@ -40,8 +40,8 @@
</versionentry>
<versionentry ver="5.1.24" reldate="08 April 2008"/>
<versionentry ver="5.1.24" subver="ndb-6.3.15" reldate="Not yet released"/>
+ <versionentry ver="5.1.24" subver="ndb-6.2.16" reldate="Not yet released"/>
<versionentry ver="5.1.24" subver="ndb-6.3.14" reldate="11 May 2008"/>
- <versionentry ver="5.1.24" subver="ndb-6.2.16" reldate="Not yet released"/>
<versionentry ver="5.1.24" subver="ndb-6.3.13" reldate="10 April 2008"/>
<versionentry ver="5.1.23" reldate="29 January 2008"/>
<versionentry ver="5.1.23" subver="ndb-6.3.12" reldate="05 April 2008"/>
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 6, Lines Added: 10, Lines Deleted: 11; 2745 bytes
@@ -1802,7 +1802,7 @@
<command>ndb_restore</command> displayed incorrect backup file
version information. This meant (for example) that, when
attempting to restore a backup made from a MySQL 5.1.22 cluster
- to a MySQL 5.1.22-ndb-6.3.3 cluster, the restore process failed
+ to a MySQL Cluster NDB 6.3.3 cluster, the restore process failed
with the error <errortext>Restore program older than backup
version. Not supported. Use new restore program.</errortext>
</para>
@@ -1898,11 +1898,10 @@
<message>
<para>
- &mccge-series; 6.2.<replaceable>x</replaceable> and
- 6.3.<replaceable>x</replaceable> source archives are now
- available in separate commercial and GPL versions. Due to
- licensing concerns, previous &mccge-series; source archives were
- removed from the FTP site.
+ MySQL Cluster NDB 6.2 and 6.3 source archives are now available
+ in separate commercial and GPL versions. Due to licensing
+ concerns, previous MySQL Cluster NDB 6.2 and 6.3 source archives
+ were removed from the FTP site.
</para>
</message>
@@ -45656,7 +45655,7 @@
<note>
<para>
- This fix was reverted in MySQL 5.1.15-ndb-6.1.6.
+ This fix was reverted in MySQL Cluster NDB 6.1.6.
</para>
</note>
@@ -45672,7 +45671,7 @@
<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.
+ made in MySQL Cluster NDB 6.1.5.
</para>
</note>
@@ -65101,7 +65100,7 @@
<para>
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.
+ MySQL Cluster NDB 6.1.10 only.
</para>
</message>
@@ -96532,8 +96531,8 @@
<para>
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
+ upgrading to this release from a previous MySQL Cluster NDB 6.x
+ 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.
Modified: trunk/it/refman-5.1/Makefile.depends
===================================================================
--- trunk/it/refman-5.1/Makefile.depends 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/Makefile.depends 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 16, Lines Added: 11, Lines Deleted: 41; 8380 bytes
@@ -728,7 +728,6 @@
../../refman-5.1/metadata/installing-core.idmap \
../../refman-5.1/metadata/introduction.idmap \
../../refman-5.1/metadata/mysql-cluster-backup.idmap \
- ../../refman-5.1/metadata/mysql-cluster-cge.idmap \
../../refman-5.1/metadata/mysql-cluster-configuration.idmap \
../../refman-5.1/metadata/mysql-cluster-limitations.idmap \
../../refman-5.1/metadata/mysql-cluster-management.idmap \
@@ -736,11 +735,11 @@
../../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.idmap \
- ../../refman-5.1/metadata/mysql-cluster-upgrade-downgrade.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../../refman-5.1/metadata/mysql-cluster-utilities.idmap \
+ ../../refman-5.1/metadata/mysql-cluster.idmap \
../../refman-5.1/metadata/news-5.1-core.idmap \
- ../../refman-5.1/metadata/sql-syntax.idmap \
- ../../refman-6.0/metadata/mysql-cluster-cge.idmap
+ ../../refman-5.1/metadata/sql-syntax.idmap
dynxml-local-mysql-cluster-news.validpure: $(dynxml_local_mysql_cluster_news_SOURCES)
dynxml-local-mysql-cluster-news.titles: $(dynxml_local_mysql_cluster_news_SOURCES)
dynxml-local-mysql-cluster-news.useless: $(dynxml_local_mysql_cluster_news_SOURCES)
@@ -763,7 +762,6 @@
dynxml_local_mysql_cluster_optvar_SOURCES = dynxml-local-mysql-cluster-optvar.xml $(dynxml_local_mysql_cluster_optvar_INCLUDES)
dynxml_local_mysql_cluster_optvar_IDMAPS = \
../../refman-5.1/metadata/dba-core.idmap \
- ../../refman-5.1/metadata/mysql-cluster-cge.idmap \
../../refman-5.1/metadata/mysql-cluster-configuration.idmap \
../../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../../refman-5.1/metadata/mysql-cluster-process-management.idmap \
@@ -804,7 +802,6 @@
../../refman-5.1/metadata/introduction.idmap \
../../refman-5.1/metadata/language-structure-core.idmap \
../../refman-5.1/metadata/mysql-cluster-backup.idmap \
- ../../refman-5.1/metadata/mysql-cluster-cge.idmap \
../../refman-5.1/metadata/mysql-cluster-configuration.idmap \
../../refman-5.1/metadata/mysql-cluster-interconnects.idmap \
../../refman-5.1/metadata/mysql-cluster-management.idmap \
@@ -1270,6 +1267,7 @@
../../refman-5.1/metadata/language-structure-core.idmap \
../../refman-5.1/metadata/mysql-cluster-disk-data.idmap \
../../refman-5.1/metadata/mysql-cluster-replication.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../../refman-5.1/metadata/mysql-cluster.idmap \
../../refman-5.1/metadata/news.idmap \
../../refman-5.1/metadata/optimization.idmap \
@@ -1286,8 +1284,7 @@
../../refman-5.1/metadata/stored-procedures.idmap \
../../refman-5.1/metadata/triggers.idmap \
../../refman-5.1/metadata/tutorial.idmap \
- ../../refman-5.1/metadata/views.idmap \
- ../../refman-6.0/metadata/mysql-cluster-cge.idmap
+ ../../refman-5.1/metadata/views.idmap
introduction.validpure: $(introduction_SOURCES)
introduction.titles: $(introduction_SOURCES)
introduction.useless: $(introduction_SOURCES)
@@ -1585,7 +1582,6 @@
language-structure-core.xml \
legalnotice.en.xml \
mysql-cluster-backup.xml \
- mysql-cluster-cge.xml \
mysql-cluster-configuration.xml \
mysql-cluster-disk-data.xml \
mysql-cluster-glossary.xml \
@@ -1778,7 +1774,6 @@
../../refman-5.1/metadata/introduction.idmap \
../../refman-5.1/metadata/language-structure-core.idmap \
../../refman-5.1/metadata/mysql-cluster-backup.idmap \
- ../../refman-5.1/metadata/mysql-cluster-cge.idmap \
../../refman-5.1/metadata/mysql-cluster-configuration.idmap \
../../refman-5.1/metadata/mysql-cluster-disk-data.idmap \
../../refman-5.1/metadata/mysql-cluster-glossary.idmap \
@@ -1832,8 +1827,7 @@
../../refman-5.1/metadata/tutorial.idmap \
../../refman-5.1/metadata/views.idmap \
../../refman-6.0/metadata/dba-core.idmap \
- ../../refman-6.0/metadata/manual.idmap \
- ../../refman-6.0/metadata/mysql-cluster-cge.idmap
+ ../../refman-6.0/metadata/manual.idmap
manual.validpure: $(manual_SOURCES)
manual.titles: $(manual_SOURCES)
manual.useless: $(manual_SOURCES)
@@ -1866,29 +1860,6 @@
mysql-cluster-backup-manprepped.xml: $(mysql_cluster_backup_SOURCES) $(mysql_cluster_backup_IDMAPS)
mysql-cluster-backup-remprepped.xml: $(mysql_cluster_backup_SOURCES) $(mysql_cluster_backup_IDMAPS)
-mysql_cluster_cge_INCLUDES = \
- ../common/fixedchars.ent \
- ../common/phrases.ent \
- ../refman-common/urls.ent \
- all-entities.ent \
- versions.ent
-mysql_cluster_cge_IMAGES =
-mysql_cluster_cge_SOURCES = mysql-cluster-cge.xml $(mysql_cluster_cge_INCLUDES)
-mysql_cluster_cge_IDMAPS = \
- ../../ndbapi/metadata/ndbapi.idmap \
- ../../refman-5.1/metadata/installing-core.idmap \
- ../../refman-5.1/metadata/mysql-cluster-news-core.idmap \
- ../../refman-5.1/metadata/news-5.1-core.idmap \
- ../../refman-6.0/metadata/mysql-cluster-cge.idmap
-mysql-cluster-cge.validpure: $(mysql_cluster_cge_SOURCES)
-mysql-cluster-cge.titles: $(mysql_cluster_cge_SOURCES)
-mysql-cluster-cge.useless: $(mysql_cluster_cge_SOURCES)
-mysql-cluster-cge.valid: $(mysql_cluster_cge_SOURCES) $(mysql_cluster_cge_IDMAPS)
-mysql-cluster-cge.validwarn: $(mysql_cluster_cge_SOURCES) $(mysql_cluster_cge_IDMAPS)
-mysql-cluster-cge-prepped.xml: $(mysql_cluster_cge_SOURCES) $(mysql_cluster_cge_IDMAPS)
-mysql-cluster-cge-manprepped.xml: $(mysql_cluster_cge_SOURCES) $(mysql_cluster_cge_IDMAPS)
-mysql-cluster-cge-remprepped.xml: $(mysql_cluster_cge_SOURCES) $(mysql_cluster_cge_IDMAPS)
-
mysql_cluster_configuration_INCLUDES = \
../common/fixedchars.ent \
../common/phrases.ent \
@@ -2058,8 +2029,8 @@
../../refman-5.1/metadata/mysql-cluster-multi-computer.idmap \
../../refman-5.1/metadata/mysql-cluster-process-management.idmap \
../../refman-5.1/metadata/mysql-cluster-security.idmap \
- ../../refman-5.1/metadata/mysql-cluster-utilities.idmap \
- ../../refman-5.1/metadata/programs-using.idmap
+ ../../refman-5.1/metadata/mysql-cluster-upgrade-downgrade.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-utilities.idmap
mysql-cluster-multi-computer.validpure: $(mysql_cluster_multi_computer_SOURCES)
mysql-cluster-multi-computer.titles: $(mysql_cluster_multi_computer_SOURCES)
mysql-cluster-multi-computer.useless: $(mysql_cluster_multi_computer_SOURCES)
@@ -2283,6 +2254,7 @@
../refman-common/images/published/ndb-size-pl-1.png
mysql_cluster_utilities_SOURCES = mysql-cluster-utilities.xml $(mysql_cluster_utilities_INCLUDES)
mysql_cluster_utilities_IDMAPS = \
+ ../../ndbapi/metadata/ndb-internals.idmap \
../../ndbapi/metadata/ndbapi.idmap \
../../refman-5.1/metadata/installing-core.idmap \
../../refman-5.1/metadata/mysql-cluster-backup.idmap \
@@ -2327,7 +2299,6 @@
dynxml-local-mysql-cluster-news.xml \
dynxml-local-mysql-cluster-optvar.xml \
mysql-cluster-backup.xml \
- mysql-cluster-cge.xml \
mysql-cluster-configuration.xml \
mysql-cluster-disk-data.xml \
mysql-cluster-glossary.xml \
@@ -2378,7 +2349,6 @@
../../refman-5.1/metadata/installing-core.idmap \
../../refman-5.1/metadata/introduction.idmap \
../../refman-5.1/metadata/mysql-cluster-backup.idmap \
- ../../refman-5.1/metadata/mysql-cluster-cge.idmap \
../../refman-5.1/metadata/mysql-cluster-configuration.idmap \
../../refman-5.1/metadata/mysql-cluster-disk-data.idmap \
../../refman-5.1/metadata/mysql-cluster-glossary.idmap \
@@ -2395,6 +2365,7 @@
../../refman-5.1/metadata/mysql-cluster-security.idmap \
../../refman-5.1/metadata/mysql-cluster-upgrade-downgrade.idmap \
../../refman-5.1/metadata/mysql-cluster-utilities.idmap \
+ ../../refman-5.1/metadata/mysql-cluster.idmap \
../../refman-5.1/metadata/news-5.1-core.idmap \
../../refman-5.1/metadata/partitioning.idmap \
../../refman-5.1/metadata/programs-client-core.idmap \
@@ -2402,8 +2373,7 @@
../../refman-5.1/metadata/replication-configuration.idmap \
../../refman-5.1/metadata/replication-notes.idmap \
../../refman-5.1/metadata/replication.idmap \
- ../../refman-5.1/metadata/sql-syntax.idmap \
- ../../refman-6.0/metadata/mysql-cluster-cge.idmap
+ ../../refman-5.1/metadata/sql-syntax.idmap
mysql-cluster.validpure: $(mysql_cluster_SOURCES)
mysql-cluster.titles: $(mysql_cluster_SOURCES)
mysql-cluster.useless: $(mysql_cluster_SOURCES)
Modified: trunk/it/refman-5.1/introduction.xml
===================================================================
--- trunk/it/refman-5.1/introduction.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/introduction.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 7, Lines Added: 60, Lines Deleted: 116; 8563 bytes
@@ -497,25 +497,7 @@
</formalpara>
</listitem>
-<!--
<listitem>
- <para>
- <emphasis role="bold">The Instance Manager (IM)</emphasis>
- now has some additional functionality: <literal>SHOW
- <replaceable>instance_name</replaceable> LOG FILES</literal>
- provides a listing of all log files, <literal>SHOW
- <replaceable>instance_name</replaceable> LOG {ERROR | SLOW |
- GENERAL} <replaceable>size</replaceable></literal> retrieves
- a part of the specified log file, and <literal>SET
- <replaceable>instance_name</replaceable>.<replaceable>option_name</replaceable>=<replaceable>option_value</replaceable></literal>
- sets an option to the specified value and writes it to the
- configuration file. See <xref linkend="instance-manager"/>.
- (Author: Petr Chardin)
- </para>
- </listitem>
--->
-
- <listitem>
<formalpara>
<title>Upgrade program</title>
@@ -586,6 +568,22 @@
<listitem>
<formalpara>
+ <title>MySQL Cluster NDB 6.x</title>
+
+ <para>
+ Many new features and other improvements have been made to
+ the <literal>NDBCLUSTER</literal> storage engine in MySQL
+ Cluster NDB 6.x (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition</quote>); for an overview of these,
+ see <xref linkend="mysql-cluster-roadmap"/>.
+ </para>
+
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+
<title>Backup of tablespaces</title>
<para>
@@ -682,24 +680,34 @@
<listitem>
<para>
- Improvements in the <literal>INFORMATION_SCHEMA</literal>
- database, with new columns added to
- <literal>INFORMATION_SCHEMA.ROUTINES</literal>, and the
- addition of the
- <literal>INFORMATION_SCHEMA.PARAMETERS</literal> table.
+ Support for additional Unicode character sets:
+ <literal>utf16</literal>, <literal>utf32</literal>, and
+ 4-byte <literal>utf8</literal>. These character sets
+ support supplementary Unicode characters; that is,
+ characters outside the Basic Multilingual Plane (BMP).
</para>
</listitem>
-<!--
<listitem>
<para>
- A tool for online backup.
+ <literal>BACKUP DATABASE</literal> and
+ <literal>RESTORE</literal> statements for backup and
+ restore operations.
</para>
</listitem>
--->
<listitem>
<para>
+ Improvements in the <literal>INFORMATION_SCHEMA</literal>
+ database, with the addition of the
+ <literal>INFORMATION_SCHEMA.PARAMETERS</literal> table,
+ and new columns added to
+ <literal>INFORMATION_SCHEMA.ROUTINES</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Optimizer enhancements for faster subqueries and joins,
including batched index access of table rows for sequences
of disjoint ranges by the <literal>MyISAM</literal> and
@@ -717,16 +725,27 @@
<listitem>
<para>
- The <literal>LOCK TABLE</literal> statement no longer
- commits transactions automatically. Following
- <literal>LOCK TABLE</literal>, you can now access tables
- not mentioned in the <literal>LOCK TABLE</literal>
- statement. You can now also issue <literal>LOCK
- TABLE</literal> many times in succession, adding
- additional tables to the locked set, and without unlocking
- any tables that were locked previously; tables are not
- unlocked until the transaction is committed.
+ The syntax for the <literal>LOCK TABLES</literal>
+ statement is extended to support transactional table locks
+ that do not commit transactions automatically. Following
+ <literal>LOCK TABLES ... IN SHARE MODE</literal> or
+ <literal>LOCK TABLES ... IN EXCLUSIVE MODE</literal>, you
+ can access tables not mentioned in the <literal>LOCK
+ TABLES</literal> statement. You can now also issue these
+ extended <literal>LOCK TABLES</literal> statements many
+ times in succession, adding additional tables to the
+ locked set, and without unlocking any tables that were
+ locked previously. When using <literal>LOCK
+ TABLES</literal> with <literal>IN SHARE MODE</literal> or
+ <literal>IN EXCLUSIVE MODE</literal>, tables are not
+ unlocked until the transaction ends.
</para>
+
+ <para>
+ The behavior of <literal>LOCK TABLES</literal> when not
+ using <literal>IN SHARE MODE</literal> or <literal>IN
+ EXCLUSIVE MODE</literal> remains unchanged.
+ </para>
</listitem>
<listitem>
@@ -746,83 +765,6 @@
</itemizedlist>
</para>
- <para>
- Several improvements for MySQL Cluster, made in &mccge-series;,
- will become generally available for MySQL Cluster in MySQL 6.0:
-
- <itemizedlist>
-
- <listitem>
- <para>
- Replication conflict detection and resolution.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Online <literal>ADD COLUMN</literal>, <literal>ADD
- INDEX</literal>, and <literal>DROP INDEX</literal>
- operations.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Batch operations, resulting in significant speed
- improvements.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Replication heartbeats, which enable real-time detection
- of replication failures and real-time failover.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The ability to bind client applications and replication
- slaves to specific network interfaces.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Enhancements to take advantage of real-time scheduling and
- to bind processes to specific CPUs on data node hosts
- having multiple processors.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <literal>NDB</literal> API supports a new
- <literal>NdbRecord</literal> interface.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The ability to use multiple cluster connections in
- <command>mysqld</command> using the
- <option>--ndb-cluster-connection-pool</option> option.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Backup status reporting.
- </para>
- </listitem>
-
- </itemizedlist>
-
- See <xref linkend="mysql-cluster-cge-differences"/> for
- additional &mccge-series; features that are expected to be made
- available in MySQL 6.0.
- </para>
-
<!--
<itemizedlist>
<listitem>
@@ -854,9 +796,10 @@
-->
<para>
- The following constructs are deprecated and have been removed in
- MySQL 6.0. Where alternatives are shown, applications should be
- updated to use them.
+ The following constructs are deprecated and have been removed
+ for MySQL 6.0 (they were actually removed in 5.2.5). Where
+ alternatives are shown, applications should be updated to use
+ them.
<itemizedlist>
@@ -1707,7 +1650,8 @@
<listitem>
<para>
- <literal>LIKE</literal> is allowed on numeric values.
+ <function role="sqlop">LIKE</function> is allowed on
+ numeric values.
</para>
</listitem>
Modified: trunk/it/refman-5.1/mysql-cluster-backup.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-backup.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-backup.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 5, Lines Added: 4, Lines Deleted: 13; 1889 bytes
@@ -652,9 +652,7 @@
unspecified and is subject to change without
notice</emphasis>. (Bug #24363)
</para>
-
- &mccge-warning-begin;
-
+
<para>
<indexterm>
<primary>attribute promotion (MySQL Cluster)</primary>
@@ -812,8 +810,6 @@
columns to <literal>BINARY</literal>.
</para>
</note>
-
- &mccge-warning-end-cluster;
<para>
The <option>-b</option> option is used to specify the ID or
@@ -1109,8 +1105,7 @@
<row>
<entry><option>--skip-table-check</option></entry>
<entry><option>-s</option></entry>
- <entry>Do not check table schemas (Added in MySQL 5.1.17; <emphasis>not
- supported in &mccge-series;</emphasis>)</entry>
+ <entry>Do not check table schemas (Added in MySQL 5.1.17)</entry>
<entry><literal>FALSE</literal></entry>
</row>
<row>
@@ -1123,9 +1118,7 @@
</tgroup>
</informaltable>
- &mccge-warning-unsupported-begin;
-
- <para>
+ <para>
Beginning with MySQL 5.1.18, several additional options are
available for use with the <option>--print_data</option>
option in generating data dumps, either to
@@ -1238,9 +1231,7 @@
</itemizedlist>
</para>
- &mccge-warning-end-cluster;
-
- <indexterm>
+ <indexterm>
<primary>ndb_restore</primary>
<secondary>errors</secondary>
</indexterm>
Modified: trunk/it/refman-5.1/mysql-cluster-configuration.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-configuration.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-configuration.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 43, Lines Added: 72, Lines Deleted: 156; 21250 bytes
@@ -81,31 +81,7 @@
<xref linkend="installing-source-tree"/>.
</para>
- &mccge-warning-begin;
-
- <warning>
- <para>
- <command>BUILD/compile-pentium-max</command> by default builds
- the MySQL Server with support for the <literal>InnoDB</literal>
- storage engine. <emphasis>You must not deploy or make use of
- &mccge-series; employing the <literal>InnoDB</literal> storage
- engine without prior written permission to do so from MySQL
- AB</emphasis>.
- </para>
-
- <para>
- If you wish to use <literal>InnoDB</literal> technology in
- conjunction with your use of &mccge-series; and do not already
- have authorization to do so as part of your MySQL Server
- license, contact your MySQL AB salesperson or other authorized
- MySQL AB representative for assistance in upgrading your MySQL
- Server license.
- </para>
- </warning>
-
- &mccge-warning-end-cluster;
-
- <para>
+ <para>
<command>BUILD/compile-pentium-max</command> also includes
OpenSSL, so you must either have or obtain OpenSSL to build
successfully, or else modify
@@ -1212,11 +1188,10 @@
</para>
<para>
- Beginning with MySQL 5.1.16
- (<emphasis>&mccge-series;</emphasis>: MySQL
- 5.1.15-ndb-6.1.3), it is possible to disable arbitration
- completely by setting <literal>ArbitrationRank</literal> to
- 0 on all management and SQL nodes.
+ Beginning with MySQL 5.1.16 and MySQL Cluster NDB 6.1.3, it
+ is possible to disable arbitration completely by setting
+ <literal>ArbitrationRank</literal> to 0 on all management
+ and SQL nodes.
</para>
</listitem>
@@ -1417,10 +1392,7 @@
</listitem>
<listitem>
-
- &mccge-warning-begin;
-
- <para id="mysql-cluster-param-ndbd-definition-tcpbind-inaddr-any">
+ <para id="mysql-cluster-param-ndbd-definition-tcpbind-inaddr-any">
<literal>TcpBind_INADDR_ANY</literal>
</para>
@@ -1433,13 +1405,10 @@
</para>
<para>
- This parameter was added in MySQL 5.1.16-ndb-6.2.0.
+ This parameter was added in MySQL Cluster NDB 6.2.0.
</para>
+ </listitem>
- &mccge-warning-end-cluster;
-
- </listitem>
-
<listitem>
<indexterm>
<primary>NoOfReplicas</primary>
@@ -1676,20 +1645,14 @@
4</literal> new pages are allocated, so the total number of
pages allocated to the table is now 22.
</para>
-
- &mccge-warning-begin;
-
+
<note>
<para>
The <quote>18.75% + 1</quote> overhead is no longer
- required in &mccge-series;
- 6.2.<replaceable>x</replaceable> and
- 6.3.<replaceable>x</replaceable> releases, beginning with
- MySQL 5.1.19-ndb-6.2.3 and MySQL 5.1.19-ndb-6.3.0.
+ required beginning with MySQL Cluster NDB 6.2.3 and MySQL
+ Cluster NDB 6.3.0.
</para>
</note>
-
- &mccge-warning-end-cluster;
<para>
Once a page has been allocated, it is currently not possible
@@ -2389,9 +2352,8 @@
</para>
<para>
- This parameter was introduced in MySQL 5.1.20, and in
- &mccge-series;, in MySQL 5.1.15-ndb-6.1.12 and MySQL
- 5.1.19-ndb-6.2.3.
+ This parameter was introduced in MySQL 5.1.20, MySQL Cluster NDB
+ 6.1.12 and MySQL MySQL Cluster NDB 6.2.3.
</para>
<formalpara>
@@ -2478,10 +2440,8 @@
<indexterm>
<primary>FragmentLogFileSize</primary>
</indexterm>
-
- &mccge-warning-begin;
-
- <para id="mysql-cluster-param-ndbd-definition-fragmentlogfilesize">
+
+ <para id="mysql-cluster-param-ndbd-definition-fragmentlogfilesize">
<literal>FragmentLogFileSize</literal>
</para>
@@ -2489,12 +2449,9 @@
Setting this parameter allows you to control directly the
size of redo log files. The default is
<literal>16M</literal>. This parameter was added in MySQL
- 5.1.15-ndb-6.1.11.
+ MySQL Cluster NDB 6.1.11.
</para>
-
- &mccge-warning-end-cluster;
-
- </listitem>
+ </listitem>
<listitem>
<indexterm>
@@ -2796,9 +2753,9 @@
</para>
<para>
- Beginning with MySQL 5.1.15 (&mccge-series;: MySQL
- 5.1.15-ndb-6.1.1), this parameter takes one of the integer
- values <literal>0</literal>, <literal>1</literal>, or
+ Beginning with MySQL 5.1.15 and MySQL Cluster NDB 6.1.1,
+ this parameter takes one of the integer values
+ <literal>0</literal>, <literal>1</literal>, or
<literal>2</literal>, which act as follows:
</para>
@@ -2836,13 +2793,12 @@
<important>
<para>
- Beginning with MySQL 5.1.15 (&mccge-series;: MySQL
- 5.1.15-ndb-6.1.1), it is no longer possible to use
- <literal>true</literal> or <literal>false</literal> for
- the value of this parameter; when upgrading from a
- previous version, you must change the value to
- <literal>0</literal>, <literal>1</literal>, or
- <literal>2</literal>.
+ Beginning with MySQL 5.1.15 and MySQL Cluster NDB 6.1.1,
+ it is no longer possible to use <literal>true</literal>
+ or <literal>false</literal> for the value of this
+ parameter; when upgrading from a previous version, you
+ must change the value to <literal>0</literal>,
+ <literal>1</literal>, or <literal>2</literal>.
</para>
</important>
</para>
@@ -2924,9 +2880,8 @@
<warning>
<para>
- When using MySQL Cluster or &mccge-series; on Linux,
- <literal>ODirect</literal> should be enabled for 2.6 or
- newer kernels.
+ When using MySQL Cluster Linux, <literal>ODirect</literal>
+ should be enabled for 2.6 or newer kernels.
</para>
</warning>
@@ -2943,19 +2898,19 @@
<listitem>
<para>
- MySQL 5.1.15-ndb-6.1.11
+ MySQL Cluster NDB 6.1.11
</para>
</listitem>
<listitem>
<para>
- MySQL 5.1.19-ndb-6.2.3
+ MySQL Cluster NDB 6.2.3
</para>
</listitem>
<listitem>
<para>
- MySQL 5.1.19-ndb-6.3.0
+ MySQL Cluster NDB 6.3.0
</para>
</listitem>
@@ -2995,9 +2950,7 @@
<para id="mysql-cluster-param-ndbd-definition-compressedbackup">
<literal>CompressedBackup</literal>
</para>
-
- &mccge-warning-begin;
-
+
<para>
Setting this parameter to <literal>1</literal> causes backup
files to be compressed. The compression used is equivalent
@@ -3022,7 +2975,7 @@
</para>
<para>
- This parameter was introduced in MySQL 5.1.23-ndb-6.3.7.
+ This parameter was introduced in MySQL Cluster NDB 6.3.7.
</para>
</listitem>
@@ -3034,9 +2987,7 @@
<para id="mysql-cluster-param-ndbd-definition-compressedlcp">
<literal>CompressedLCP</literal>
</para>
-
- &mccge-warning-begin;
-
+
<para>
Setting this parameter to <literal>1</literal> causes local
checkpoint files to be compressed. The compression used is
@@ -3062,13 +3013,11 @@
</para>
<para>
- This parameter was introduced in MySQL 5.1.23-ndb-6.3.7.
+ This parameter was introduced in MySQL Cluster NDB 6.3.7.
</para>
</listitem>
</itemizedlist>
-
- &mccge-warning-end-cluster;
<para id="mysql-cluster-timeouts-intervals-disk-paging">
<emphasis role="bold">Controlling Timeouts, Intervals, and Disk
@@ -3354,10 +3303,8 @@
<indexterm>
<primary>TimeBetweenEpochs</primary>
</indexterm>
-
- &mccge-warning-begin;
- <para id="mysql-cluster-param-ndbd-definition-timebetweenepochs">
+ <para id="mysql-cluster-param-ndbd-definition-timebetweenepochs">
<literal>TimeBetweenEpochs</literal>
</para>
@@ -3371,20 +3318,15 @@
<literal>TimeBetweenEpochs</literal> is part of the
implementation of <quote>micro-GCPs</quote>, which can be
used to improve the performance of MySQL Cluster
- Replication. This parameter was introduced in
- MySQL-5.1.22-ndb-6.2.5 and MySQL 5.1.22-ndb-6.3.2.
+ Replication. This parameter was introduced in MySQL Cluster
+ NDB 6.2.5 and MySQL Cluster NDB 6.3.2.
</para>
-
- &mccge-warning-end-cluster;
-
- </listitem>
+ </listitem>
<listitem>
<indexterm>
<primary>TimeBetweenEpochsTimeout</primary>
</indexterm>
-
- &mccge-warning-begin;
<para id="mysql-cluster-param-ndbd-definition-timebetweenepochstimeout">
<literal>TimeBetweenEpochsTimeout</literal>
@@ -3402,21 +3344,16 @@
<literal>TimeBetweenEpochsTimeout</literal> is part of the
implementation of <quote>micro-GCPs</quote>, which can be
used to improve the performance of MySQL Cluster
- Replication. This parameter was introduced in
- MySQL-5.1.22-ndb-6.2.7 and MySQL 5.1.22-ndb-6.3.4.
+ Replication. This parameter was introduced in MySQL-MySQL
+ Cluster NDB 6.2.7 and MySQL Cluster NDB 6.3.4.
</para>
-
- &mccge-warning-end-cluster;
-
</listitem>
<listitem>
<indexterm>
<primary>MaxBufferedEpochs</primary>
</indexterm>
-
- &mccge-warning-begin;
-
+
<para id="mysql-cluster-param-ndbd-definition-maxbufferedepochs">
<literal>MaxBufferedEpochs</literal>
</para>
@@ -3445,9 +3382,6 @@
events in the binlog), forcing the client to reconnect or
restart the process.
</para>
-
- &mccge-warning-end-cluster;
-
</listitem>
<listitem>
@@ -4238,8 +4172,8 @@
</para>
<para>
- This parameter was added in MySQL Cluster 5.1.16.
- (&mccge-series;: MySQL Cluster 5.1.14-ndb-6.1.0).
+ This parameter was added in MySQL Cluster 5.1.16 and MySQL
+ Cluster NDB 6.1.0.
</para>
</listitem>
@@ -4362,9 +4296,7 @@
<indexterm>
<primary>BackupReportFrequency</primary>
</indexterm>
-
- &mccge-warning-begin;
-
+
<para id="mysql-cluster-param-ndbd-definition-backupreportfrequency">
This parameter controls how often backup status reports are
issued in the management client during a backup, as well as
@@ -4381,12 +4313,9 @@
</para>
<para>
- This parameter was added in MySQL 5.1.19-ndb-6.2.3.
+ This parameter was added in MySQL Cluster NDB 6.2.3.
</para>
-
- &mccge-warning-end-cluster;
-
- </listitem>
+ </listitem>
<listitem>
<indexterm>
@@ -4461,8 +4390,6 @@
</para>
</important>
- &mccge-warning-begin;
-
<para id="mysql-cluster-realtime-performance-parameters">
<emphasis role="bold">Realtime Performance Parameters</emphasis>
</para>
@@ -4471,7 +4398,7 @@
The <literal>[ndbd]</literal> parameters discussed in this
section are used in scheduling and locking of threads to
specific CPUs on multiprocessor data node hosts. They were
- introduced in MySQL 5.1.22-ndb-6.3.4.
+ introduced in MySQL Cluster NDB 6.3.4.
</para>
<itemizedlist>
@@ -4575,13 +4502,6 @@
</itemizedlist>
- <remark role="TODO">
- [js] Uncomment the following if and when more non-CGE material
- is added past this point.
- </remark>
-
-<!-- &mccge-warning-end-cluster; -->
-
</section>
<section id="mysql-cluster-api-definition">
@@ -4720,11 +4640,10 @@
</para>
<para>
- Beginning with MySQL 5.1.16
- (<emphasis>&mccge-series;</emphasis>: MySQL
- 5.1.15-ndb-6.1.3), it is possible to disable arbitration
- completely by setting <literal>ArbitrationRank</literal> to
- 0 on all management and SQL nodes.
+ Beginning with MySQL 5.1.16 and MySQL Cluster NDB 6.1.3, it
+ is possible to disable arbitration completely by setting
+ <literal>ArbitrationRank</literal> to 0 on all management
+ and SQL nodes.
</para>
</listitem>
@@ -5721,7 +5640,7 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-backupreportfrequency">BackupReportFrequency</link></literal>
- (Added in MySQL 5.1.19-ndb-6.2.3)</entry>
+ (Added in MySQL Cluster NDB 6.2.3)</entry>
<entry>seconds</entry>
<entry>0</entry>
<entry>0</entry>
@@ -5754,7 +5673,7 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-compressedbackup">CompressedBackup</link></literal>
- (Added in MySQL 5.1.23-ndb-6.3.7)</entry>
+ (Added in MySQL Cluster NDB 6.3.7)</entry>
<entry>boolean</entry>
<entry>0</entry>
<entry>0</entry>
@@ -5763,7 +5682,7 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-compressedlcp">CompressedLCP</link></literal>
- (Added in MySQL 5.1.23-ndb-6.3.7)</entry>
+ (Added in MySQL Cluster NDB 6.3.7)</entry>
<entry>boolean</entry>
<entry>0</entry>
<entry>0</entry>
@@ -5841,7 +5760,7 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-filesystempath">FileSystemPath</link></literal>
- (Added in MySQL-5.1.15-ndb-6.1.11)</entry>
+ (Added in MySQL-MySQL Cluster NDB 6.1.11)</entry>
<entry>string</entry>
<entry>value specified for <literal>DataDir</literal></entry>
<entry>N/A</entry>
@@ -5907,7 +5826,7 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-lockexecutethreadtocpu">LockExecuteThreadToCPU</link></literal>
- (Added in MySQL-5.1.22-ndb-6.3.4)</entry>
+ (Added in MySQL-MySQL Cluster NDB 6.3.4)</entry>
<entry>integer</entry>
<entry>65535</entry>
<entry>0</entry>
@@ -5916,7 +5835,7 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-lockmaintthreadstocpu">LockMaintThreadsToCPU</link></literal>
- (Added in MySQL-5.1.22-ndb-6.3.4)</entry>
+ (Added in MySQL-MySQL Cluster NDB 6.3.4)</entry>
<entry>integer</entry>
<entry>65535</entry>
<entry>0</entry>
@@ -5925,9 +5844,8 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory">LockPagesInMainMemory</link></literal></entry>
- <entry><emphasis>As of MySQL 5.1.15 (&mccge-series;: MySQL
- 5.1.15-ndb-6.1.1)</emphasis>: integer;
- <emphasis>previously</emphasis>: true|false
+ <entry><emphasis>As of MySQL 5.1.15 and MySQL Cluster NDB 6.1.1</emphasis>:
+ integer; <emphasis>previously</emphasis>: true|false
(<literal>1</literal>|<literal>0</literal>)</entry>
<entry>0</entry>
<entry>0</entry>
@@ -6016,8 +5934,8 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-maxallocate">MaxAllocate</link></literal>
- (Added in MySQL 5.1.15-ndb-6.1.12 and MySQL
- 5.1.19-ndb-6.2.3)</entry>
+ (Added in MySQL Cluster NDB 6.1.12 and MySQL MySQL
+ Cluster NDB 6.2.3)</entry>
<entry>integer</entry>
<entry>32M</entry>
<entry>1M</entry>
@@ -6026,7 +5944,7 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-maxbufferedepochs">MaxBufferedEpochs</link></literal>
- (Added in MySQL 5.1.15-ndb-6.2.14)</entry>
+ (Added in MySQL Cluster NDB 6.2.14)</entry>
<entry>integer</entry>
<entry>100</entry>
<entry>0</entry>
@@ -6159,8 +6077,7 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-memreportfrequency">MemReportFrequency</link></literal>
- (added in MySQL 5.1.16; &mccge-series;: added in MySQL
- 5.1.14-ndb-6.1.0)</entry>
+ (Added in MySQL 5.1.16 and MySQL Cluster NDB 6.1.0)</entry>
<entry>integer (seconds)</entry>
<entry>0</entry>
<entry>0</entry>
@@ -6229,7 +6146,7 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-realtimescheduler">RealTimeScheduler</link></literal>
- (Added in MySQL 5.1.22-ndb-6.3.4)</entry>
+ (Added in MySQL Cluster NDB 6.3.4)</entry>
<entry>boolean</entry>
<entry>0</entry>
<entry>0</entry>
@@ -6255,7 +6172,7 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-schedulerexecutiontimer">SchedulerExecutionTimer</link></literal>
- (added in MySQL 5.1.22-ndb-6.3.4)</entry>
+ (added in MySQL Cluster NDB 6.3.4)</entry>
<entry>μseconds (integer)</entry>
<entry>50</entry>
<entry>0</entry>
@@ -6264,7 +6181,7 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-schedulerspintimer">SchedulerSpinTimer</link></literal>
- (added in MySQL 5.1.22-ndb-6.3.4)</entry>
+ (added in MySQL Cluster NDB 6.3.4)</entry>
<entry>μseconds (integer)</entry>
<entry>0</entry>
<entry>0</entry>
@@ -6333,8 +6250,7 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-tcpbind-inaddr-any">TcpBind_INADDR_ANY</link></literal>
- (<emphasis>&mccge-series; only</emphasis>: added in
- MySQL 5.1.16-ndb-6.2.0)</entry>
+ (Added in MySQL Cluster NDB 6.2.0)</entry>
<entry>true|false (<literal>1</literal>|<literal>0</literal>)</entry>
<entry>1</entry>
<entry>0</entry>
@@ -6343,8 +6259,8 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-timebetweenepochs">TimeBetweenEpochs</link></literal>
- (<emphasis>&mccge-series; only</emphasis>: added in
- MySQL 5.1.22-ndb-6.2.5 and MySQL 5.1.22-ndb-6.3.2)</entry>
+ (Added in MySQL Cluster NDB 6.2.5 and MySQL Cluster NDB
+ 6.3.2)</entry>
<entry>milliseconds</entry>
<entry>100</entry>
<entry>0</entry>
@@ -6353,8 +6269,8 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-timebetweenepochstimeout">TimeBetweenEpochsTimeout</link></literal>
- (<emphasis>&mccge-series; only</emphasis>: added in
- MySQL 5.1.22-ndb-6.2.7 and MySQL 5.1.22-ndb-6.3.4)</entry>
+ (Added in MySQL Cluster NDB 6.2.7 and MySQL Cluster NDB
+ 6.3.4)</entry>
<entry>milliseconds</entry>
<entry>4000</entry>
<entry>0</entry>
Modified: trunk/it/refman-5.1/mysql-cluster-disk-data.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-disk-data.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-disk-data.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 3, Lines Added: 6, Lines Deleted: 11; 1892 bytes
@@ -339,13 +339,10 @@
</para>
<note>
-
- &mccge-warning-begin;
-
<para>
- Beginning with MySQL 5.1.19-ndb-6.2.5 and MySQL
- 5.1.20-ndb-6.3.2, it is also possible to specify whether an
- individual column is stored on disk or in memory by using a
+ Beginning with MySQL Cluster NDB 6.2.5 and MySQL Cluster NDB
+ 6.3.2, it is also possible to specify whether an individual
+ column is stored on disk or in memory by using a
<literal>STORAGE</literal> clause as part of the column's
definition in a <literal>CREATE TABLE</literal> or
<literal>ALTER TABLE</literal> statement. <literal>STORAGE
@@ -354,9 +351,7 @@
to be used. See <xref linkend="create-table"/>, for more
information.
</para>
-
- &mccge-warning-end-cluster;
- </note>
+ </note>
<para>
Once table <literal>ts_1</literal> has been created as shown,
@@ -375,8 +370,8 @@
belonging to these columns is stored in RAM. In MySQL 5.1,
only non-indexed columns can be held on disk; indexes and
indexed column data continue to be stored in memory. This
- tradeoff between the use of indexes and conservation of RAM
- is something you must keep in mind as you design Disk Data
+ tradeoff between the use of indexes and conservation of RAM is
+ something you must keep in mind as you design Disk Data
tables.
</para>
</listitem>
Modified: trunk/it/refman-5.1/mysql-cluster-glossary.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-glossary.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-glossary.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 1, Lines Added: 44, Lines Deleted: 0; 2143 bytes
@@ -707,6 +707,50 @@
</para>
</listitem>
+ <listitem>
+ <formalpara>
+
+ <title>Angel process</title>
+
+ <para>
+ When a data node is started, <command>ndbd</command> actually
+ starts two processes. One of these is known as the
+ <quote>angel</quote> process; its purpose is to check to make
+ sure that the main <command>ndbd</command> process continues
+ to run, and to restart the main process if it should stop for
+ any reason.
+ </para>
+
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+
+ <title>Watchdog thread</title>
+
+ <para>
+ Each <command>ndbd</command> process has an internal
+ <firstterm>watchdog thread</firstterm> which monitors the main
+ worker thread, ensuring forward progress and a timely response
+ to cluster protocols such as the cluster heartbeat. If the
+ <command>ndbd</command> process is not being woken up promptly
+ by the operating system when its sleep time expires,
+ <literal>INFO</literal> and <literal>WARNING</literal> events,
+ which are identifiable because they contain
+ <quote>Watchdog:...</quote>, are written to the cluster log.
+ Such messages are usually a symptom of an overloaded system;
+ you should see what else is running on the system, and whether
+ the ndbd <command>process</command> is being swapped out to
+ disk. If <command>ndbd</command> cannot wake up regularly then
+ it cannot respond to heartbeat messages on time, and other
+ nodes eventually consider it <quote>dead</quote> due to the
+ missed heartbeats, causing it to be excluded from the cluster.
+ </para>
+
+ </formalpara>
+ </listitem>
+
</itemizedlist>
</section>
Modified: trunk/it/refman-5.1/mysql-cluster-interconnects.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-interconnects.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-interconnects.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 5, Lines Added: 19, Lines Deleted: 121; 7442 bytes
@@ -229,7 +229,7 @@
<filename>DIS_GPL_2_5_0_SEP_10_2004.tar.gz</filename> and
<filename>SCI_SOCKET_2_3_0_OKT_01_2004.tar.gz</filename>. You
should be able to find these (or possibly newer versions) at
- <ulink url="http://www.dolphinics.no/support/downloads.html"/>.
+ <ulink url="http://www.dolphinics.com/support/downloads.html"/>.
</para>
<formalpara>
@@ -503,22 +503,21 @@
shell> <userinput>./status.sh</userinput>
</programlisting>
- <remark role="todo">
- Document switches for ksocketconfig script, or provide a pointer
- to same. [js]
- </remark>
-
<para>
If you discover an error and need to change the SCI socket
configuration, it is necessary to use
<command>ksocketconfig</command> to accomplish this task:
- </para>
<programlisting>
shell> <userinput>cd /opt/DIS/util</userinput>
shell> <userinput>./ksocketconfig -f</userinput>
</programlisting>
+ For more information about <command>ksocketconfig</command>,
+ consult the documentation available from
+ <ulink url="http://www.dolphinics.com/support/documentation.html"/>.
+ </para>
+
<formalpara>
<title>Testing the setup</title>
@@ -609,9 +608,9 @@
</section>
- <section id="mysql-cluster-performance-figures">
+ <section id="mysql-cluster-interconnects-performance">
- <title>Understanding the Impact of Cluster Interconnects</title>
+ <title>MySQL Cluster Interconnects and Performance</title>
<indexterm>
<primary>MySQL Cluster</primary>
@@ -713,110 +712,13 @@
</itemizedlist>
<para>
- To check the base performance of these access methods, we have
- developed a set of benchmarks. One such benchmark,
- <command>testReadPerf</command>, tests simple and batched primary
- and unique key accesses. This benchmark also measures the setup
- cost of range scans by issuing scans returning a single record.
- There is also a variant of this benchmark which uses a range scan
- to fetch a batch of records.
- </para>
-
- <para>
- In this way, we can determine the cost of both a single key access
- and a single record scan access, as well as measure the impact of
- the communication media used, on base access methods.
- </para>
-
- <remark role="todo">
- How current are these figures? [js]
- </remark>
-
- <para>
- In our tests, we ran the base benchmarks for both a normal
- transporter using TCP/IP sockets and a similar setup using SCI
- sockets. The figures reported in the following table are for small
- accesses of 20 records per access. The difference between serial
- and batched access decreases by a factor of 3 to 4 when using 2KB
- records instead. SCI Sockets were not tested with 2KB records.
- Tests were performed on a cluster with 2 data nodes running on 2
- dual-CPU machines equipped with AMD MP1900+ processors.
- </para>
-
- <informaltable>
- <tgroup cols="3">
- <colspec colwidth="33*"/>
- <colspec colwidth="34*"/>
- <colspec colwidth="33*"/>
- <tbody>
- <row>
- <entry><emphasis role="bold">Access Type</emphasis></entry>
- <entry><emphasis role="bold">TCP/IP Sockets</emphasis></entry>
- <entry><emphasis role="bold">SCI Socket</emphasis></entry>
- </row>
- <row>
- <entry>Serial pk access</entry>
- <entry>400 microseconds</entry>
- <entry>160 microseconds</entry>
- </row>
- <row>
- <entry>Batched pk access</entry>
- <entry>28 microseconds</entry>
- <entry>22 microseconds</entry>
- </row>
- <row>
- <entry>Serial uk access</entry>
- <entry>500 microseconds</entry>
- <entry>250 microseconds</entry>
- </row>
- <row>
- <entry>Batched uk access</entry>
- <entry>70 microseconds</entry>
- <entry>36 microseconds</entry>
- </row>
- <row>
- <entry>Indexed eq-bound</entry>
- <entry>1250 microseconds</entry>
- <entry>750 microseconds</entry>
- </row>
- <row>
- <entry>Index range</entry>
- <entry>24 microseconds</entry>
- <entry>12 microseconds</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <indexterm>
- <primary>MySQL Cluster</primary>
- <secondary>SCI, performance <foreignphrase>vs</foreignphrase> TCP/IP</secondary>
- </indexterm>
-
- <para>
- We also performed another set of tests to check the performance of
- SCI Sockets <foreignphrase>vis-à-vis</foreignphrase> that of the
- SCI transporter, and both of these as compared with the TCP/IP
- transporter. All these tests used primary key accesses either
- serially and multi-threaded, or multi-threaded and batched.
- </para>
-
- <para>
- The tests showed that SCI sockets were about 100% faster than
- TCP/IP. The SCI transporter was faster in most cases compared to
- SCI sockets. One notable case occurred with many threads in the
- test program, which showed that the SCI transporter did not
- perform very well when used for the <command>mysqld</command>
- process.
- </para>
-
- <para>
- Our overall conclusion was that, for most benchmarks, using SCI
- sockets improves performance by approximately 100% over TCP/IP,
- except in rare instances when communication performance is not an
- issue. This can occur when scan filters make up most of processing
- time or when very large batches of primary key accesses are
- achieved. In that case, the CPU processing in the
+ With benchmarks developed internally by MySQL for testing simple
+ and batched primary and unique key accesses, we have found that
+ using SCI sockets improves performance by approximately 100% over
+ TCP/IP, except in rare instances when communication performance is
+ not an issue. This can occur when scan filters make up most of
+ processing time or when very large batches of primary key accesses
+ are achieved. In that case, the CPU processing in the
<command>ndbd</command> processes becomes a fairly large part of
the overhead.
</para>
@@ -838,17 +740,13 @@
as well.)
</para>
- <remark role="todo">
- Provide links to these? (Not high priority item.) [js]
- </remark>
-
<para>
There are several other optimized socket implementations for
computer clusters, including Myrinet, Gigabit Ethernet, Infiniband
- and the VIA interface. We have tested MySQL Cluster so far only
- with SCI sockets. See <xref linkend="mysql-cluster-sci-sockets"/>
- for information on how to set up SCI sockets using ordinary TCP/IP
- for MySQL Cluster.
+ and the VIA interface. However, we have tested MySQL Cluster so
+ far only with SCI sockets. See
+ <xref linkend="mysql-cluster-sci-sockets"/>, for information on
+ how to set up SCI sockets using ordinary TCP/IP for MySQL Cluster.
</para>
</section>
Modified: trunk/it/refman-5.1/mysql-cluster-limitations.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-limitations.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-limitations.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 12, Lines Added: 37, Lines Deleted: 76; 9111 bytes
@@ -16,26 +16,16 @@
</indexterm>
<para>
- In the sections that follow, we discuss known limitations in MySQL
- ¤t-series; Cluster and &mccge-series; releases as compared
- with the features available when using the <literal>MyISAM</literal>
- and <literal>InnoDB</literal> storage engines. Currently, there are
- no plans to address these in coming releases of MySQL
- ¤t-series; or &mccge-series;; however, we will attempt to
- supply fixes for these issues in subsequent release series. If you
- check the <quote>Cluster</quote> category in the MySQL bugs database
- at <ulink url="http://bugs.mysql.com"/>, you can find known bugs
- which (if marked <quote>¤t-series;</quote>) we intend to
- correct in upcoming releases of MySQL ¤t-series;.
- </para>
+ In the sections that follow, we discuss known limitations in current
+ releases pf MySQL Cluster as compared with the features available
+ when using the <literal>MyISAM</literal> and
+ <literal>InnoDB</literal> storage engines. If you check the
+ <quote>Cluster</quote> category in the MySQL bugs database at
+ <ulink url="http://bugs.mysql.com"/>, you can find known bugs in the
+ following categories under <quote>MySQL Server:</quote> in the MySQL
+ bugs database at <ulink url="http://bugs.mysql.com"/>, which we
+ intend to correct in upcoming releases of MySQL Cluster:
- <para>
- If you check the following categories under <quote>MySQL
- Server:</quote> in the MySQL bugs database at
- <ulink url="http://bugs.mysql.com"/>, you can find known bugs which
- (if marked <quote>¤t-series;</quote>) we intend to correct in
- upcoming releases of MySQL ¤t-series;:
-
<itemizedlist>
<listitem>
@@ -66,11 +56,6 @@
</para>
<para>
- Some of these issues may be addressed in &mccge-series; and the
- fixes included in a future mainline MySQL Cluster version.
- </para>
-
- <para>
This information is intended to be complete with respect to the
conditions just set forth. You can report any discrepancies that you
encounter to the MySQL bugs database using the instructions given in
@@ -426,19 +411,14 @@
rolling restart of the cluster. See
<xref linkend="mysql-cluster-rolling-restart"/>.
</para>
-
- &mccge-warning-begin;
-
+
<para>
- In MySQL 5.1.23-ndb-6.3.7 and later &mccge-series;
- 6.3.<replaceable>x</replaceable> releases, this
+ Beginning with MySQL Cluster NDB 6.3.7, this
limitation can be overcome using <literal>OPTIMIZE
TABLE</literal>. See
<xref linkend="mysql-cluster-limitations-resolved"/>,
for more information.
</para>
-
- &mccge-warning-end-cluster;
</listitem>
<listitem>
@@ -562,21 +542,16 @@
<listitem>
<para>
The maximum number of metadata objects in
- MySQL ¤t-series; Cluster and
- &mccge-series; is 20320. This limit is
- hard-coded.
+ current versions of MySQL Cluster. This
+ limit is hard-coded.
</para>
</listitem>
</itemizedlist>
- <note>
- <para role="mccge-warning">
- &mccge-series; users should see
- <xref linkend="mysql-cluster-limitations-resolved"/>,
- for more information.
- </para>
- </note>
+ See
+ <xref linkend="mysql-cluster-limitations-resolved"/>,
+ for more information.
</para>
</formalpara>
@@ -897,9 +872,8 @@
<note>
<para>
- This issue was fixed in MySQL 5.1.23. (In
- &mccge-series;, the issue was fixed in MySQL
- 5.1.22-ndb-6.2.7 and MySQL 5.1.22-ndb-6.3.4.)
+ This issue was fixed in MySQL 5.1.23, MySQL Cluster
+ NDB 6.2.7, and MySQL Cluster NDB 6.3.4.
</para>
</note>
</para>
@@ -1006,18 +980,13 @@
</para>
</formalpara>
-
- &mccge-warning-begin;
-
+
<para>
- In MySQL 5.1.23-ndb-6.3.7 and later &mccge-series;
- 6.3.<replaceable>x</replaceable> releases, this limitation
- has been lifted. See
+ Beginning with MySQL Cluster NDB 6.3.7, this limitation has
+ been lifted. See
<xref linkend="mysql-cluster-limitations-resolved"/>, for
more information.
</para>
-
- &mccge-warning-end-cluster;
</listitem>
<listitem>
@@ -1526,9 +1495,9 @@
While it is possible to run multiple cluster processes
concurrently on a single host, it is not always advisable to do
so for reasons of performance and high availability, as well as
- other considerations. In particular, in MySQL ¤t-series;
- or &mccge-series;, we do not support for production use any
- MySQL Cluster deployment in which more than one
+ other considerations. In particular, in MySQL 5.1 and MySQL
+ Cluster NDB 6.x, we do not support for production use any MySQL
+ Cluster deployment in which more than one
<command>ndbd</command> process is run on a single physical
machine.
@@ -1536,8 +1505,8 @@
<para>
We may support multiple data nodes per host in a future
MySQL release, following additional testing. However, in
- MySQL ¤t-series; and &mccge-series;, such
- configurations can be considered experimental only.
+ current versions of MySQL Cluster, such configurations can
+ be considered experimental only.
</para>
</note>
</para>
@@ -1585,8 +1554,7 @@
<para>
A number of limitations and related issues existing in earlier
- versions of MySQL Cluster have been resolved over the course of
- development of MySQL ¤t-series; or &mccge-series;:
+ versions of MySQL Cluster have been resolved:
<itemizedlist>
@@ -1840,14 +1808,12 @@
</listitem>
<listitem>
-
- &mccge-warning-begin;
- <formalpara>
+ <formalpara>
<title>Maximum number of cluster nodes</title>
<para>
- Prior to MySQL 5.1.15-ndb-6.1.1, the total maximum number
+ Prior to MySQL Cluster NDB 6.1.1, the total maximum number
of nodes in a MySQL Cluster was 63, including all SQL
nodes (MySQL Servers), API nodes (applications accessing
the cluster other than MySQL servers), data nodes, and
@@ -1857,30 +1823,28 @@
</formalpara>
<para>
- Starting with MySQL 5.1.15-ndb-6.1.1, up to 255 API nodes
+ Starting with MySQL Cluster NDB 6.1.1, up to 255 API nodes
(including MySQL servers acting as cluster SQL nodes) are
supported by a single cluster. The total number of data
nodes and management nodes beginning with this version is
63, of which up to 48 can be data nodes.
</para>
- <para>
- The limitation that a data node cannot have a node ID
- greater than 49 continues to apply in &mccge-series;.
- </para>
-
- &mccge-warning-end-cluster;
+ <note>
+ <para>
+ The limitation that a data node cannot have a node ID
+ greater than 49 continues to apply.
+ </para>
+ </note>
</listitem>
<listitem>
- &mccge-warning-begin;
-
<formalpara>
<title>Recovery of memory from deleted rows</title>
<para>
- Beginning with MySQL 5.1.23-ndb-6.3.7, memory can be
+ Beginning with MySQL Cluster NDB 6.3.7, memory can be
reclaimed from an <literal>NDB</literal> table for reuse
with any <literal>NDB</literal> table by employing
<literal>OPTIMIZE TABLE</literal>, subject to the
@@ -1936,9 +1900,6 @@
</para>
</formalpara>
-
-
- &mccge-warning-end-cluster;
</listitem>
</itemizedlist>
Modified: trunk/it/refman-5.1/mysql-cluster-management.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-management.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-management.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 8; 1006 bytes
@@ -720,10 +720,8 @@
<indexterm>
<primary>REPORT command (MySQL Cluster)</primary>
</indexterm>
-
- &mccge-warning-begin;
- <para>
+ <para>
<literal><replaceable>node_id</replaceable> REPORT
<replaceable>report-type</replaceable></literal>
</para>
@@ -760,12 +758,9 @@
<para>
The <literal>REPORT</literal> command was introduced in MySQL
- 5.1.19-ndb-6.2.3 and MySQL 5.1.19-ndb-6.3.0.
+ Cluster NDB 6.2.3 and MySQL Cluster NDB 6.3.0.
</para>
-
- &mccge-warning-end-cluster;
-
- </listitem>
+ </listitem>
<listitem>
<indexterm>
Modified: trunk/it/refman-5.1/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-multi-computer.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-multi-computer.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 6, Lines Added: 29, Lines Deleted: 48; 4694 bytes
@@ -1115,23 +1115,27 @@
<para>
On the management host, issue the following command from the
system shell to start the management node process:
- </para>
- <remark role="todo">
- List switches for clients or pointer to same.
- </remark>
-
<programlisting>
shell> <userinput>ndb_mgmd -f /var/lib/mysql-cluster/config.ini</userinput>
</programlisting>
-
- <para>
- Note that <command>ndb_mgmd</command> must be told where to
- find its configuration file, using the <option>-f</option> or
- <option>--config-file</option> option. (See
- <xref linkend="mysql-cluster-ndb-mgmd-process"/>, for
- details.)
</para>
+
+ <note>
+ <para>
+ <command>ndb_mgmd</command> must be told where to find its
+ configuration file, using the <option>-f</option> or
+ <option>--config-file</option> option. (See
+ <xref linkend="mysql-cluster-ndb-mgmd-process"/>, for
+ details.)
+ </para>
+
+ <para>
+ For additional options which can be used with
+ <command>ndb_mgmd</command>, see
+ <xref linkend="mysql-cluster-command-options"/>.
+ </para>
+ </note>
</listitem>
<listitem>
@@ -1146,9 +1150,7 @@
</listitem>
<listitem>
- &mccge-warning-unsupported-begin;
-
- <para>
+ <para>
If you used RPM files to install MySQL on the cluster host
where the SQL node is to reside, you can (and should) use the
supplied startup script to start the MySQL server process on
@@ -1157,10 +1159,8 @@
</listitem>
</orderedlist>
-
- &mccge-warning-end-cluster;
- <indexterm>
+ <indexterm>
<primary>MySQL Cluster</primary>
<secondary>ndb_mgm</secondary>
</indexterm>
@@ -1228,11 +1228,6 @@
<secondary>performing queries</secondary>
</indexterm>
- <remark role="todo">
- Look into changing this section to use new sample DB once MikeH
- has it ready.
- </remark>
-
<para>
Working with data in MySQL Cluster is not much different from
doing so in MySQL without Cluster. There are two points to keep in
@@ -1599,15 +1594,11 @@
shell> <userinput>ndb_mgm -e shutdown</userinput>
</programlisting>
- <remark role="todo">
- Document any other commands that can be passed to ndb_mgm in this
- fashion (or provide pointer). /JS 2005-07-19
- </remark>
-
<para>
The <option>-e</option> option here is used to pass a command to
- the <command>ndb_mgm</command> client from the shell. See
- <xref linkend="command-line-options"/>. The command causes the
+ the <command>ndb_mgm</command> client from the shell. (See
+ <xref linkend="mysql-cluster-command-options"/>, for more
+ information about this option.) The command causes the
<command>ndb_mgm</command>, <command>ndb_mgmd</command>, and any
<command>ndbd</command> processes to terminate gracefully. Any SQL
nodes can be terminated using <command>mysqladmin
@@ -1655,27 +1646,17 @@
</itemizedlist>
- <remark role="todo">
- [pd] Hmm ... why are these three paragraphs _here_? (But where
- would be more appropriate instead?)
- </remark>
-
<para>
- For information on making Cluster backups, see
- <xref linkend="mysql-cluster-backup-using-management-client"/>.
+ In a production setting, it is usually not desirable to shut down
+ the cluster completely. In many cases, even when making
+ configuration changes, or performing upgrades to the cluster
+ hardware or software (or both), which require shutting down
+ individual host machines, it is possible to do so without shutting
+ down the cluster as a whole by performing a <firstterm>rolling
+ restart</firstterm> of the cluster. For more information about
+ doing this, see <xref linkend="mysql-cluster-rolling-restart"/>.
</para>
- <para>
- To restore the cluster from backup requires the use of the
- <command>ndb_restore</command> command. This is covered in
- <xref linkend="mysql-cluster-restore"/>.
- </para>
-
- <para>
- More information on configuring MySQL Cluster can be found in
- <xref linkend="mysql-cluster-configuration"/>.
- </para>
-
</section>
</section>
Modified: trunk/it/refman-5.1/mysql-cluster-news-core.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-news-core.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-news-core.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 56, Lines Added: 1368, Lines Deleted: 1447; 154034 bytes
@@ -12,7 +12,7 @@
-->
<section id="mysql-cluster-news">
- <title>Changes in &mccge-series;</title>
+ <title>Changes in MySQL Cluster 6.x</title>
<remark role="dynamic-dependency-list"/>
@@ -22,101 +22,139 @@
</indexterm>
<para>
- This section contains changelog information for &mccge-series;.
+ This section contains changelog information for MySQL Cluster that
+ use version 6.1, 6.2, and 6.3 of the <literal>NDBCLUSTER</literal>
+ storage engine.
</para>
<para>
- Each &mccge-series; release is based on a mainline MySQL 5.1 release
+ Each MySQL Cluster release is based on a mainline MySQL 5.1 release
and a particular version of the <literal>NDBCLUSTER</literal>
storage engine, as shown in the version string returned by executing
<literal>SELECT VERSION()</literal> in the <command>mysql</command>
client, or by executing the <command>ndb_mgm</command> client
<literal>SHOW</literal> or <literal>STATUS</literal> command; for
- more information, see <xref linkend="mysql-cluster-cge"/>.
+ more information, see <xref linkend="mysql-cluster"/>.
</para>
<para>
- For general information about features added in &mccge-series;, see
- <xref linkend="mysql-cluster-cge-differences"/>. For a full list of
- changes in &mccge-series;, please refer to the changelog section for
- each individual &mccge-series; release.
+ For general information about features added in MySQL Cluster, see
+ <xref linkend="mysql-cluster-roadmap"/>. For a complete list of all
+ bugfixes and feature changes in MySQL Cluster, please refer to the
+ changelog section for each individual MySQL Cluster release.
</para>
<para>
- An overview of features added in MySQL 5.1 not specific to
- &mccge-series; can be found here: <xref linkend="mysql-nutshell"/>.
- For a full list of changes in MySQL 5.1 releases not specific to
- &mccge-series;, see <xref linkend="news-5-1-x"/>.
+ An overview of features added in MySQL 5.1 not specific to MySQL
+ Cluster can be found here: <xref linkend="mysql-nutshell"/>. For a
+ complete list of all bugfixes and features changes made in MySQL 5.1
+ that are not specific to MySQL Cluster, see
+ <xref linkend="news-5-1-x"/>.
</para>
- <remark>
+ <remark role="NOTE">
To insert a new MySQL Cluster changelog subsection, use the
- <filename>mysql-cluster-changelog-template.xml</filename> template
+ <filename>mysql-cluster-changelog-TEMPLATE.xml</filename> template
in the current directory.
</remark>
<section id="mysql-cluster-news-6-3">
- <title>Changes in &mccge-series; 6.3.x</title>
+ <title>Changes in MySQL Cluster NDB 6.3</title>
<para>
- This section contains change history information for
- &mccge-series; releases based on version 6.3 of the
- <literal>NDBCLUSTER</literal> storage engine.
+ This section contains change history information for MySQL Cluster
+ releases based on version 6.3 of the <literal>NDBCLUSTER</literal>
+ storage engine.
</para>
- <section id="mysql-cluster-news-5-1-24-ndb-6-3-14">
+ <para>
+ For an overview of new features added in MySQL Cluster NDB 6.3,
+ see <xref linkend="mysql-cluster-changes-5-1-ndb-6-3"/>.
+ </para>
- <title condition="dynamic:changelog:vertitle" role="5.1.24-ndb-6.3.14:mysqld:all"/>
+ <section id="mysql-cluster-news-5-1-24-ndb-6-3-15">
+ <title condition="dynamic:changelog:vertitle" role="5.1.24-ndb-6.3.15:mysqld:all"/>
+
<para role="release-level">
This is a new Beta development release, fixing recently
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; 6.3 release.
+ discovered bugs in previous MySQL Cluster NDB 6.3 releases.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
+ <para>
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.24 (see <xref linkend="news-5-1-24"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.19-ndb-6.3.0, MySQL 5.1.19-ndb-6.3.1, MySQL
- 5.1.22-ndb-6.3.2, MySQL 5.1.22-ndb-6.3.3, MySQL
- 5.1.22-ndb-6.3.4, and MySQL 5.1.22-ndb-6.3.5, MySQL
- 5.1.22-ndb-6.3.6, and MySQL 5.1.23-ndb-6.3.7, MySQL
- 5.1.23-ndb-6.3.8, MySQL 5.1.23-ndb-6.3.9, and MySQL
- 5.1.23-ndb-6.3.10, 5.1.23-ndb-6.3.11, and MySQL
- 5.1.23-ndb-6.3.12, and MySQL 5.1.24-ndb-6.3.13. This release
- also includes all bugfixes and feature enhancements that were
- made in the mainline MySQL 5.1.21, 5.1.22, 5.1.23, and 5.1.24
- releases; information about these can be found in
- <xref linkend="news-5-1-21"/>, <xref linkend="news-5-1-22"/>,
- <xref linkend="news-5-1-23"/>, and
- <xref linkend="news-5-1-24"/>.
+ <para condition="dynamic:changelog:entrylist" role="5.1.24-ndb-6.3.15:mysqld:all"/>
+
+ </section>
+
+ <section id="mysql-cluster-news-5-1-24-ndb-6-3-14">
+
+ <title condition="dynamic:changelog:vertitle" role="5.1.24-ndb-6.3.14:mysqld:all"/>
+
+ <para role="release-level">
+ This is a new Beta development release, fixing recently
+ discovered bugs in previous MySQL Cluster NDB 6.3 releases.
</para>
-<!--
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.18-ndb-6.2.1 from a previous release</title>
-
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
<para>
-
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
</para>
-
- </formalpara>
-
- </important>
- -->
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.24 (see <xref linkend="news-5-1-24"/>).
+ </para>
+
+ <note>
+ <para role="release-non-production">
+ Please refer to our bug database at
+ <ulink url="http://bugs.mysql.com/"/> for more details about
+ the individual bugs fixed in this version.
+ </para>
+ </note>
+
<para condition="dynamic:changelog:entrylist" role="5.1.24-ndb-6.3.14:mysqld:all"/>
</section>
@@ -127,79 +165,39 @@
<para role="release-level">
This is a new Beta development release, fixing recently
- discovered bugs and incorporating improvements made since
- &mccge-series; 5.1.23-ndb-6.3.10. This include all bugfixes and
- improvements that were originally scheduled to appear in MySQL
- 5.1.23-ndb-6.3.11 and MySQL 5.1.23-ndb-6.3.12.
+ discovered bugs in previous MySQL Cluster NDB 6.3 releases.
</para>
- <formalpara>
+ <formalpara role="download-location">
- <title>Obtaining &mccge-series; 5.1.24-ndb-6.3.13</title>
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
<para>
- &mccge-series; 5.1.24-ndb-6.3.13 is a source-only release
- which you must compile and install using the instructions
- found in <xref linkend="installing-source"/>, and in
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
<xref linkend="mysql-cluster-building"/>. You can download the
GPL source tarball from the MySQL FTP site at
- <ulink url="&base-url-cge-files;mysql-5.1.24-ndb-6.3.13/mysql-5.1.24-ndb-6.3.13-telco.tar.gz"/>.
- This file contains the complete GPL source archive.
+ <ulink url="&base-url-cluster-files;"/>.
</para>
</formalpara>
<para>
- You can also obtain the latest GPL &mccge-series; sources from
- <ulink url="http://mysql.bkbits.net/"/> using the free BitKeeper
- client. See <xref linkend="installing-source-tree"/>, for more
- information.
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.24 (see <xref linkend="news-5-1-24"/>).
</para>
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.19-ndb-6.3.0, MySQL 5.1.19-ndb-6.3.1, MySQL
- 5.1.22-ndb-6.3.2, MySQL 5.1.22-ndb-6.3.3, MySQL
- 5.1.22-ndb-6.3.4, and MySQL 5.1.22-ndb-6.3.5, MySQL
- 5.1.22-ndb-6.3.6, and MySQL 5.1.23-ndb-6.3.7, MySQL
- 5.1.23-ndb-6.3.8, MySQL 5.1.23-ndb-6.3.9, and MySQL
- 5.1.23-ndb-6.3.10, as well as all bugfixes and feature changes
- which were originally scheduled to appear in MySQL
- 5.1.23-ndb-6.3.11 and MySQL 5.1.23-ndb-6.3.12 before these were
- withdrawn due to issues uncovered soon after they were released.
- MySQL 5.1.24-ndb-6.3.13 also includes all bugfixes and feature
- enhancements that were made in the mainline MySQL 5.1.21,
- 5.1.22, 5.1.23, and 5.1.24 releases; information about these can
- be found in <xref linkend="news-5-1-21"/>,
- <xref linkend="news-5-1-22"/>, <xref linkend="news-5-1-23"/>,
- and <xref linkend="news-5-1-24"/>.
- </para>
-
-<!--
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.18-ndb-6.2.1 from a previous release</title>
-
- <para>
-
- </para>
-
- </formalpara>
-
- </important>
- -->
-
<para condition="dynamic:changelog:entrylist" role="5.1.24-ndb-6.3.13:mysqld:all"/>
</section>
@@ -209,11 +207,10 @@
<title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.3.12:mysqld:all"/>
<para role="release-level">
- &mccge-series; 5.1.23-ndb-6.3.12 was pulled due to issues
- discovered shortly after its release, and is no longer
- available. Users of 5.1.23-ndb-6.3.10 and earlier &mccge-series;
- 6.<replaceable>x</replaceable> releases should upgrade to
- &mccge-series; 5.1.24-ndb-6.3.13 or later.
+ MySQL Cluster NDB 6.3.12 was pulled due to issues discovered
+ shortly after its release, and is no longer available. Users of
+ MySQL Cluster NDB 6.3.10 and earlier MySQL Cluster NDB 6.3
+ releases should upgrade to MySQL Cluster NDB 6.3.13 or later.
</para>
<para>
@@ -230,11 +227,10 @@
<title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.3.11:mysqld:all"/>
<para role="release-level">
- &mccge-series; 5.1.23-ndb-6.3.11 was pulled due to issues
- discovered shortly after its release, and is no longer
- available. Users of 5.1.23-ndb-6.3.10 and earlier &mccge-series;
- 6.<replaceable>x</replaceable> releases should upgrade to
- &mccge-series; 5.1.24-ndb-6.3.13 or later.
+ This release was pulled due to issues discovered shortly after
+ its release, and is no longer available. Users of MySQL Cluster
+ NDB 6.3.10 and earlier MySQL Cluster NDB 6.3 releases should
+ upgrade to MySQL Cluster NDB 6.3.13 or later.
</para>
<para>
@@ -251,34 +247,40 @@
<title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.3.10:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing a recently
- discovered bug.
+ This is a new Beta development release, fixing recently
+ discovered bugs in previous MySQL Cluster NDB 6.3 releases.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
+ <para>
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.23 (see <xref linkend="news-5-1-23"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.19-ndb-6.3.0, MySQL 5.1.19-ndb-6.3.1, MySQL
- 5.1.22-ndb-6.3.2, MySQL 5.1.22-ndb-6.3.3, MySQL
- 5.1.22-ndb-6.3.4, and MySQL 5.1.22-ndb-6.3.5, MySQL
- 5.1.22-ndb-6.3.6, and MySQL 5.1.23-ndb-6.3.7, MySQL
- 5.1.23-ndb-6.3.8, and MySQL 5.1.23-ndb-6.3.9, as well as all
- bugfixes and feature changes which were added in the mainline
- 5.1.21, 5.1.22, and 5.1.23 releases; information about these can
- be found in <xref linkend="news-5-1-21"/>,
- <xref linkend="news-5-1-22"/>, and
- <xref linkend="news-5-1-23"/>.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.23-ndb-6.3.10:mysqld:all"/>
</section>
@@ -289,32 +291,39 @@
<para role="release-level">
This is a new Beta development release, fixing recently
- discovered bugs.
+ discovered bugs in previous MySQL Cluster NDB 6.3 releases.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
+ <para>
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.23 (see <xref linkend="news-5-1-23"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.19-ndb-6.3.0, MySQL 5.1.19-ndb-6.3.1, MySQL
- 5.1.22-ndb-6.3.2, MySQL 5.1.22-ndb-6.3.3, MySQL
- 5.1.22-ndb-6.3.4, and MySQL 5.1.22-ndb-6.3.5, MySQL
- 5.1.22-ndb-6.3.6, and MySQL 5.1.23-ndb-6.3.7, and MySQL
- 5.1.23-ndb-6.3.8, as well as all bugfixes and feature changes
- which were added in the mainline 5.1.21, 5.1.22, and 5.1.23
- releases; information about these can be found in
- <xref linkend="news-5-1-21"/>, <xref linkend="news-5-1-22"/>,
- and <xref linkend="news-5-1-23"/>.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.23-ndb-6.3.9:mysqld:all"/>
</section>
@@ -325,32 +334,39 @@
<para role="release-level">
This is a new Beta development release, fixing recently
- discovered bugs.
+ discovered bugs in previous MySQL Cluster NDB 6.3 releases.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
+ <para>
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.23 (see <xref linkend="news-5-1-23"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.19-ndb-6.3.0, MySQL 5.1.19-ndb-6.3.1, MySQL
- 5.1.22-ndb-6.3.2, MySQL 5.1.22-ndb-6.3.3, MySQL
- 5.1.22-ndb-6.3.4, and MySQL 5.1.22-ndb-6.3.5, MySQL
- 5.1.22-ndb-6.3.6, and MySQL 5.1.23-ndb-6.3.7, as well as all
- bugfixes and feature changes which were added in the mainline
- 5.1.21, 5.1.22, and 5.1.23 releases; information about these can
- be found in <xref linkend="news-5-1-21"/>,
- <xref linkend="news-5-1-22"/>, and
- <xref linkend="news-5-1-23"/>.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.23-ndb-6.3.8:mysqld:all"/>
</section>
@@ -361,31 +377,39 @@
<para role="release-level">
This is a new Beta development release, fixing recently
- discovered bugs.
+ discovered bugs in previous MySQL Cluster NDB 6.3 releases.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
+ <para>
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.23 (see <xref linkend="news-5-1-23"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.19-ndb-6.3.0, MySQL 5.1.19-ndb-6.3.1, MySQL
- 5.1.22-ndb-6.3.2, MySQL 5.1.22-ndb-6.3.3, MySQL
- 5.1.22-ndb-6.3.4, MySQL 5.1.22-ndb-6.3.5, and MySQL
- 5.1.22-ndb-6.3.6, as well as all bugfixes and feature changes
- which were added in the mainline 5.1.21, 5.1.22, and 5.1.23
- releases; information about these can be found in
- <xref linkend="news-5-1-21"/>, <xref linkend="news-5-1-22"/>,
- and <xref linkend="news-5-1-23"/>.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.23-ndb-6.3.7:mysqld:all"/>
</section>
@@ -396,30 +420,39 @@
<para role="release-level">
This is a new Beta development release, fixing recently
- discovered bugs.
+ discovered bugs in previous MySQL Cluster NDB 6.3 releases.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
+ <para>
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.22 (see <xref linkend="news-5-1-22"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.19-ndb-6.3.0, MySQL 5.1.19-ndb-6.3.1, MySQL
- 5.1.22-ndb-6.3.2, MySQL 5.1.22-ndb-6.3.3, MySQL
- 5.1.22-ndb-6.3.4, and MySQL 5.1.22-ndb-6.3.5, as well as all
- bugfixes and feature changes which were added in the mainline
- 5.1.21 and 5.1.22 releases; information about these can be found
- in <xref linkend="news-5-1-21"/> and
- <xref linkend="news-5-1-22"/>.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.22-ndb-6.3.6:mysqld:all"/>
</section>
@@ -430,29 +463,39 @@
<para role="release-level">
This is a new Beta development release, fixing recently
- discovered bugs.
+ discovered bugs in previous MySQL Cluster NDB 6.3 releases.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
+ <para>
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.22 (see <xref linkend="news-5-1-22"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.19-ndb-6.3.0, MySQL 5.1.19-ndb-6.3.1, MySQL
- 5.1.22-ndb-6.3.2, MySQL 5.1.22-ndb-6.3.3, and MySQL
- 5.1.22-ndb-6.3.4, as well as all bugfixes and feature changes
- which were added in the mainline 5.1.21 and 5.1.22 releases;
- information about these can be found in
- <xref linkend="news-5-1-21"/> and <xref linkend="news-5-1-22"/>.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.22-ndb-6.3.5:mysqld:all"/>
</section>
@@ -463,30 +506,39 @@
<para role="release-level">
This is a new Beta development release, fixing recently
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ discovered bugs in previous MySQL Cluster NDB 6.3 releases.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
+ <para>
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.22 (see <xref linkend="news-5-1-22"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.19-ndb-6.3.0, MySQL 5.1.19-ndb-6.3.1, MySQL
- 5.1.22-ndb-6.3.2, and MySQL 5.1.22-ndb-6.3.3, as well as all
- bugfixes and feature changes which were added in the mainline
- 5.1.21 and 5.1.22 releases; information about these can be found
- in <xref linkend="news-5-1-21"/> and
- <xref linkend="news-5-1-22"/>.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.22-ndb-6.3.4:mysqld:all"/>
</section>
@@ -497,29 +549,39 @@
<para role="release-level">
This is a new Beta development release, fixing recently
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ discovered bugs in previous MySQL Cluster NDB 6.3 releases.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
+ <para>
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.22 (see <xref linkend="news-5-1-22"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.19-ndb-6.3.0, MySQL 5.1.19-ndb-6.3.1, and
- MySQL 5.1.22-ndb-6.3.2, as well as all bugfixes and feature
- changes which were added in the mainline 5.1.21 and 5.1.22
- releases; information about these can be found in
- <xref linkend="news-5-1-21"/> and <xref linkend="news-5-1-22"/>.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.22-ndb-6.3.3:mysqld:all"/>
</section>
@@ -530,29 +592,39 @@
<para role="release-level">
This is a new Beta development release, fixing recently
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ discovered bugs in previous MySQL Cluster NDB 6.3 releases.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
+ <para>
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.22 (see <xref linkend="news-5-1-22"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.19-ndb-6.3.0 and MySQL 5.1.19-ndb-6.3.1, as
- well as all bugfixes and feature changes which were added in the
- mainline 5.1.21 and 5.1.22 releases; information about these can
- be found in <xref linkend="news-5-1-21"/> and
- <xref linkend="news-5-1-22"/>.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.22-ndb-6.3.2:mysqld:all"/>
</section>
@@ -562,28 +634,40 @@
<title condition="dynamic:changelog:vertitle" role="5.1.19-ndb-6.3.1:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing a recently
- discovered bug.
+ This is a new Beta development release, fixing recently
+ discovered bugs in the previous MySQL Cluster NDB 6.3 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
+ <para>
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.3 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.19 (see <xref linkend="news-5-1-19"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.19-ndb-6.3.0, as well as all bugfixes and
- feature changes which were added in the mainline 5.1.19 release;
- information about these can be found in
- <xref linkend="news-5-1-19"/>.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.19-ndb-6.3.1:mysqld:all"/>
</section>
@@ -593,30 +677,45 @@
<title condition="dynamic:changelog:vertitle" role="5.1.19-ndb-6.3.0:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is the first development release for MySQL Cluster NDB 6.3,
+ based on version 6.3 of the <literal>NDBCLUSTER</literal>
+ storage engine.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.3</title>
+
+ <para>
+ MySQL Cluster NDB 6.3 releases are source-only releases which
+ you must compile and install using the instructions found in
+ <xref linkend="installing-source"/>, and in
+ <xref linkend="mysql-cluster-building"/>. You can download the
+ GPL source tarball from the MySQL FTP site at
+ <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ <remark role="TODO">
+ Update to include relevant versions.
+ </remark>
+
+ This Beta release incorporates all bugfixes and feature changes
+ made in previous MySQL Cluster releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.19 (see <xref linkend="news-5-1-19"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, and
- MySQL 5.1.19-ndb-6.2.3, as well as all bugfixes and feature
- changes which were added in the mainline 5.1.19 release;
- information about these can be found in
- <xref linkend="news-5-1-19"/>.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.19-ndb-6.3.0:mysqld:all"/>
</section>
@@ -625,70 +724,57 @@
<section id="mysql-cluster-news-6-2">
- <title>Changes in &mccge-series; 6.2.x</title>
+ <title>Changes in MySQL Cluster NDB 6.2</title>
<para>
- This section contains change history information for
- &mccge-series; releases based on version 6.2 of the
- <literal>NDBCLUSTER</literal> storage engine.
+ This section contains change history information for MySQL Cluster
+ releases based on version 6.2 of the <literal>NDBCLUSTER</literal>
+ storage engine.
</para>
+ <para>
+ For an overview of new features added in MySQL Cluster NDB 6.2,
+ see <xref linkend="mysql-cluster-changes-5-1-ndb-6-2"/>.
+ </para>
+
<section id="mysql-cluster-news-5-1-24-ndb-6-2-16">
<title condition="dynamic:changelog:vertitle" role="5.1.24-ndb-6.2.16:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.24 (see <xref linkend="news-5-1-24"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, MySQL
- 5.1.19-ndb-6.2.3, MySQL 5.1.19-ndb-6.2.4, MySQL
- 5.1.22-ndb-6.2.5, MySQL 5.1.22-ndb-6.2.6, MySQL
- 5.1.22-ndb-6.2.7, MySQL 5.1.22-ndb-6.2.8, MySQL
- 5.1.23-ndb-6.2.9, MySQL 5.1.23-ndb-6.2.10, MySQL
- 5.1.23-ndb-6.2.11, MySQL 5.1.23-ndb-6.2.12, MySQL
- 5.1.23-ndb-6.2.13, MySQL 5.1.23-ndb-6.2.14, and MySQL
- 5.1.23-ndb-6.2.15, as well as all bugfixes and feature changes
- which were added in the mainline 5.1.20, 5.1.21, 5.1.22, 5.1.23,
- and 5.1.24 releases; information about these can be found in
- <xref linkend="news-5-1-20"/>, <xref linkend="news-5-1-21"/>,
- <xref linkend="news-5-1-22"/>, <xref linkend="news-5-1-23"/>,
- and <xref linkend="news-5-1-24"/>. Also included are most (but
- not all) bugfixes made in &mccge-series;
- 6.1.<replaceable>x</replaceable> through MySQL
- 5.1.15-ndb-6.1.16.
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.24-ndb-6.2.16:mysqld:all"/>
-<!--
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.18-ndb-6.2.1 from a previous release</title>
-
- <para>
-
- </para>
-
- </formalpara>
-
- </important>
- -->
-
- <para condition="dynamic:changelog:entrylist" role="5.1.23-ndb-6.2.15:mysqld:all"/>
-
</section>
<section id="mysql-cluster-news-5-1-23-ndb-6-2-15">
@@ -696,55 +782,22 @@
<title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.2.15:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
+ This is re-release of MySQL Cluster NDB 6.2.14 providing
+ binaries for supported platforms. For more information, see
+ <xref linkend="mysql-cluster-news-5-1-23-ndb-6-2-14"/>.
</para>
- <note>
- <para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
- <ulink url="http://bugs.mysql.com/"/> for more details about
- the individual bugs fixed in this version.
- </para>
- </note>
+ <formalpara role="download-location">
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, MySQL
- 5.1.19-ndb-6.2.3, MySQL 5.1.19-ndb-6.2.4, MySQL
- 5.1.22-ndb-6.2.5, MySQL 5.1.22-ndb-6.2.6, MySQL
- 5.1.22-ndb-6.2.7, MySQL 5.1.22-ndb-6.2.8, MySQL
- 5.1.23-ndb-6.2.9, MySQL 5.1.23-ndb-6.2.10, MySQL
- 5.1.23-ndb-6.2.11, MySQL 5.1.23-ndb-6.2.12, MySQL
- 5.1.23-ndb-6.2.13, and MySQL 5.1.23-ndb-6.2.14, as well as all
- bugfixes and feature changes which were added in the mainline
- 5.1.20, 5.1.21, 5.1.22, and 5.1.23 releases; information about
- these can be found in <xref linkend="news-5-1-20"/>,
- <xref linkend="news-5-1-21"/>, <xref linkend="news-5-1-22"/>,
- and <xref linkend="news-5-1-23"/>. Also included are most (but
- not all) bugfixes made in &mccge-series;
- 6.1.<replaceable>x</replaceable> through MySQL
- 5.1.15-ndb-6.1.16.
- </para>
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
-<!--
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.18-ndb-6.2.1 from a previous release</title>
-
<para>
-
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
</para>
-
- </formalpara>
-
- </important>
- -->
- <para condition="dynamic:changelog:entrylist" role="5.1.23-ndb-6.2.15:mysqld:all"/>
+ </formalpara>
</section>
@@ -753,76 +806,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.2.14:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
- <formalpara>
+ <formalpara role="download-location">
- <title>Obtaining &mccge-series; 5.1.23-ndb-6.2.14</title>
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
<para>
- &mccge-series; 5.1.23-ndb-6.2.14 is a source-only release
- which you must compile and install using the instructions
- found in <xref linkend="installing-source"/>, and in
- <xref linkend="mysql-cluster-building"/>. You can download the
- GPL source tarball from the MySQL FTP site at
- <ulink url="&base-url-cge-files;mysql-5.1.23-ndb-6.2.14/mysql-5.1.23-ndb-6.2.14-telco.tar.gz"/>.
- This file contains the complete GPL source archive.
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
</para>
</formalpara>
<para>
- You can also obtain the latest GPL &mccge-series; sources from
- <ulink url="http://mysql.bkbits.net/"/> using the free BitKeeper
- client. See <xref linkend="installing-source-tree"/>, for more
- information.
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.23 (see <xref linkend="news-5-1-23"/>).
</para>
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, MySQL
- 5.1.19-ndb-6.2.3, MySQL 5.1.19-ndb-6.2.4, MySQL
- 5.1.22-ndb-6.2.5, MySQL 5.1.22-ndb-6.2.6, MySQL
- 5.1.22-ndb-6.2.7, MySQL 5.1.22-ndb-6.2.8, MySQL
- 5.1.23-ndb-6.2.9, MySQL 5.1.23-ndb-6.2.10, MySQL
- 5.1.23-ndb-6.2.11, MySQL 5.1.23-ndb-6.2.12, and MySQL
- 5.1.23-ndb-6.2.13, as well as all bugfixes and feature changes
- which were added in the mainline 5.1.20, 5.1.21, 5.1.22, and
- 5.1.23 releases; information about these can be found in
- <xref linkend="news-5-1-20"/>, <xref linkend="news-5-1-21"/>,
- <xref linkend="news-5-1-22"/>, and
- <xref linkend="news-5-1-23"/>. Also included are most (but not
- all) bugfixes made in the MCCGE 6.1.<replaceable>x</replaceable>
- series through MySQL 5.1.15-ndb-6.1.16.
- </para>
-
-<!--
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.18-ndb-6.2.1 from a previous release</title>
-
- <para>
-
- </para>
-
- </formalpara>
-
- </important>
- -->
-
<para condition="dynamic:changelog:entrylist" role="5.1.23-ndb-6.2.14:mysqld:all"/>
</section>
@@ -832,38 +846,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.2.13:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.23 (see <xref linkend="news-5-1-23"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, MySQL
- 5.1.19-ndb-6.2.3, MySQL 5.1.19-ndb-6.2.4, MySQL
- 5.1.22-ndb-6.2.5, MySQL 5.1.22-ndb-6.2.6, MySQL
- 5.1.22-ndb-6.2.7, MySQL 5.1.22-ndb-6.2.8, MySQL
- 5.1.23-ndb-6.2.9, MySQL 5.1.23-ndb-6.2.10, MySQL
- 5.1.23-ndb-6.2.11, and MySQL 5.1.23-ndb-6.2.12, as well as all
- bugfixes and feature changes which were added in the mainline
- 5.1.20, 5.1.21, 5.1.22, and 5.1.23 releases; information about
- these can be found in <xref linkend="news-5-1-20"/>,
- <xref linkend="news-5-1-21"/>, <xref linkend="news-5-1-22"/>,
- and <xref linkend="news-5-1-23"/>. Also included are most (but
- not all) bugfixes made in &mccge-series;
- 6.1.<replaceable>x</replaceable> through MySQL
- 5.1.15-ndb-6.1.16.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.23-ndb-6.2.13:mysqld:all"/>
</section>
@@ -873,44 +886,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.2.12:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.23 (see <xref linkend="news-5-1-23"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, MySQL
- 5.1.19-ndb-6.2.3, MySQL 5.1.19-ndb-6.2.4, MySQL
- 5.1.22-ndb-6.2.5, MySQL 5.1.22-ndb-6.2.6, MySQL
- 5.1.22-ndb-6.2.7, MySQL 5.1.22-ndb-6.2.8, MySQL
- 5.1.23-ndb-6.2.9, MySQL 5.1.23-ndb-6.2.10, and MySQL
- 5.1.23-ndb-6.2.11, as well as all bugfixes and feature changes
- which were added in the mainline 5.1.20, 5.1.21, 5.1.22, and
- 5.1.23 releases; information about these can be found in
- <xref linkend="news-5-1-20"/>, <xref linkend="news-5-1-21"/>,
- <xref linkend="news-5-1-22"/>, and
- <xref linkend="news-5-1-23"/>. Also included are most (but not
- all) bugfixes made in the MCCGE 6.1.<replaceable>x</replaceable>
- series through MySQL 5.1.15-ndb-6.1.16.
- </para>
-
- <important>
- <para>
- This release does <emphasis>not</emphasis> provide support for
- the InnoDB storage engine.
- </para>
- </important>
-
<para condition="dynamic:changelog:entrylist" role="5.1.23-ndb-6.2.12:mysqld:all"/>
</section>
@@ -920,37 +926,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.2.11:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.23 (see <xref linkend="news-5-1-23"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, MySQL
- 5.1.19-ndb-6.2.3, MySQL 5.1.19-ndb-6.2.4, MySQL
- 5.1.22-ndb-6.2.5, MySQL 5.1.22-ndb-6.2.6, MySQL
- 5.1.22-ndb-6.2.7, MySQL 5.1.22-ndb-6.2.8, MySQL
- 5.1.23-ndb-6.2.9, and MySQL 5.1.23-ndb-6.2.10, as well as all
- bugfixes and feature changes which were added in the mainline
- 5.1.20, 5.1.21, 5.1.22, and 5.1.23 releases; information about
- these can be found in <xref linkend="news-5-1-20"/>,
- <xref linkend="news-5-1-21"/>, <xref linkend="news-5-1-22"/>,
- and <xref linkend="news-5-1-23"/>. Also included are most (but
- not all) bugfixes made in &mccge-series;
- 6.1.<replaceable>x</replaceable> through MySQL
- 5.1.15-ndb-6.1.16.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.23-ndb-6.2.11:mysqld:all"/>
</section>
@@ -960,36 +966,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.2.10:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.23 (see <xref linkend="news-5-1-23"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, MySQL
- 5.1.19-ndb-6.2.3, MySQL 5.1.19-ndb-6.2.4, MySQL
- 5.1.22-ndb-6.2.5, MySQL 5.1.22-ndb-6.2.6, MySQL
- 5.1.22-ndb-6.2.7, MySQL 5.1.22-ndb-6.2.8, and MySQL
- 5.1.23-ndb-6.2.9, as well as all bugfixes and feature changes
- which were added in the mainline 5.1.20, 5.1.21, 5.1.22, and
- 5.1.23 releases; information about these can be found in
- <xref linkend="news-5-1-20"/>, <xref linkend="news-5-1-21"/>,
- <xref linkend="news-5-1-22"/>, and
- <xref linkend="news-5-1-23"/>. Also included are most (but not
- all) bugfixes made in the MCCGE 6.1.<replaceable>x</replaceable>
- series through MySQL 5.1.15-ndb-6.1.16.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.23-ndb-6.2.10:mysqld:all"/>
</section>
@@ -999,35 +1006,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.22-ndb-6.2.9:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.22 (see <xref linkend="news-5-1-22"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, MySQL
- 5.1.19-ndb-6.2.3, MySQL 5.1.19-ndb-6.2.4, MySQL
- 5.1.22-ndb-6.2.5, MySQL 5.1.22-ndb-6.2.6, MySQL
- 5.1.22-ndb-6.2.7, and MySQL 5.1.22-ndb-6.2.8, as well as all
- bugfixes and feature changes which were added in the mainline
- 5.1.20, 5.1.21 and 5.1.22 releases; information about these can
- be found in <xref linkend="news-5-1-20"/>,
- <xref linkend="news-5-1-21"/>, and
- <xref linkend="news-5-1-22"/>. Also included are most (but not
- all) bugfixes made in the MCCGE 6.1.<replaceable>x</replaceable>
- series through MySQL 5.1.15-ndb-6.1.16.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.22-ndb-6.2.9:mysqld:all"/>
</section>
@@ -1037,35 +1046,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.22-ndb-6.2.8:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.22 (see <xref linkend="news-5-1-22"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, MySQL
- 5.1.19-ndb-6.2.3, MySQL 5.1.19-ndb-6.2.4, MySQL
- 5.1.22-ndb-6.2.5, MySQL 5.1.22-ndb-6.2.6, and MySQL
- 5.1.22-ndb-6.2.7, as well as all bugfixes and feature changes
- which were added in the mainline 5.1.20, 5.1.21 and 5.1.22
- releases; information about these can be found in
- <xref linkend="news-5-1-20"/>, <xref linkend="news-5-1-21"/>,
- and <xref linkend="news-5-1-22"/>. Also included are most (but
- not all) bugfixes made in &mccge-series;
- 6.1.<replaceable>x</replaceable> through MySQL
- 5.1.15-ndb-6.1.16.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.22-ndb-6.2.8:mysqld:all"/>
</section>
@@ -1075,35 +1086,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.22-ndb-6.2.7:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.22 (see <xref linkend="news-5-1-22"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, MySQL
- 5.1.19-ndb-6.2.3, MySQL 5.1.19-ndb-6.2.4, MySQL
- 5.1.22-ndb-6.2.5, and MySQL 5.1.22-ndb-6.2.6, as well as all
- bugfixes and feature changes which were added in the mainline
- 5.1.20, 5.1.21 and 5.1.22 releases; information about these can
- be found in <xref linkend="news-5-1-20"/>,
- <xref linkend="news-5-1-21"/>, and
- <xref linkend="news-5-1-22"/>. Also included are most (but not
- all) bugfixes made in the MCCGE 6.1.<replaceable>x</replaceable>
- series through MySQL 5.1.15-ndb-6.1.16.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.22-ndb-6.2.7:mysqld:all"/>
</section>
@@ -1113,34 +1126,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.22-ndb-6.2.6:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.22 (see <xref linkend="news-5-1-22"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, MySQL
- 5.1.19-ndb-6.2.3, MySQL 5.1.19-ndb-6.2.4, and MySQL
- 5.1.22-ndb-6.2.5, as well as all bugfixes and feature changes
- which were added in the mainline 5.1.20, 5.1.21 and 5.1.22
- releases; information about these can be found in
- <xref linkend="news-5-1-20"/>, <xref linkend="news-5-1-21"/>,
- and <xref linkend="news-5-1-22"/>. Also included are most (but
- not all) bugfixes made in &mccge-series;
- 6.1.<replaceable>x</replaceable> through MySQL
- 5.1.15-ndb-6.1.16.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.22-ndb-6.2.6:mysqld:all"/>
</section>
@@ -1150,33 +1166,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.22-ndb-6.2.5:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.22 (see <xref linkend="news-5-1-22"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2, MySQL
- 5.1.19-ndb-6.2.3, and MySQL 5.1.19-ndb-6.2.4, as well as all
- bugfixes and feature changes which were added in the mainline
- 5.1.20, 5.1.21 and 5.1.22 releases; information about these can
- be found in <xref linkend="news-5-1-20"/>,
- <xref linkend="news-5-1-21"/>, and
- <xref linkend="news-5-1-22"/>. Also included are most (but not
- all) bugfixes made in the MCCGE 6.1.<replaceable>x</replaceable>
- series through MySQL 5.1.15-ndb-6.1.16.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.22-ndb-6.2.5:mysqld:all"/>
</section>
@@ -1186,31 +1206,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.19-ndb-6.2.4:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.19 (see <xref linkend="news-5-1-19"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.3, and
- MySQL 5.1.19-ndb-6.2.4, as well as all bugfixes and feature
- changes which were added in the mainline 5.1.19 release;
- information about these can be found in
- <xref linkend="news-5-1-19"/>. Also included are most (but not
- all) bugfixes made in the MCCGE 6.1.<replaceable>x</replaceable>
- series through MySQL 5.1.15-ndb-6.1.16.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.19-ndb-6.2.4:mysqld:all"/>
</section>
@@ -1220,31 +1246,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.19-ndb-6.2.3:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.18 (see <xref linkend="news-5-1-18"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1 and MySQL 5.1.18-ndb-6.2.2, as
- well as all bugfixes and feature changes which were added in the
- mainline 5.1.19 release; information about these can be found in
- <xref linkend="news-5-1-19"/>. Also included are most (but not
- all) bugfixes made in the MCCGE 6.1.<replaceable>x</replaceable>
- series through MySQL 5.1.15-ndb-6.1.16.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.19-ndb-6.2.4:mysqld:all"/>
</section>
@@ -1254,29 +1286,37 @@
<title condition="dynamic:changelog:vertitle" role="5.1.18-ndb-6.2.2:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.2 release.
</para>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
+ <para>
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.18 (see <xref linkend="news-5-1-18"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.16-ndb-6.2.0 and MySQL 5.1.18-ndb-6.2.1, which
- includes all bugfixes and feature changes which were added in
- the mainline 5.1.18 release; information about these can be
- found in <xref linkend="news-5-1-18"/>.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.18-ndb-6.2.2:mysqld:all"/>
</section>
@@ -1286,138 +1326,78 @@
<title condition="dynamic:changelog:vertitle" role="5.1.18-ndb-6.2.1:mysqld:all"/>
<para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a Beta development release, fixing recently discovered
+ bugs in the previous MySQL Cluster NDB 6.2 release.
</para>
- <warning>
+ <formalpara role="download-location">
+
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
<para>
- This release was withdrawn after production and should no
- longer be used.
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
</para>
- </warning>
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.2 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.18 (see <xref linkend="news-5-1-18"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.0, which includes all bugfixes and
- feature changes which were added in the mainline 5.1.18 release;
- information about these can be found in
- <xref linkend="news-5-1-18"/>.
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.18-ndb-6.2.1:mysqld:all"/>
- <important>
- <formalpara>
+ </section>
- <title>Upgrading to MySQL 5.1.18-ndb-6.2.1 from a previous release</title>
+ <section id="mysql-cluster-news-5-1-16-ndb-6-2-0">
- <para>
- The internal specifications for columns in
- <literal>NDB</literal> tables changed to allow compatibility
- with future MySQL Cluster and &mccge-series; releases that
- are expected to implement online adding and dropping of
- columns. This change is not backwards compatible with MySQL
- 5.1.16-ndb-6.2.0, ndb-6.1.x versions prior to MySQL
- 5.1.15-ndb-6.1.7, or MySQL Cluster mainline releases prior
- to 5.1.18.
- </para>
+ <title condition="dynamic:changelog:vertitle" role="5.1.16-ndb-6.2.0:mysqld:all"/>
- </formalpara>
+ <para role="release-level">
+ This is the first MySQL Cluster NDB 6.2 development release,
+ based on version 6.2 of the <literal>NDBCLUSTER</literal>
+ storage engine.
+ </para>
- <para>
- See
- <link linkend="mysql-cluster-upgrade-downgrade-compatibility-online-add-drop-column">the
- related note</link> in
- <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>,
- for important information prior to upgrading a MySQL Cluster
- to MySQL 5.1.15-ndb-6.1.7 or later from MySQL 5.1.15-ndb-6.1.6
- or an earlier ndb-6.1.x release.
- </para>
+ <formalpara role="download-location">
+ <title>Obtaining MySQL Cluster NDB 6.2</title>
+
<para>
- See also Bug #28205.
+ You can download the latest MySQL Cluster NDB 6.2 source code
+ and binaries for supported platforms from
+ &base-url-cluster-downloads;.
</para>
- </important>
- <para condition="dynamic:changelog:entrylist" role="5.1.18-ndb-6.2.1:mysqld:all"/>
+ </formalpara>
- </section>
-
- <section id="mysql-cluster-news-5-1-16-ndb-6-2-0">
-
- <title condition="dynamic:changelog:vertitle" role="5.1.16-ndb-6.2.0:mysqld:all"/>
-
- <para role="release-level">
- This is a new Beta development release, fixing recently
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ <para>
+ This Beta release incorporates bugfixes and changes made in
+ previous MySQL Cluster releases, as well as all bugfixes and
+ feature changes which were added in mainline MySQL 5.1 through
+ MySQL 5.1.16 (see <xref linkend="news-5-1-16"/>).
</para>
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- which were added in MySQL 5.1.15-ndb-6.1.1 as well as in the
- mainline 5.1.16 release.
- </para>
-
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.16-ndb-6.2.0 from a previous release</title>
-
- <para>
- This release is not binary compatible with previous MySQL
- &mccge-series; or mainline MySQL 5.1 releases. This means
- that:
-
- <itemizedlist>
-
- <listitem>
- <para>
- You cannot perform an online upgrade to this release
- from any of the MySQL &mccge-series; releases based on
- MySQL 5.1.14 or MySQL 5.1.15, or from any of the
- mainline MySQL 5.1 releases. When upgrading from one
- of these versions, you must shut down the cluster,
- replace all binaries, then restart the cluster.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You must recompile all NDB API and MGM API
- applications used with a previous version of MySQL
- Cluster, including those compiled against any of the
- MySQL &mccge-series; releases based on MySQL 5.1.14 or
- MySQL 5.1.15.
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
-
- </formalpara>
- </important>
-
<para condition="dynamic:changelog:entrylist" role="5.1.16-ndb-6.2.0:mysqld:all"/>
</section>
@@ -1426,54 +1406,61 @@
<section id="mysql-cluster-news-6-1">
- <title>Changes in &mccge-series; 6.1.x</title>
+ <title>Changes in MySQL Cluster NDB 6.1</title>
<para>
- This section contains change history information for
- &mccge-series; releases based on version 6.1 of the
- <literal>NDBCLUSTER</literal> storage engine.
+ This section contains change history information for MySQL Cluster
+ releases based on version 6.1 of the <literal>NDBCLUSTER</literal>
+ storage engine.
</para>
+ <para>
+ For an overview of new features added in MySQL Cluster NDB 6.1,
+ see <xref linkend="mysql-cluster-changes-5-1-ndb-6-1"/>.
+ </para>
+
<section id="mysql-cluster-news-5-1-15-ndb-6-1-23">
<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
- made since the previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, MySQL
- 5.1.15-ndb-6.1.10, MySQL 5.1.15-ndb-6.1.11, MySQL
- 5.1.15-ndb-6.1.12, MySQL 5.1.15-ndb-6.1.13, MySQL
- 5.1.15-ndb-6.1.14, MySQL 5.1.15-ndb-6.1.15, MySQL
- 5.1.15-ndb-6.1.16, MySQL 5.1.15-ndb-6.1.17, MySQL
- 5.1.15-ndb-6.1.18, MySQL 5.1.15-ndb-6.1.19, MySQL
- 5.1.15-ndb-6.1.20, MySQL 5.1.15-ndb-6.1.21, and MySQL
- 5.1.15-ndb-6.1.22. This version also incorporates all bugfixes
- and feature changes which were added in the mainline MySQL 5.1
- releases up to and including 5.1.15 (see
- <xref linkend="news-5-1-15"/>).
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.23:mysqld:all"/>
- <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-22">
@@ -1481,40 +1468,43 @@
<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
- made since the previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, MySQL
- 5.1.15-ndb-6.1.10, MySQL 5.1.15-ndb-6.1.11, MySQL
- 5.1.15-ndb-6.1.12, MySQL 5.1.15-ndb-6.1.13, MySQL
- 5.1.15-ndb-6.1.14, MySQL 5.1.15-ndb-6.1.15, MySQL
- 5.1.15-ndb-6.1.16, MySQL 5.1.15-ndb-6.1.17, MySQL
- 5.1.15-ndb-6.1.18, MySQL 5.1.15-ndb-6.1.19, MySQL
- 5.1.15-ndb-6.1.20, and MySQL 5.1.15-ndb-6.1.21. This version
- also incorporates all bugfixes and feature changes which were
- added in the mainline MySQL 5.1 releases up to and including
- 5.1.15 (see <xref linkend="news-5-1-15"/>).
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.22:mysqld:all"/>
- <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-21">
@@ -1522,38 +1512,41 @@
<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
- bugfixes made since the previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, MySQL
- 5.1.15-ndb-6.1.10, MySQL 5.1.15-ndb-6.1.11, MySQL
- 5.1.15-ndb-6.1.12, MySQL 5.1.15-ndb-6.1.13, MySQL
- 5.1.15-ndb-6.1.14, MySQL 5.1.15-ndb-6.1.15, MySQL
- 5.1.15-ndb-6.1.16, MySQL 5.1.15-ndb-6.1.17, MySQL
- 5.1.15-ndb-6.1.18, MySQL 5.1.15-ndb-6.1.19, and MySQL
- 5.1.15-ndb-6.1.20. This version also incorporates all bugfixes
- and feature changes which were added in the mainline MySQL 5.1
- releases up to and including 5.1.15 (see
- <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
</section>
@@ -1563,39 +1556,43 @@
<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
- made since the previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, MySQL
- 5.1.15-ndb-6.1.10, MySQL 5.1.15-ndb-6.1.11, MySQL
- 5.1.15-ndb-6.1.12, MySQL 5.1.15-ndb-6.1.13, MySQL
- 5.1.15-ndb-6.1.14, MySQL 5.1.15-ndb-6.1.15, MySQL
- 5.1.15-ndb-6.1.16, MySQL 5.1.15-ndb-6.1.17, MySQL
- 5.1.15-ndb-6.1.18, and MySQL 5.1.15-ndb-6.1.19. This version
- also incorporates all bugfixes and feature changes which were
- added in the mainline MySQL 5.1 releases up to and including
- 5.1.15 (see <xref linkend="news-5-1-15"/>).
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.20:mysqld:all"/>
- <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.21:mysqld:all"/>
-
</section>
<section id="mysql-cluster-news-5-1-15-ndb-6-1-19">
@@ -1603,37 +1600,41 @@
<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
- feature enhancements since the previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, MySQL
- 5.1.15-ndb-6.1.10, MySQL 5.1.15-ndb-6.1.11, MySQL
- 5.1.15-ndb-6.1.12, MySQL 5.1.15-ndb-6.1.13, MySQL
- 5.1.15-ndb-6.1.14, MySQL 5.1.15-ndb-6.1.15, MySQL
- 5.1.15-ndb-6.1.16, MySQL 5.1.15-ndb-6.1.17, and MySQL
- 5.1.15-ndb-6.1.18. This version also incorporates all bugfixes
- and feature changes which were added in the mainline MySQL 5.1
- releases up to and including 5.1.15 (see
- <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.19:mysqld:all"/>
</section>
@@ -1643,10 +1644,33 @@
<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
- discovered bugs in the previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
Please refer to our bug database at
@@ -1655,22 +1679,6 @@
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, MySQL
- 5.1.15-ndb-6.1.10, MySQL 5.1.15-ndb-6.1.11, MySQL
- 5.1.15-ndb-6.1.12, MySQL 5.1.15-ndb-6.1.13, MySQL
- 5.1.15-ndb-6.1.14, MySQL 5.1.15-ndb-6.1.15, MySQL
- 5.1.15-ndb-6.1.16, and MySQL 5.1.15-ndb-6.1.17. This version
- also incorporates all bugfixes and feature changes which were
- added in the mainline MySQL 5.1 releases up to and including
- 5.1.15 (see <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.18:mysqld:all"/>
</section>
@@ -1680,36 +1688,41 @@
<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
- discovered bugs in the previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, MySQL
- 5.1.15-ndb-6.1.10, MySQL 5.1.15-ndb-6.1.11, MySQL
- 5.1.15-ndb-6.1.12, MySQL 5.1.15-ndb-6.1.13, MySQL
- 5.1.15-ndb-6.1.14, MySQL 5.1.15-ndb-6.1.15, and MySQL
- 5.1.15-ndb-6.1.16. This version also incorporates all bugfixes
- and feature changes which were added in the mainline MySQL 5.1
- releases up to and including 5.1.15 (see
- <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.17:mysqld:all"/>
</section>
@@ -1719,35 +1732,41 @@
<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
- discovered bugs in the previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, MySQL
- 5.1.15-ndb-6.1.10, MySQL 5.1.15-ndb-6.1.11, MySQL
- 5.1.15-ndb-6.1.12, MySQL 5.1.15-ndb-6.1.13, MySQL
- 5.1.15-ndb-6.1.14, and MySQL 5.1.15-ndb-6.1.15. This version
- also incorporates all bugfixes and feature changes which were
- added in the mainline MySQL 5.1 releases up to and including
- 5.1.15 (see <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.16:mysqld:all"/>
</section>
@@ -1757,35 +1776,41 @@
<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
- discovered bug in the previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, MySQL
- 5.1.15-ndb-6.1.10, MySQL 5.1.15-ndb-6.1.11, MySQL
- 5.1.15-ndb-6.1.12, MySQL 5.1.15-ndb-6.1.13, and MySQL
- 5.1.15-ndb-6.1.14. This version also incorporates all bugfixes
- and feature changes which were added in the mainline MySQL 5.1
- releases up to and including 5.1.15 (see
- <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.15:mysqld:all"/>
</section>
@@ -1795,34 +1820,41 @@
<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
- made since the previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, MySQL
- 5.1.15-ndb-6.1.10, MySQL 5.1.15-ndb-6.1.11, MySQL
- 5.1.15-ndb-6.1.12, and MySQL 5.1.15-ndb-6.1.13. This version
- also incorporates all bugfixes and feature changes which were
- added in the mainline MySQL 5.1 releases up to and including
- 5.1.15 (see <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.14:mysqld:all"/>
</section>
@@ -1832,35 +1864,41 @@
<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
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, MySQL
- 5.1.15-ndb-6.1.10, MySQL 5.1.15-ndb-6.1.11, and MySQL
- 5.1.15-ndb-6.1.12. This version also incorporates all bugfixes
- and feature changes which were added in the mainline MySQL 5.1
- releases up to and including 5.1.15 (see
- <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.13:mysqld:all"/>
</section>
@@ -1870,34 +1908,41 @@
<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
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, MySQL
- 5.1.15-ndb-6.1.10, and MySQL 5.1.15-ndb-6.1.11. This version
- also incorporates all bugfixes and feature changes which were
- added in the mainline MySQL 5.1 releases up to and including
- 5.1.15 (see <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.12:mysqld:all"/>
</section>
@@ -1907,34 +1952,41 @@
<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
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, MySQL 5.1.15-ndb-6.1.9, and MySQL
- 5.1.15-ndb-6.1.10. This version also incorporates all bugfixes
- and feature changes which were added in the mainline MySQL 5.1
- releases up to and including 5.1.15 (see
- <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.11:mysqld:all"/>
</section>
@@ -1944,33 +1996,41 @@
<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
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, MySQL
- 5.1.15-ndb-6.1.8, and MySQL 5.1.15-ndb-6.1.9. This version also
- incorporates all bugfixes and feature changes which were added
- in the mainline MySQL 5.1 releases up to and including 5.1.15
- (see <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.10:mysqld:all"/>
</section>
@@ -1980,23 +2040,41 @@
<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
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
<para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, MySQL 5.1.15-ndb-6.1.7, and MySQL
- 5.1.15-ndb-6.1.8. This version also incorporates all bugfixes
- and feature changes which were added in the mainline MySQL 5.1
- releases up to and including 5.1.15 (see
- <xref linkend="news-5-1-15"/>).
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
+ <note>
+ <para role="release-non-production">
+ Please refer to our bug database at
+ <ulink url="http://bugs.mysql.com/"/> for more details about
+ the individual bugs fixed in this version.
+ </para>
+ </note>
+
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.9:mysqld:all"/>
</section>
@@ -2006,32 +2084,41 @@
<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
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, MySQL
- 5.1.15-ndb-6.1.6, and MySQL 5.1.15-ndb-6.1.7. This version also
- incorporates all bugfixes and feature changes which were added
- in the mainline MySQL 5.1 releases up to and including 5.1.15
- (see <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.8:mysqld:all"/>
</section>
@@ -2041,99 +2128,85 @@
<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
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, MySQL 5.1.15-ndb-6.1.5, and MySQL
- 5.1.15-ndb-6.1.6. This version also incorporates all bugfixes
- and feature changes which were added in the mainline MySQL 5.1
- releases up to and including 5.1.15 (see
- <xref linkend="news-5-1-15"/>).
- </para>
+ <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.7:mysqld:all"/>
- <important>
- <formalpara>
+ </section>
- <title>Upgrading to MySQL 5.1.15-ndb-6.1.7 from a previous release</title>
+ <section id="mysql-cluster-news-5-1-15-ndb-6-1-6">
- <para>
- The internal specifications for columns in
- <literal>NDB</literal> tables has changed to allow
- compatibility with future MySQL Cluster and &mccge-series;
- releases that are expected to implement online adding and
- dropping of columns. This change is not backwards compatible
- with MySQL 5.1.16-ndb-6.2.0, ndb-6.1.x versions prior to
- MySQL 5.1.15-ndb-6.1.7, or MySQL Cluster mainline releases
- prior to 5.1.18.
- </para>
+ <title condition="dynamic:changelog:vertitle" role="5.1.15-ndb-6.1.6:mysqld:all"/>
- </formalpara>
+ <para role="release-level">
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
+ </para>
- <para>
- See
- <link linkend="mysql-cluster-upgrade-downgrade-compatibility-online-add-drop-column">the
- related note</link> in
- <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>,
- for important information prior to upgrading a MySQL Cluster
- to MySQL 5.1.15-ndb-6.1.7 or later from MySQL 5.1.15-ndb-6.1.6
- or an earlier ndb-6.1.x release.
- </para>
+ <formalpara role="download-location">
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
<para>
- See also Bug #28205.
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
</para>
- </important>
- <para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.7:mysqld:all"/>
+ </formalpara>
- </section>
-
- <section id="mysql-cluster-news-5-1-15-ndb-6-1-6">
-
- <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
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL
- 5.1.15-ndb-6.1.4, and MySQL 5.1.15-ndb-6.1.5. This version also
- incorporates all bugfixes and feature changes which were added
- in the mainline MySQL 5.1 releases up to and including 5.1.15
- (see <xref linkend="news-5-1-15"/>).
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.6:mysqld:all"/>
</section>
@@ -2143,75 +2216,41 @@
<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
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, and MySQL
- 5.1.15-ndb-6.1.4. This version also incorporates all bugfixes
- and feature changes which were added in the mainline MySQL 5.1
- releases up to and including 5.1.15 (see
- <xref linkend="news-5-1-15"/>).
- </para>
-
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.15-ndb-6.1.5 from a previous release</title>
-
- <para>
- This release is not binary compatible with releases previous
- to MySQL 5.1.15-ndb-6.1.3. This means that:
-
- <itemizedlist>
-
- <listitem>
- <para>
- You cannot perform an online upgrade to this release
- from MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1,
- MySQL 5.1.15-ndb-6.1.2, or any of the mainline MySQL
- 5.1 releases. When upgrading from one of these
- versions, you must shut down the cluster, replace all
- binaries, then restart the cluster.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You must recompile all NDB API and MGM API
- applications used with a previous version of MySQL
- Cluster, including those compiled against MySQL
- 5.1.15-ndb-6.1.3.
- </para>
- </listitem>
-
- </itemizedlist>
-
- This release is also not backwards compatible with MySQL
- 5.1.15-ndb-6.1.14 or any release previous to MySQL
- 5.1.15-ndb-6.1.14 due to changes in the
- <literal>mysql</literal> system database. See
- <citetitle>Functionality added or changed</citetitle> for
- more information.
- </para>
-
- </formalpara>
- </important>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.5:mysqld:all"/>
</section>
@@ -2221,72 +2260,41 @@
<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
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
<para>
- This was a testing release only, and not distributed to
- customers.
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
- 5.1.15-ndb-6.1.2, and MySQL 5.1.15-ndb-6.1.3. This version also
- incorporates all bugfixes and feature changes which were added
- in the mainline MySQL 5.1 releases up to and including 5.1.15
- (see <xref linkend="news-5-1-15"/>).
- </para>
-
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.15-ndb-6.1.4 from a previous release</title>
-
- <para>
- This release is not binary compatible with previous
- releases. This means that:
-
- <itemizedlist>
-
- <listitem>
- <para>
- You cannot perform an online upgrade to this release
- from MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1,
- MySQL 5.1.15-ndb-6.1.2, or any of the mainline MySQL
- 5.1 releases. When upgrading from one of these
- versions, you must shut down the cluster, replace all
- binaries, then restart the cluster.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You must recompile all NDB API and MGM API
- applications used with a previous version of MySQL
- Cluster, including those compiled against MySQL
- 5.1.15-ndb-6.1.3.
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
-
- </formalpara>
- </important>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.4:mysqld:all"/>
</section>
@@ -2296,80 +2304,41 @@
<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
- discovered bugs and incorporating improvements made since the
- previous &mccge-series; release.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, and
- MySQL 5.1.15-ndb-6.1.2. This version also incorporates all
- bugfixes and feature changes which were added in the mainline
- 5.1.15 release; information about these can be found in
- <xref linkend="news-5-1-15"/>.
- </para>
-
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.15-ndb-6.1.3 from a previous release</title>
-
- <para>
- This release is not binary compatible with releases previous
- to MySQL 5.1.15-ndb-6.1.2. This means that:
-
- <itemizedlist>
-
- <listitem>
- <para>
- You cannot perform an online upgrade to this release
- from MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1,
- or any of the mainline MySQL 5.1 releases. When
- upgrading from one of these versions, you must shut
- down the cluster, replace all binaries, then restart
- the cluster.
- </para>
-
- <para>
- However, you <emphasis>can</emphasis> perform an
- online upgrade of a Cluster running MySQL
- 5.1.15-ndb-6.1.2 to MySQL 5.1.15-ndb-6.1.3, using the
- rolling upgrade procedure described in
- <xref linkend="mysql-cluster-rolling-restart"/>. You
- should replace all binaries for all data nodes,
- management nodes, and SQL nodes as part of this
- process. When upgrading the data nodes, you will need
- to restart each data with the
- <option>--initial</option> option.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You must recompile all NDB API and MGM API
- applications used with a previous version of MySQL
- Cluster, including those compiled against MySQL
- 5.1.15-ndb-6.1.2.
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
-
- </formalpara>
- </important>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.3:mysqld:all"/>
</section>
@@ -2379,77 +2348,41 @@
<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
- discovered bug.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
<para>
- Like all releases for MySQL &mccge-series;, this is a
- source-only release which you must compile and install using the
- instructions found in <xref linkend="installing-source"/>, and
- in <xref linkend="mysql-cluster-building"/>. You can download
- the source code archive for this release from the MySQL FTP site
- at <ulink url="&base-url-cge-files;mysql-5.1.15-ndb-6.1.2"/>.
- The file
- <filename>mysqlcom-5.1.15-ndb-6.1.2-telco.tar.gz</filename> in
- this directory contains the complete source archive.
+ This Beta release incorporates all bugfixes and changes made in
+ previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes
+ and feature changes which were added in mainline MySQL 5.1
+ through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
</para>
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This Beta release is a hotfix release, made to resolve a single
- critical issue which occurred in MySQL 5.1.15-ndb-6.1.1-beta. It
- incorporates all bugfixes and feature changes made in MySQL
- 5.1.14-ndb-6.1.0 and MySQL 5.1.15-ndb-6.1.1. This version also
- incorporates all bugfixes and feature changes which were added
- in the mainline 5.1.15 release; information about these can be
- found in <xref linkend="news-5-1-15"/>.
- </para>
-
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.15-ndb-6.1.2 from a previous release</title>
-
- <para>
- This release is not binary compatible with any previous
- releases. This means that:
-
- <itemizedlist>
-
- <listitem>
- <para>
- You cannot perform an online upgrade to this release
- from MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1,
- or any of the mainline MySQL 5.1 releases. You must
- shut down the cluster, replace all binaries, then
- restart the cluster.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You must recompile any MySQL Cluster API applications
- used with a previous version of MySQL Cluster. This
- includes all NDB API and MGM API applications.
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
-
- </formalpara>
- </important>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.2:mysqld:all"/>
</section>
@@ -2459,64 +2392,41 @@
<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
- discovered bugs.
+ This is a bugfix release, fixing recently discovered bugs in the
+ previous MySQL Cluster NDB 6.1 release.
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
+ <para>
+ This Beta release incorporates all bugfixes and changes made in
+ the previous MySQL Cluster NDB 6.1 release, as well as all
+ bugfixes and feature changes which were added in mainline MySQL
+ 5.1 through MySQL 5.1.15 (see <xref linkend="news-5-1-15"/>).
+ </para>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This section documents all changes and bug fixes that have been
- applied in this Beta release since the release of MySQL Cluster
- 5.1.14-ndb-6.1.0. This version also incorporates all bugfixes
- and feature changes which were added in the mainline 5.1.15
- release; information about these can be found in
- <xref linkend="news-5-1-15"/>.
- </para>
-
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.15-ndb-6.1.1 from a previous release</title>
-
- <para>
- This release is not binary compatible with any previous
- releases. This means that:
-
- <itemizedlist>
-
- <listitem>
- <para>
- You cannot perform an online upgrade to this release
- from either MySQL 5.1.14-ndb-6.1.0 or from any of the
- mainline MySQL 5.1 releases. You must shut down the
- cluster, replace all binaries, then restart the
- cluster.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You must recompile any MySQL Cluster API applications
- used with a previous version of MySQL Cluster. This
- includes all NDB API and MGM API applications.
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
-
- </formalpara>
- </important>
-
<para condition="dynamic:changelog:entrylist" role="5.1.15-ndb-6.1.1:mysqld:all"/>
</section>
@@ -2526,26 +2436,37 @@
<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
- discovered bugs.
+ This is the first MySQL Cluster NDB 6.1 release,
+ incorporatingnew features and bugfiuxes made for the
+ <literal>NDBCLUSTER</literal> storage engine made since
+ branching from MySQL 5.1.14 standard (see
+ <xref linkend="news-5-1-14"/>).
</para>
+ <formalpara role="download-location">
+
+ <title>MySQL Cluster NDB 6.1 no longer in development</title>
+
+ <para>
+ MySQL Cluster NDB 6.1 (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition 6.1.x</quote>) is no longer being
+ developed or maintained; if you are using a MySQL Cluster NDB
+ 6.1 release, you should consider upgrading to MySQL Cluster
+ NDB 6.2 or 6.3. If you require source code for this series,
+ you can obtain it from
+ <ulink url="http://mysql.bkbits.net/"/>.
+ </para>
+
+ </formalpara>
+
<note>
<para role="release-non-production">
- Although MySQL has worked very hard to ensure a high level of
- quality, protect your data by making a backup as you would for
- any software beta release. Please refer to our bug database at
+ Please refer to our bug database at
<ulink url="http://bugs.mysql.com/"/> for more details about
the individual bugs fixed in this version.
</para>
</note>
- <para>
- This section documents all changes and bug fixes that have been
- applied in this Beta release since MySQL &mccge-series; diverged
- from MySQL 5.1.14 standard.
- </para>
-
<para condition="dynamic:changelog:entrylist" role="5.1.14-ndb-6.1.0:mysqld:all"/>
</section>
Modified: trunk/it/refman-5.1/mysql-cluster-optvar-core.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-optvar-core.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-optvar-core.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 10, Lines Added: 16, Lines Deleted: 47; 4895 bytes
@@ -137,9 +137,9 @@
</important>
<para>
- Beginning with MySQL 5.1.24-ndb-6.2.16 and MySQL
- 5.1.24-ndb-6.3.13, the value used for this option is available
- as a global status variable. (Bug #35573)
+ Beginning with MySQL Cluster NDB 6.2.16 and MySQL Cluster NDB
+ 6.3.13, the value used for this option is available as a
+ global status variable. (Bug #35573)
</para>
</listitem>
@@ -318,11 +318,11 @@
</para>
<para>
- Beginning with MySQL 5.1.23-ndb-6.2.10, MySQL
- 5.1.23-ndb-6.3.7, and MySQL 5.1.23, this variable affects the
- number of <literal>AUTO_INCREMENT</literal> IDs that are
- fetched between statements only. Within a statement, at least
- 32 IDs are now obtained at a time. The default value for
+ Beginning with MySQL Cluster NDB 6.2.10, MySQL Cluster NDB
+ 6.3.7, and MySQL 5.1.23, this variable affects the number of
+ <literal>AUTO_INCREMENT</literal> IDs that are fetched between
+ statements only. Within a statement, at least 32 IDs are now
+ obtained at a time. The default value for
<literal>ndb_autoincrement_prefetch_sz</literal> is now
<literal>1</literal>, to increase the speed of statements
inserting single rows. (Bug #31956)
@@ -461,13 +461,10 @@
the SQL node attempts to use a given data node 8 times before
proceeding to the next one.
</para>
-
- &mccge-warning-begin;
-
+
<para>
- In MySQL 5.1.22-ndb-6.3.4 and later &mccge-series;
- 6.3.<replaceable>x</replaceable> releases, this option takes
- one of the integer values <literal>0</literal>,
+ Begiunning with MySQL Cluster NDB 6.3.4, this option takes one
+ of the integer values <literal>0</literal>,
<literal>1</literal>, <literal>2</literal>, or
<literal>3</literal>, with <literal>1</literal> being the
default. These values affect node selection as follows:
@@ -521,8 +518,7 @@
<important>
<para>
- In MySQL 5.1.22-ndb-6.3.4 and later &mccge-series;
- 6.3.<replaceable>x</replaceable> versions, it is no longer
+ Beginning with MySQL Cluster NDB 6.3.4, it is no longer
possible to set
<option>--ndb_optimized_node_selection</option> to
<literal>ON</literal> or <literal>OFF</literal>;
@@ -531,10 +527,7 @@
</para>
</important>
</para>
-
- &mccge-warning-end-cluster;
-
- </listitem>
+ </listitem>
<listitem>
<para id="option_mysqld_ndb_report_thresh_binlog_epoch_slip">
@@ -628,18 +621,6 @@
<para condition="dynamic:optvar:item" role="5.1:mysqld:ndb_wait_connected"/>
- <formalpara role="mccge-warning">
-
- <title>&mccge-series;</title>
-
- <para>
- This variable is available in &mccge-series; only. For more
- information about &mccge-series;, see
- <xref linkend="mysql-cluster-cge"/>.
- </para>
-
- </formalpara>
-
<para>
This variable can be used to cause the MySQL server to wait a
given period of time for connections to MySQL Cluster
@@ -750,7 +731,7 @@
<para>
Provides the number of round trips to the
<literal>NDB</literal> kernel made by operations. Added in
- MySQL 5.1.22-ndb-6.3.6.
+ MySQL Cluster NDB 6.3.6.
</para>
</listitem>
@@ -776,9 +757,6 @@
</listitem>
<listitem>
-
- &mccge-warning-begin;
-
<para id="option_mysqld_Slave_heartbeat_period">
<literal>Slave_heartbeat_period</literal>
</para>
@@ -789,17 +767,11 @@
</para>
<para>
- This variable was added in MySQL 5.1.22-ndb-6.3.4.
+ This variable was added in MySQL Cluster NDB 6.3.4.
</para>
-
- &mccge-warning-end-all;
-
</listitem>
<listitem>
-
- &mccge-warning-begin;
-
<para id="option_mysqld_Slave_received_heartbeats">
<literal>Slave_received_heartbeats</literal>
</para>
@@ -812,11 +784,8 @@
</para>
<para>
- This variable was added in MySQL 5.1.22-ndb-6.3.4.
+ This variable was added in MySQL Cluster NDB 6.3.4.
</para>
-
- &mccge-warning-end-cluster;
-
</listitem>
</itemizedlist>
Modified: trunk/it/refman-5.1/mysql-cluster-process-management.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-process-management.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-process-management.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 11; 1213 bytes
@@ -1358,9 +1358,7 @@
<indexterm>
<primary>--bind-address option (ndb_mgmd)</primary>
</indexterm>
-
- &mccge-warning-begin;
-
+
<para>
<option>--bind-address=<replaceable>host</replaceable>[:<replaceable>port</replaceable>]</option>
</para>
@@ -1382,15 +1380,10 @@
</para>
<para>
- This option was added in MySQL 5.1.19-ndb-6.2.5 and MySQL
- 5.1.22-ndb-6.3.2. It is not available in &mccge-series;
- ndb-6.1.<replaceable>x</replaceable> or mainline MySQL 5.1
- releases.
+ This option was added in MySQL Cluster NDB 6.2.5 and MySQL
+ Cluster NDB 6.3.2.
</para>
-
- &mccge-warning-end-cluster;
-
- </listitem>
+ </listitem>
<listitem>
<indexterm>
Modified: trunk/it/refman-5.1/mysql-cluster-replication.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-replication.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-replication.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 11, Lines Added: 17, Lines Deleted: 40; 5084 bytes
@@ -891,12 +891,10 @@
found in <xref linkend="news-5-1-14"/>.
</para>
</important>
-
- &mccge-warning-begin;
-
+
<para>
- Beginning with MySQL 5.1.22-ndb-6.3.2, this table has been changed
- to facilitate 3-way replication recovery. Two columns
+ Beginning with MySQL Cluster NDB 6.3.2, this table has been
+ changed to facilitate 3-way replication recovery. Two columns
<literal>orig_server_id</literal> and
<literal>orig_epoch</literal> have been added to this table; when
<command>mysqld</command> is started with the
@@ -922,11 +920,9 @@
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
</programlisting>
- The <literal>gci</literal> column was added in MySQL
- 5.1.22-ndb-6.2.6 and MySQL 5.1.22-ndb-6.3.2.
+ The <literal>gci</literal> column was added in MySQL Cluster NDB
+ 6.2.6 and MySQL Cluster NDB 6.3.2.
</para>
-
- &mccge-warning-end-cluster;
<para>
The following figure shows the relationship of the MySQL Cluster
@@ -1130,10 +1126,8 @@
<literal>ndb_schema</literal> tables does not exist on the slave,
it is created by <command>ndb_restore</command>. (Bug #14612)
</para>
-
- &mccge-warning-begin;
-
- <para>
+
+ <para>
Conflict resolution for MySQL Cluster Replication requires the
presence of an additional <literal>mysql.ndb_replication</literal>
table. Currently, this table must be created manually. For
@@ -1141,13 +1135,6 @@
<xref linkend="mysql-cluster-replication-conflict-resolution"/>.
</para>
- <remark role="NOTE">
- [js] Uncomment the following before adding any text past this
- point that does not apply strictly to MCCGE releases.
- </remark>
-
-<!-- &mccge-warning-end-cluster; -->
-
</section>
<section id="mysql-cluster-replication-preparation">
@@ -1513,15 +1500,13 @@
are covered in
<xref linkend="mysql-cluster-replication-two-channels"/>.
</para>
-
- &mccge-warning-begin;
-
- <indexterm>
+
+ <indexterm>
<primary>batched updates (MySQL Cluster Replication)</primary>
</indexterm>
<para>
- Beginning with MySQL 5.1.19-ndb-6.2.3, it is possible to improve
+ Beginning with MySQL Cluster NDB 6.2.3, it is possible to improve
cluster replication performance by enabling <firstterm>batched
updates</firstterm>. This can be accomplished by starting slave
<command>mysqld</command> processes with the
@@ -1585,13 +1570,9 @@
6 rows in set (0.00 sec)
</programlisting>
</para>
-
- &mccge-warning-end-cluster;
+ </section>
-
- </section>
-
<section id="mysql-cluster-replication-two-channels">
<title>Using Two Replication Channels</title>
@@ -2436,8 +2417,6 @@
<primary>conflict resolution</primary>
<secondary>in MySQL Cluster Replication</secondary>
</indexterm>
-
- &mccge-warning-section;
<para>
When using a replication setup involving multiple masters
@@ -2820,9 +2799,8 @@
</formalpara>
<para>
- This conflict resolution function is available in
- &mccge-series; releases beginning with MySQL
- 5.1.19-ndb-6.3.0.
+ This conflict resolution function is available
+ beginning with MySQL Cluster NDB 6.3.0.
</para>
</listitem>
@@ -2842,9 +2820,8 @@
</formalpara>
<para>
- This conflict resolution function is available in
- &mccge-series; releases beginning with MySQL
- 5.1.22-ndb-6.3.4.
+ This conflict resolution function is available
+ beginning with MySQL Cluster NDB 6.3.4.
</para>
</listitem>
@@ -2874,7 +2851,7 @@
<title>Status information</title>
<para id="option_mysqld_Ndb_conflict_fn_max">
- Beginning with MySQL 5.1.22-ndb-6.3.3, a server status variable
+ Beginning with MySQL Cluster NDB 6.3.3, a server status variable
<literal>Ndb_conflict_fn_max</literal> provides a count of the
number of times that a row was not applied on the current SQL
node due to <quote>greatest timestamp wins</quote> conflict
@@ -2885,7 +2862,7 @@
</formalpara>
<para id="option_mysqld_Ndb_conflict_fn_old">
- Beginning with MySQL-5.1.22-ndb-6.3.4, the number of times that a
+ Beginning with MySQL Cluster NDB 6.3.4, the number of times that a
row was not applied as the result of <quote>same timestamp
wins</quote> conflict resolution on a given
<command>mysqld</command> since the last time it was restarted is
Modified: trunk/it/refman-5.1/mysql-cluster-roadmap.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-roadmap.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-roadmap.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 11, Lines Added: 27, Lines Deleted: 25; 6094 bytes
@@ -33,8 +33,8 @@
<para>
In this section, we discuss changes in the implementation of MySQL
- Cluster in MySQL ¤t-series; and &mccge-series; as compared to
- MySQL &previous-series;.
+ Cluster in MySQL ¤t-series; and MySQL Cluster NDB as compared
+ to MySQL &previous-series;.
</para>
<!--
@@ -53,8 +53,8 @@
There are a number of significant changes in the implementation of
the <literal>NDBCLUSTER</literal> storage engine in mainline MySQL
5.1 releases up to and including MySQL 5.1.23 as compared to that in
- MySQL 5.0; &mccge-series; makes further changes and improvements in
- MySQL Cluster in addition to these. The changes and features most
+ MySQL 5.0; MySQL Cluster NDB makes further changes and improvements
+ in MySQL Cluster in addition to these. The changes and features most
likely to be of interest are shown in the following table:
<remark role="TODO">
@@ -96,7 +96,7 @@
<colspec colwidth="50*"/>
<thead>
<row>
- <entry><link linkend="mysql-cluster-changes-5-1-ndb-6-1">&mccge-series;
+ <entry><link linkend="mysql-cluster-changes-5-1-ndb-6-1">MySQL Cluster NDB
6.1</link></entry>
</row>
</thead>
@@ -122,7 +122,7 @@
<colspec colwidth="50*"/>
<thead>
<row>
- <entry><link linkend="mysql-cluster-changes-5-1-ndb-6-2">&mccge-series;
+ <entry><link linkend="mysql-cluster-changes-5-1-ndb-6-2">MySQL Cluster NDB
6.2</link></entry>
</row>
</thead>
@@ -159,7 +159,7 @@
<colspec colwidth="50*"/>
<thead>
<row>
- <entry><link linkend="mysql-cluster-changes-5-1-ndb-6-3">&mccge-series;
+ <entry><link linkend="mysql-cluster-changes-5-1-ndb-6-3">MySQL Cluster NDB
6.3</link></entry>
</row>
</thead>
@@ -215,9 +215,9 @@
<para>
A number of new features for MySQL Cluster have been implemented
in MySQL 5.1 through MySQL 5.1.23, when support for MySQL Cluster
- was moved to &mccge-series;. All of the features in the following
- list are also available in all &mccge-series; (6.1 and later)
- releases.
+ was moved to MySQL Cluster NDB. All of the features in the
+ following list are also available in all MySQL Cluster NDB (6.1
+ and later) releases.
</para>
<itemizedlist>
@@ -418,7 +418,8 @@
<para>
In mainline MySQL 5.1 releases, distribution awareness
was supported only when using the NDB API; support was
- added for SQL and API nodes in &mccge-series; 6.3 (see
+ added for SQL and API nodes in MySQL Cluster NDB 6.3
+ (see
<xref linkend="mysql-cluster-changes-5-1-ndb-6-3"/>,
which includes an example showing how to create a table
in order to take advantage of distribution awareness).
@@ -459,14 +460,15 @@
<section id="mysql-cluster-changes-5-1-ndb-6-1">
- <title>Features Added in &mccge-series; 6.1</title>
+ <title>Features Added in MySQL Cluster NDB 6.1</title>
<para>
The following list provides an overview of significant feature
- additions and changes made in &mccge-series; 6.1. All of the
- changes in this list are also available in &mccge-series; 6.2 and
- 6.3 releases. For detailed information about all changes made in
- &mccge-series; 6.1, see <xref linkend="mysql-cluster-news-6-1"/>.
+ additions and changes made in MySQL Cluster NDB 6.1. All of the
+ changes in this list are also available in MySQL Cluster NDB 6.2
+ and 6.3 releases. For detailed information about all changes made
+ in MySQL Cluster NDB 6.1, see
+ <xref linkend="mysql-cluster-news-6-1"/>.
<itemizedlist>
@@ -557,14 +559,14 @@
<section id="mysql-cluster-changes-5-1-ndb-6-2">
- <title>Features Added in &mccge-series; 6.2</title>
+ <title>Features Added in MySQL Cluster NDB 6.2</title>
<para>
The following list provides an overview of significant feature
- additions and changes made in &mccge-series; 6.2. All of the
- changes in this list are also available in &mccge-series; 6.3 .
+ additions and changes made in MySQL Cluster NDB 6.2. All of the
+ changes in this list are also available in MySQL Cluster NDB 6.3 .
For more detailed information about all feature changes and
- bugfixes made in &mccge-series; 6.2, see
+ bugfixes made in MySQL Cluster NDB 6.2, see
<xref linkend="mysql-cluster-news-6-2"/>.
<itemizedlist>
@@ -837,13 +839,13 @@
<section id="mysql-cluster-changes-5-1-ndb-6-3">
- <title>Features Added in &mccge-series; 6.3</title>
+ <title>Features Added in MySQL Cluster NDB 6.3</title>
<para>
The following list provides an overview of significant feature
- additions and changes first made in &mccge-series; 6.3. For more
- detailed information about all feature changes and bugfixes made
- in &mccge-series; 6.3, see
+ additions and changes first made in MySQL Cluster NDB 6.3. For
+ more detailed information about all feature changes and bugfixes
+ made in MySQL Cluster NDB 6.3, see
<xref linkend="mysql-cluster-news-6-3"/>.
<itemizedlist>
@@ -1163,7 +1165,7 @@
<title>Distribution awareness (SQL nodes)</title>
<para>
- In &mccge-series; 6.3, SQL nodes can take advantage of
+ In MySQL Cluster NDB 6.3, SQL nodes can take advantage of
<link linkend="mysql-cluster-changes-5-1-distribution-awareness">distribution
awareness</link>. Here we provide a brief example showing
how to design a table to make a given class of queries
Modified: trunk/it/refman-5.1/mysql-cluster-upgrade-downgrade.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-upgrade-downgrade.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-upgrade-downgrade.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 4, Lines Added: 9, Lines Deleted: 10; 2193 bytes
@@ -34,10 +34,9 @@
</para>
<para>
- For information about upgrading or downgrading between
- &mccge-series; releases, or between &mccge-series; releases and
- mainline MySQL releases, see the changelogs relating to
- &mccge-series;.
+ For information about upgrading or downgrading between MySQL Cluster
+ NDB releases, or between MySQL Cluster NDB releases and mainline
+ MySQL releases, see the changelogs relating to MySQL Cluster NDB.
</para>
<para>
@@ -553,14 +552,14 @@
</para>
<para>
- In order to minimize possible later difficulties, it is
+ In order to minimise possible later difficulties, it is
strongly advised that the procedure outlined above be followed
as soon as possible after to upgrading from MySQL 5.1.17 or
earlier to MySQL 5.1.18 or later.
</para>
<para>
- For users of &mccge-series; the relevant versions are as
+ For users of MySQL Cluster NDB the relevant versions are as
follows:
<itemizedlist>
@@ -568,11 +567,11 @@
<listitem>
<formalpara>
- <title>ndb-6.1.x series</title>
+ <title>MySQL Cluster NDB 6.1</title>
<para>
The new table format is implemented beginning with
- MySQL 5.1.15-ndb-6.1.7.
+ MySQL Cluster NDB 6.1.7.
</para>
</formalpara>
@@ -581,11 +580,11 @@
<listitem>
<formalpara>
- <title>ndb-6.2.x series</title>
+ <title>MySQL Cluster NDB 6.2</title>
<para>
The new table format is implemented beginning with
- MySQL 5.1.16-ndb-6.2.1.
+ MySQL Cluster NDB 6.2.1.
</para>
</formalpara>
Modified: trunk/it/refman-5.1/mysql-cluster-utilities.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster-utilities.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster-utilities.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 14, Lines Added: 26, Lines Deleted: 42; 6185 bytes
@@ -232,9 +232,7 @@
</listitem>
<listitem>
- &mccge-warning-begin;
-
- <para>
+ <para>
<command>ndbd_redo_log_reader</command>: Reads a redo log file,
checking it for errors, printing it in a human-readable format,
or both.
@@ -243,15 +241,12 @@
<note>
<para>
An alpha version of this utility was made available in MySQL
- 5.1.15-ndb-6.1.3. Currently, it should be considered
+ Cluster NDB 6.1.3. Currently, it should be considered
experimental.
</para>
</note>
+ </listitem>
- &mccge-warning-end-cluster;
-
- </listitem>
-
</itemizedlist>
<para>
@@ -285,7 +280,6 @@
<listitem>
<para>
<command>ndbd_redo_log_reader</command>
- (<emphasis>&mccge-series; only</emphasis>)
</para>
</listitem>
@@ -886,6 +880,7 @@
use <command>ndb_cpcd</command> in a production cluster.
</para>
+<!--
<remark role="TODO">
[js] Update following para with xref when info is added to
Internals Manual.
@@ -898,6 +893,7 @@
usage available in the near future as part of the MySQL
Internals Manual.
</para>
+-->
<para>
The source files for <command>ndb_cpcd</command> may be found
@@ -1586,14 +1582,10 @@
ndb_print_schema_file <replaceable>file_name</replaceable>
</programlisting>
- <remark role="todo">
- [js] Add link to discussion of cluster filesystem when that
- has been added to the Manual.
- </remark>
-
<para>
<replaceable>file_name</replaceable> is the name of a cluster
- schema file.
+ schema file. For more information about cluster schema files,
+ see <xref linkend="ndb-internals-ndbd-filesystemdir-files"/>.
</para>
<para>
@@ -1672,11 +1664,6 @@
ndb_print_sys_file <replaceable>file_name</replaceable>
</programlisting>
- <remark role="todo">
- [js] Add link to discussion of cluster filesystem when that
- has been added to the Manual.
- </remark>
-
<para>
<replaceable>file_name</replaceable> is the name of a cluster
system file (sysfile). Cluster system files are located in a
@@ -1684,7 +1671,9 @@
path under this directory to system files matches the pattern
<filename>ndb_<replaceable>#</replaceable>_fs/D<replaceable>#</replaceable>/DBDIH/P<replaceable>#</replaceable>.sysfile</filename>.
In each case, the <replaceable>#</replaceable> represents a
- number (not necessarily the same number).
+ number (not necessarily the same number). For more
+ information, see
+ <xref linkend="ndb-internals-ndbd-filesystemdir-files"/>.
</para>
<para>
@@ -1730,7 +1719,6 @@
<manvolnum>1</manvolnum>
<refmiscinfo class="manual">MySQL Database System</refmiscinfo>
<refmiscinfo class="source">MySQL</refmiscinfo>
- <refmiscinfo class="version">&mccge-series;</refmiscinfo>
<refmiscinfo class="refman">Check and Print Content of Cluster Redo Log</refmiscinfo>
</refmeta>
@@ -1750,9 +1738,7 @@
<title>Description</title>
- &mccge-warning-section;
-
- <para>
+ <para>
Reads a redo log file, checking it for errors, printing its
contents in a human-readable format, or both.
<command>ndbd_redo_log_reader</command> is intended for use
@@ -1761,11 +1747,11 @@
</para>
<para>
- This utility was made available as part of the default builds
- of &mccge-series; beginning with MySQL 5.1.15-ndb-6.1.3. It
- remains under development, and its syntax and behavior are
- subject to change in future releases. For this reason, it
- should be considered experimental at this time.
+ This utility was made available as part of default builds
+ beginning with MySQL Cluster NDB 6.1.3. It remains under
+ development, and its syntax and behavior are subject to change
+ in future releases. For this reason, it should be considered
+ experimental at this time.
</para>
<para>
@@ -1783,11 +1769,6 @@
ndbd_redo_log_reader <replaceable>file_name</replaceable> [<replaceable>options</replaceable>]
</programlisting>
- <remark role="todo">
- [js] Add link to discussion of cluster filesystem when that
- has been added to the Internals Manual.
- </remark>
-
<para>
<replaceable>file_name</replaceable> is the name of a cluster
REDO log file. REDO log files are located in the numbered
@@ -1796,7 +1777,9 @@
the REDO log files matches the pattern
<filename>ndb_<replaceable>#</replaceable>_fs/D<replaceable>#</replaceable>/LCP/<replaceable>#</replaceable>/T<replaceable>#</replaceable>F<replaceable>#</replaceable>.Data</filename>.
In each case, the <replaceable>#</replaceable> represents a
- number (not necessarily the same number).
+ number (not necessarily the same number). For more
+ information, see
+ <xref linkend="ndb-internals-ndbd-filesystemdir-files"/>.
</para>
<para>
@@ -2800,12 +2783,13 @@
</itemizedlist>
</para>
- <para>
- Beginning with MySQL 5.1.23
- (<emphasis>&mccge-series;</emphasis>: 5.1.22-ndb-6.2.5), the
- behavior of this utility and its available options have
- changed. (Bug #28683, Bug #28253)
- </para>
+ <note>
+ <para>
+ Beginning with MySQL 5.1.23 and MySQL Cluster NDB 6.2.5, the
+ behavior of this utility and its available options have
+ changed. (Bug #28683, Bug #28253)
+ </para>
+ </note>
<para>
Typical usage is shown here:
Modified: trunk/it/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/it/refman-5.1/mysql-cluster.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/mysql-cluster.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 4, Lines Added: 199, Lines Deleted: 36; 10800 bytes
@@ -33,7 +33,7 @@
</remark>
<para>
- This chapter contains information about <firstterm>MySQL
+ This chapter contains information about <firstterm>MySQL
Cluster</firstterm>, which is a high-availability, high-redundancy
version of MySQL adapted for the distributed computing environment,
using the <literal>NDB</literal> (also known as
@@ -46,36 +46,33 @@
releases through MySQL 5.1.23, including RPMs compatible with most
modern Linux distributions. Beginning with MySQL 5.1.24, standard
MySQL server binaries built by MySQL no longer provide support for
- the <literal>NDBCLUSTER</literal> storage engine. Instead, MySQL Cluster
- users should upgrade to &mccge-series; 6.2.15 (or a later
- &mccge-series; release) which includes binary releases for supported
+ the <literal>NDBCLUSTER</literal> storage engine. Instead, MySQL
+ Cluster users should upgrade to MySQL Cluster NDB 6.2.15 (or a later
+ MySQL Cluster release) which includes binary releases for supported
platforms, including RPMs that should work with most Linux
distributions. MySQL Cluster users who build from source should be
aware that, also beginning with MySQL 5.1.24,
<literal>NDBCLUSTER</literal> sources in the standard MySQL 5.1 tree
- are no longer maintained; these users should upgrade using the
- &mccge-series; 6.2.15 (or later) source release.
+ are no longer maintained; these users should upgrade using the MySQL
+ Cluster NDB 6.2.15 (or later) source release.
</para>
- <para>
- This chapter contains information about MySQL Cluster in MySQL 5.1
- mainline releases through MySQL 5.1.23, &mccge-series; 6.2 releases
- through &mccge-current-6.2;, and &mccge-series; 6.3 releases through
- &mccge-current-6.3;. It also contains historical information about
- the &mccge-series; 6.1 series, which is no longer in active
- development.
- </para>
-
<note>
<para>
- Binary releases and RPMs are not available for &mccge-series;
- prior to &mccge-series; 6.2.15.
+ MySQL Cluster NDB 6.1, 6.2, and 6.3 were formerly known as
+ <quote>MySQL Cluster Carrier Grade Edition</quote>. This
+ designation was dropped beginning with MySQL Cluster NDB 6.2.15
+ and MySQL Cluster NDB 6.3.14.
</para>
</note>
<para>
- For more information about MySQL &mccge-series;, see
- <xref linkend="mysql-cluster-cge"/>.
+ This chapter contains information about MySQL Cluster in MySQL 5.1
+ mainline releases through MySQL 5.1.23, MySQL Cluster NDB 6.2
+ releases through &mysql-cluster-current-6.2;, and MySQL Cluster NDB
+ 6.3 releases through &mysql-cluster-current-6.3;. It also contains
+ historical information about the MySQL Cluster NDB 6.1 series,
+ although this series is no longer in active development.
</para>
<indexterm>
@@ -83,23 +80,191 @@
<secondary>available platforms</secondary>
</indexterm>
- <para>
- MySQL Cluster is currently available and supported on a number of
- platforms, including Linux, Solaris, Mac OS X, HP-UX, and other
- Unix-style operating systems on a variety of hardware. For exact
- levels of support available for on specific combinations of
- operating system versions, operating system distributions, and
- hardware platforms, please refer to the
- <ulink url="http://www.mysql.com/support/supportedplatforms/cluster.html">Cluster
- Supported Platforms list</ulink> maintained by the MySQL Support
- Team on the MySQL AB Web site.
- </para>
+ <formalpara>
+ <title>Platforms supported</title>
+
+ <para>
+ MySQL Cluster is currently available and supported on a number of
+ platforms, including Linux, Solaris, Mac OS X, HP-UX, and other
+ Unix-style operating systems on a variety of hardware. For exact
+ levels of support available for on specific combinations of
+ operating system versions, operating system distributions, and
+ hardware platforms, please refer to the
+ <ulink url="http://www.mysql.com/support/supportedplatforms/cluster.html">Cluster
+ Supported Platforms list</ulink> maintained by the MySQL Support
+ Team on the MySQL AB Web site.
+
+ <important>
+ <para>
+ MySQL Cluster is <emphasis>not</emphasis> currently supported
+ on Microsoft Windows. We are working to make Cluster available
+ on all operating systems supported by MySQL, including
+ Windows, and will update the information provided here as this
+ work continues.
+ </para>
+ </important>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Availability</title>
+
+ <para>
+ MySQL Cluster NDB 6.2 binary and source packages are available for
+ supported platforms from
+ <ulink url="&base-url-cluster-downloads;"/>.
+
+ <note>
+ <para>
+ Binary releases and RPMs are not available for MySQL Cluster
+ NDB 6.2 prior to MySQL Cluster NDB 6.2.15.
+ </para>
+ </note>
+
+ MySQL Cluster NDB 6.3 is currently available only as source.
+ Source tarballs for the latest MySQL Cluster NDB 6.3 release can
+ be obtained from <ulink url="&base-url-cluster-files;"/>.
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>MySQL Cluster versioning</title>
+
+ <para>
+ Starting with MySQL Cluster NDB 6.1 and 6.2, MySQL Cluster follows
+ a somewhat different release pattern from the mainline MySQL 5.1
+ Cluster series of releases. Each MySQL Cluster release is
+ identified by a two-part version string, which is displayed by
+ <literal>SELECT VERSION()</literal> in the
+ <command>mysql</command> client, as shown here:
+
+<programlisting>
+shell> <userinput>mysql</userinput>
+Welcome to the MySQL monitor. Commands end with ; or \g.
+Your MySQL connection id is 2
+Server version: 5.1.24-ndb-6.2.16-debug Source distribution
+
+Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
+
+mysql> <userinput>SELECT VERSION();</userinput>
++-------------------------+
+| VERSION() |
++-------------------------+
+| 5.1.24-ndb-6.2.16-debug |
++-------------------------+
+1 row in set (0.00 sec)
+</programlisting>
+
+ This version string is also displayed in the output from the
+ <command>ndb_mgm</command> client's <literal>SHOW</literal>
+ command:
+
+<programlisting>
+ndb_mgm> <userinput>SHOW</userinput>
+Connected to Management Server at: localhost:1186
+Cluster Configuration
+---------------------
+[ndbd(NDB)] 2 node(s)
+id=1 @10.0.10.6 (mysql-5.1.24 ndb-6.2.15, Nodegroup: 0, Master)
+id=2 @10.0.10.8 (mysql-5.1.24 ndb-6.2.15, Nodegroup: 0)
+
+[ndb_mgmd(MGM)] 1 node(s)
+id=3 @10.0.10.2 (mysql-5.1.24 ndb-6.2.15)
+
+[mysqld(API)] 2 node(s)
+id=4 @10.0.10.10 (mysql-5.1.24 ndb-6.2.15)
+id=5 (not connected, accepting connect from any host)
+</programlisting>
+
+ The version string identifies the mainline MySQL version from
+ which the CGE release was branched and the version of the
+ <literal>NDB</literal> storage engine used. For example, the full
+ version string for MySQL Cluster NDB 6.1.15 (the first MySQL
+ Cluster NDB 6.2 binary release, as shown in the preceding
+ examples) is <literal>mysql-5.1.24 ndb-6.2.15</literal>. From this
+ we can determine the following information:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The portion of the version string preceding
+ <literal>ndb</literal> is the MySQL Server base version.
+ This means that MySQL Cluster NDB 6.2.15 derives from the
+ MySQL 5.1.24, and contains all feature enhancement and
+ bugfixes from MySQL 5.1 up to and including MySQL 5.1.24.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The portion of the version string following
+ <literal>ndb-</literal> represents the version number of the
+ <literal>NDB</literal> (or <literal>NDBCLUSTER</literal>)
+ storage engine. MySQL Cluster NDB 6.2.15 uses version 6.2.15
+ of the <literal>NDB</literal> storage engine.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>MySQL Cluster development source trees</title>
+
+ <para>
+ Three MySQL Cluster development trees can also be accessed via
+ <ulink url="http://mysql.bkbits.net/"/>:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal><ulink url="http://mysql.bkbits.net:8080/mysql-5.1-telco-6.1">MySQL
+ Cluster NDB 6.1</ulink></literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal><ulink url="http://mysql.bkbits.net:8080/mysql-5.1-telco-6.2">MySQL
+ Cluster NDB 6.2</ulink></literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal><ulink url="http://mysql.bkbits.net:8080/mysql-5.1-telco">MySQL
+ Cluster new development tree</ulink></literal>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ The MySQL Cluster development sources maintained at
+ <ulink url="http://mysql.bkbits.net/"/> are GPL-licensed. For
+ information about obtaining and building MySQL sources from
+ BitKeeper, see <xref linkend="installing-source-tree"/>.
+ </para>
+
+ </formalpara>
+
<para>
- MySQL Cluster is <emphasis>not</emphasis> currently supported on
- Microsoft Windows. We are working to make Cluster available on all
- operating systems supported by MySQL, including Windows, and will
- update the information provided here as this work continues.
+ Currently, MySQL Cluster NDB 6.2 and MySQL Cluster NDB 6.3 are both
+ under active development, with the 6.2 series intended for
+ production and 6.3 in beta. MySQL Cluster NDB 6.4 is beginning to be
+ developed internally and is intended for testing purposes. The
+ ndb-6.1.<replaceable>x</replaceable> series is no longer in active
+ development. For an overview of major features added in MySQL
+ Cluster, see <xref linkend="mysql-cluster-roadmap"/>.
</para>
<para>
@@ -170,8 +335,6 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="mysql-cluster-overview.xml"/>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="mysql-cluster-cge.xml"/>
-
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="mysql-cluster-multi-computer.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="mysql-cluster-configuration.xml"/>
Modified: trunk/it/refman-5.1/news-5.1-core.xml
===================================================================
--- trunk/it/refman-5.1/news-5.1-core.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/news-5.1-core.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 461 bytes
@@ -32,7 +32,7 @@
</para>
<para>
- For changes relating to &mccge-series;, see
+ For changes relating to MySQL Cluster NDB 6.x, see
<xref linkend="mysql-cluster-news"/>.
</para>
Modified: trunk/it/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/it/refman-5.1/sql-syntax.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/it/refman-5.1/sql-syntax.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 13, Lines Added: 43, Lines Deleted: 80; 9635 bytes
@@ -634,9 +634,6 @@
</listitem>
<listitem>
-
- &mccge-warning-begin;
-
<para>
The <literal>ONLINE</literal> keyword can be used to perform
online <literal>ADD COLUMN</literal>, <literal>ADD
@@ -836,7 +833,7 @@
<para>
The <literal>ONLINE</literal> keyword was added in MySQL
- 5.1.22-ndb-6.2.5 and MySQL 5.1.22-ndb-6.3.2.
+ Cluster NDB 6.2.5 and MySQL Cluster NDB 6.3.2.
</para>
<note>
@@ -849,9 +846,6 @@
<xref linkend="drop-index"/>, for more information.
</para>
</note>
-
- &mccge-warning-end-all;
-
</listitem>
<listitem>
@@ -2396,26 +2390,22 @@
<literal>utf8</literal> columns require up to three index bytes
per character.
</para>
-
- &mccge-warning-begin;
-
+
<para>
- Beginning with MySQL 5.1.22-ndb-6.2.5 and MySQL
- 5.1.22-ndb-6.3.3, you can add indexes to <literal>NDB</literal>
- tables online, using the <literal>ONLINE</literal> keyword. This
- means that the creation of the index does not require the
- affected table to be copied (and so the table is not locked)
- while the index is created. You can also add indexes offline
- (which causes the table to be locked) using
- <literal>OFFLINE</literal>. The rules and limitations governing
- online <literal>CREATE ONLINE INDEX</literal> and
- <literal>CREATE OFFLINE INDEX</literal> are the same as for
- <literal>ALTER ONLINE TABLE ... ADD INDEX</literal> and
- <literal>ALTER OFFLINE TABLE ... ADD INDEX</literal>. For more
- information, see <xref linkend="alter-table"/>.
+ Beginning with MySQL Cluster NDB 6.2.5 and MySQL Cluster NDB
+ 6.3.3, you can add indexes to <literal>NDB</literal> tables
+ online, using the <literal>ONLINE</literal> keyword. This means
+ that the creation of the index does not require the affected
+ table to be copied (and so the table is not locked) while the
+ index is created. You can also add indexes offline (which causes
+ the table to be locked) using <literal>OFFLINE</literal>. The
+ rules and limitations governing online <literal>CREATE ONLINE
+ INDEX</literal> and <literal>CREATE OFFLINE INDEX</literal> are
+ the same as for <literal>ALTER ONLINE TABLE ... ADD
+ INDEX</literal> and <literal>ALTER OFFLINE TABLE ... ADD
+ INDEX</literal>. For more information, see
+ <xref linkend="alter-table"/>.
</para>
-
- &mccge-warning-end-all;
<para>
A <literal>UNIQUE</literal> index creates a constraint such that
@@ -3450,23 +3440,19 @@
</listitem>
<listitem>
-
- &mccge-warning-begin;
-
<para>
<indexterm>
<primary>column format</primary>
</indexterm>
- Beginning with MySQL 5.1.19-ndb-6.2.5 and MySQL
- 5.1.20-ndb-6.3.2, it is also possible to specify a data
- storage format for individual columns of
- <literal>NDB</literal> tables using
- <literal>COLUMN_FORMAT</literal>. Allowable column formats
- are <literal>FIXED</literal>, <literal>DYNAMIC</literal>,
- and <literal>DEFAULT</literal>. <literal>FIXED</literal> is
- used to specify fixed-width storage,
- <literal>DYNAMIC</literal> allows the column to be
+ Beginning with MySQL Cluster NDB 6.2.5 and MySQL Cluster NDB
+ 6.3.2, it is also possible to specify a data storage format
+ for individual columns of <literal>NDB</literal> tables
+ using <literal>COLUMN_FORMAT</literal>. Allowable column
+ formats are <literal>FIXED</literal>,
+ <literal>DYNAMIC</literal>, and <literal>DEFAULT</literal>.
+ <literal>FIXED</literal> is used to specify fixed-width
+ storage, <literal>DYNAMIC</literal> allows the column to be
variable-width, and <literal>DEFAULT</literal> causes the
column to use fixed-width or variable-width storage as
determined by the column's data type (possibly overridden by
@@ -3487,15 +3473,13 @@
</listitem>
<listitem>
- &mccge-warning-begin;
-
<para>
<indexterm>
<primary>column storage</primary>
</indexterm>
For <literal>NDB</literal> tables, beginning with MySQL
- 5.1.19-ndb-6.2.5 and MySQL 5.1.20-ndb-6.3.2, it is also
+ Cluster NDB 6.2.5 and MySQL Cluster NDB 6.3.2, it is also
possible to specify whether the column is stored on disk or
in memory by using a <literal>STORAGE</literal> clause.
<literal>STORAGE DISK</literal> causes the column to be
@@ -3513,8 +3497,6 @@
tables using storage engines other than
<literal>NDB</literal>.
</para>
-
- &mccge-warning-end-all;
</listitem>
<listitem>
@@ -5662,32 +5644,22 @@
</para>
<remark role="help-description-end"/>
-
- &mccge-warning-begin;
-
+
<para>
- For <literal>NDB</literal> tables, beginning with MySQL
- 5.1.22-ndb-6.2.5 and MySQL 5.1.22-ndb-6.3.3, you can drop
- indexes online, using the <literal>ONLINE</literal> keyword.
- This means that the <literal>DROP</literal> operation does not
- require the affected table to be copied (and so the table is not
- locked). You can also drop indexes offline (which causes the
- table to be locked) using <literal>OFFLINE</literal>. The rules
- and limitations governing online <literal>DROP ONLINE
+ For <literal>NDB</literal> tables, beginning with MySQL Cluster
+ NDB 6.2.5 and MySQL Cluster NDB 6.3.3, you can drop indexes
+ online, using the <literal>ONLINE</literal> keyword. This means
+ that the <literal>DROP</literal> operation does not require the
+ affected table to be copied (and so the table is not locked).
+ You can also drop indexes offline (which causes the table to be
+ locked) using <literal>OFFLINE</literal>. The rules and
+ limitations governing online <literal>DROP ONLINE
INDEX</literal> and <literal>ADD OFFLINE INDEX</literal> are the
same as for <literal>ALTER ONLINE TABLE ... DROP INDEX</literal>
and <literal>ALTER OFFLINE TABLE ... DROP INDEX</literal>. For
more information, see <xref linkend="alter-table"/>.
</para>
- <remark role="NOTE">
- [js] Uncomment next item if more text is added following it.
- </remark>
-
-<!--
- &mccge-warning-end-all;
--->
-
</section>
<section id="drop-logfile-group">
@@ -18625,16 +18597,13 @@
created using any other storage engine, including
<literal>NDB</literal> Disk Data tables.
</para>
-
- &mccge-warning-begin;
-
+
<para>
- In MySQL 5.1.23-ndb-6.3.7 and later &mccge-series;
- 6.3.<replaceable>x</replaceable> releases, <literal>OPTIMIZE
- TABLE</literal> is supported for dynamic columns of in-memory
- <literal>NDB</literal> tables. The performance of
- <literal>OPTIMIZE</literal> on Cluster tables can be tuned by
- adjusting the value of the
+ In MySQL Cluster NDB 6.3.7 and later MySQL Cluster NDB 6.3
+ releases, <literal>OPTIMIZE TABLE</literal> is supported for
+ dynamic columns of in-memory <literal>NDB</literal> tables.
+ The performance of <literal>OPTIMIZE</literal> on Cluster
+ tables can be tuned by adjusting the value of the
<literal>ndb_optimization_delay</literal> system variable,
which controls the number of milliseconds to wait between
processing batches of rows by <literal>OPTIMIZE
@@ -18644,13 +18613,11 @@
</para>
<para>
- Beginning with MySQL 5.1.23-ndb-6.3.8, <literal>OPTIMIZE
+ Beginning with MySQL Cluster NDB 6.3.8, <literal>OPTIMIZE
TABLE</literal> can be interrupted by (for example) killing
the SQL thread performing the <literal>OPTIMIZE</literal>
operation.
</para>
-
- &mccge-warning-end-cluster;
<para>
For <literal>MyISAM</literal> tables, <literal>OPTIMIZE
@@ -25865,9 +25832,7 @@
<literal>localhost</literal>, then, like in other parts of
MySQL, the port number might be ignored.
</para>
-
- &mccge-warning-begin;
-
+
<para>
<literal>MASTER_BIND</literal> is for use on replication
slaves having multiple network interfaces, and determines
@@ -25880,7 +25845,7 @@
<para>
The ability to bind a replication slave to specific network
- interface was added in MySQL 5.1.22-ndb-6.3.4.
+ interface was added in MySQL Cluster NDB 6.3.4.
</para>
<para>
@@ -25918,10 +25883,8 @@
<para>
<literal>MASTER_HEARTBEAT_PERIOD</literal> was added in MySQL
- 5.1.22-ndb-6.3.4.
+ Cluster NDB 6.3.4.
</para>
-
- &mccge-warning-end-all;
<note>
<para>
Modified: trunk/ndbapi/class-dictionary.xml
===================================================================
--- trunk/ndbapi/class-dictionary.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/ndbapi/class-dictionary.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 6, Lines Added: 6, Lines Deleted: 19; 1839 bytes
@@ -180,12 +180,6 @@
<entry><literal>listEvents()</literal></entry>
<entry><para>
Fetches a list of the events defined in the dictionary
- </para>
-
-
-
- <para role="telco-warning">
- This method is available in &mccge-series; only.
</para></entry>
</row>
<row>
@@ -1535,11 +1529,8 @@
<primary>createRecord() (method of Dictionary)</primary>
</indexterm>
+ <formalpara>
- &mccge-warning-section;
-
- <formalpara>
-
<title>Description</title>
<para>
@@ -1551,8 +1542,8 @@
</formalpara>
<para>
- <literal>Dctionary::createRecord()</literal> is available in
- &mccge-series; releases beginning with MySQL 5.1.19-ndb-6.2.3.
+ <literal>Dctionary::createRecord()</literal> is available
+ beginning with MySQL Cluster NDB 6.2.3.
</para>
<formalpara>
@@ -2554,10 +2545,8 @@
<title><literal>Dictionary::listEvents()</literal></title>
- &mccge-warning-section;
+ <formalpara>
- <formalpara>
-
<title>Description</title>
<para>
@@ -2568,7 +2557,7 @@
</formalpara>
<para>
- This method was added in MySQL 5.1.15-ndb-6.1.13.
+ This method was added in MySQL Cluster NDB 6.1.13.
</para>
<formalpara>
@@ -2643,10 +2632,8 @@
<indexterm>
<primary>releaseRecord() (method of Dictionary)</primary>
</indexterm>
-
- &mccge-warning-section;
- <formalpara>
+ <formalpara>
<title>Description</title>
Modified: trunk/ndbapi/class-ndb-cluster-connection.xml
===================================================================
--- trunk/ndbapi/class-ndb-cluster-connection.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/ndbapi/class-ndb-cluster-connection.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 7, Lines Added: 4, Lines Deleted: 28; 2220 bytes
@@ -230,12 +230,6 @@
<entry><para>
Disables the creation of new <literal>Ndb</literal>
objects.
- </para>
-
-
-
- <para role="telco-warning">
- This method is available in &mccge-series; only.
</para></entry>
</row>
<row>
@@ -243,12 +237,6 @@
<entry><para>
Enables the creation of new <literal>Ndb</literal>
objects.
- </para>
-
-
-
- <para role="telco-warning">
- This method is available in &mccge-series; only.
</para></entry>
</row>
<row>
@@ -256,12 +244,6 @@
<entry><para>
Used to iterate through multiple <literal>Ndb</literal>
objects.
- </para>
-
-
-
- <para role="telco-warning">
- This method is available in &mccge-series; only.
</para></entry>
</row>
</tbody>
@@ -886,10 +868,8 @@
<secondary>Ndb objects</secondary>
</indexterm>
- &mccge-warning-section;
+ <formalpara>
- <formalpara>
-
<title>Description</title>
<para>
@@ -1011,10 +991,8 @@
<title><literal>ndb_cluster_connection::lock_ndb_objects()</literal></title>
- &mccge-warning-section;
+ <formalpara>
- <formalpara>
-
<title>Description</title>
<para>
@@ -1062,7 +1040,7 @@
</formalpara>
<para>
- This method was added in MySQL 5.1.15-ndb-6.1.4. For more
+ This method was added in MySQL Cluster NDB 6.1.4. For more
information, see
<xref linkend="class-ndb-cluster-connection-get-next-ndb-object"/>.
</para>
@@ -1086,10 +1064,8 @@
<title><literal>ndb_cluster_connection::unlock_ndb_objects()</literal></title>
- &mccge-warning-section;
+ <formalpara>
- <formalpara>
-
<title>Description</title>
<para>
Modified: trunk/ndbapi/class-ndb.xml
===================================================================
--- trunk/ndbapi/class-ndb.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/ndbapi/class-ndb.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 3, Lines Added: 10, Lines Deleted: 17; 1925 bytes
@@ -945,14 +945,12 @@
</formalpara>
- &mccge-warning-begin;
-
<formalpara>
<title>Distribution-aware form of <literal>startTransaction()</literal></title>
<para>
- Beginning with MySQL 5.1.15-ndb-6.1.4, it is possible to
+ Beginning with MySQL Cluster NDB 6.1.4, it is possible to
employ <firstterm>distribution awareness</firstterm> with this
method — that is, to suggest which node should act as
the transaction coordinator. When
@@ -1135,8 +1133,6 @@
to <literal>startTransaction()</literal> was successful.
</para>
- &mccge-warning-end-api;
-
<formalpara>
<title>Return Value</title>
@@ -1428,20 +1424,17 @@
</para>
</formalpara>
-
- &mccge-warning-begin;
-
- <para>
- Beginning with MySQL 5.1.22-ndb-6.2.5, this method waits for the
- next <emphasis>epoch</emphasis>, rather than the next GCP. See
- <xref linkend="class-ndbeventoperation"/>, for more information
- about the differences in event handling for this and later
- &mccge-series; 6.2.<replaceable>x</replaceable> releases.
+
+ <para>
+ Beginning with MySQL Cluster NDB 6.2.5, this method waits for
+ the next <emphasis>epoch</emphasis>, rather than the next GCP.
+ See <xref linkend="class-ndbeventoperation"/>, for more
+ information about the differences in event handling for this and
+ later MySQL Cluster NDB 6.2.<replaceable>x</replaceable>
+ releases.
</para>
-
- &mccge-warning-end-api;
- <formalpara>
+ <formalpara>
<title>Signature</title>
Modified: trunk/ndbapi/class-ndbeventoperation.xml
===================================================================
--- trunk/ndbapi/class-ndbeventoperation.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/ndbapi/class-ndbeventoperation.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 13; 1334 bytes
@@ -1117,22 +1117,17 @@
</para>
</formalpara>
-
- &mccge-warning-begin;
-
- <para>
- Beginning with MySQL 5.1.22-ndb-6.2.5, this method actually
+
+ <para>
+ Beginning with MySQL Cluster NDB 6.2.5, this method actually
returns the latest epoch number, and all references to GCIs in
- the documentation for this method when using this &mccge-series;
- version or a later &mccge-series;
- 6.2.<replaceable>x</replaceable> version should be taken to mean
- epoch numbers instead. This is a consequence of the
- implementation for micro-CGPs.
+ the documentation for this method when using this or a later
+ MySQL Cluster NDB version should be taken to mean epoch numbers
+ instead. This is a consequence of the implementation for
+ micro-CGPs.
</para>
-
- &mccge-warning-end-api;
- <note>
+ <note>
<para>
The GCI obtained using this method is not necessarily
associated with an event.
Modified: trunk/ndbapi/class-ndbindexscanoperation.xml
===================================================================
--- trunk/ndbapi/class-ndbindexscanoperation.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/ndbapi/class-ndbindexscanoperation.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 8; 870 bytes
@@ -136,20 +136,16 @@
</para>
</formalpara>
-
- &mccge-warning-begin;
-
- <para>
- Beginning with MySQL 5.1.19-ndb-6.2.3, this class defines an
+
+ <para>
+ Beginning with MySQL Cluster NDB 6.2.3, this class defines an
additional struct for use with operations employing
<literal>NdbRecord</literal>; see
<xref linkend="struct-indexbound"/>, and
<xref linkend="interface-ndbrecord"/>, for more information.
</para>
-
- &mccge-warning-end-api;
- <formalpara>
+ <formalpara>
<title>Class diagram</title>
Modified: trunk/ndbapi/class-ndbscanoperation.xml
===================================================================
--- trunk/ndbapi/class-ndbscanoperation.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/ndbapi/class-ndbscanoperation.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 12, Lines Added: 35, Lines Deleted: 55; 5267 bytes
@@ -438,9 +438,8 @@
)
</programlisting>
- In &mccge-series; releases beginning with MySQL
- 5.1.19-ndb-6.2.3, it is also possible to use this method as
- shown here:
+ Beginning with MySQL Cluster NDB 6.2.3, it is also possible to
+ use this method as shown here:
<programlisting>
int nextResult
@@ -532,17 +531,14 @@
</para>
</formalpara>
-
- &mccge-warning-begin;
-
- <formalpara>
+ <formalpara>
+
<title>Parameters</title>
<para>
- In &mccge-series; releases beginning with MySQL
- 5.1.19-ndb-6.2.3, this method can also be called with the
- following parameters:
+ Beginning with MySQL Cluster NDB 6.2.3, this method can also
+ be called with the following parameters:
<itemizedlist>
@@ -585,10 +581,8 @@
</para>
</formalpara>
-
- &mccge-warning-end-api;
- <formalpara>
+ <formalpara>
<title>Return Value</title>
@@ -792,9 +786,9 @@
)
</programlisting>
- In &mccge-series; releases beginning with MySQL
- 5.1.19-ndb-6.2.3, the following signature is also supported
- for this method, when using <literal>NdbRecord</literal>:
+ Beginning with MySQL Cluster NDB 6.2.3, the following
+ signature is also supported for this method, when using
+ <literal>NdbRecord</literal>:
<programlisting>
NdbOperation *lockCurrentTuple
@@ -820,15 +814,13 @@
</para>
</formalpara>
-
- &mccge-warning-begin;
-
- <formalpara>
- <title>Parameters</title>
+ <formalpara>
+ <title>Parameters when using <literal>NdbRecord</literal></title>
+
<para>
- When using <literal>NdbRecord</literal> in &mccge-series; (see
+ When using the <literal>NdbRecord</literal> interface (see
<xref linkend="interface-ndbrecord"/>), this method takes
these parameters, as described in the following list:
@@ -881,10 +873,8 @@
takeover on an <literal>NdbRecord</literal>-style scan.
</para>
</important>
-
- &mccge-warning-end-api;
- <formalpara>
+ <formalpara>
<title>Return Value</title>
@@ -956,10 +946,9 @@
)
</programlisting>
- In &mccge-series; releases beginning with MySQL
- 5.1.19-ndb-6.2.3, it is also possible to employ this method,
- when using <literal>NdbRecord</literal> with scans, as shown
- here:
+ Beginning with MySQL Cluster NDB 6.2.3, it is also possible to
+ employ this method, when using <literal>NdbRecord</literal>
+ with scans, as shown here:
<programlisting>
NdbOperation* updateCurrentTuple
@@ -988,17 +977,15 @@
</para>
</formalpara>
-
- &mccge-warning-begin;
-
- <formalpara>
- <title>Parameters</title>
+ <formalpara>
+ <title>Parameters when using <literal>NdbRecord</literal></title>
+
<para>
- When using <literal>NdbRecord</literal> in &mccge-series;
- releases beginning with MySQL 5.1.19-ndb-6.2.3, this method
- takes the following parameters, as described here:
+ When using the <literal>NdbRecord</literal> interface
+ (beginning with MySQL Cluster NDB 6.2.3), this method takes
+ the following parameters, as described here:
<itemizedlist>
@@ -1038,11 +1025,8 @@
</para>
</formalpara>
-
-
- &mccge-warning-end-api;
- <formalpara>
+ <formalpara>
<title>Return Value</title>
@@ -1113,9 +1097,9 @@
)
</programlisting>
- In &mccge-series; releases beginning with MySQL
- 5.1.19-ndb-6.2.3, this method's signature when performing
- <literal>NdbRecord</literal>-style scans is shown here:
+ Beginning with MySQL Cluster NDB 6.2.3, this method's
+ signature when performing <literal>NdbRecord</literal>-style
+ scans is shown here:
<programlisting>
</programlisting>
@@ -1137,17 +1121,15 @@
</para>
</formalpara>
-
- &mccge-warning-begin;
-
- <formalpara>
- <title>Parameters</title>
+ <formalpara>
+ <title>Parameters when using <literal>NdbRecord</literal></title>
+
<para>
- When used with <literal>NdbRecord</literal> in &mccge-series;
- releases beginning with MySQL 5.1.19-ndb-6.2.3, this method
- takes two parameters, as shown here:
+ When used with the <literal>NdbRecord</literal> interface
+ (beginning with MySQL Cluster NDB 6.2.3), this method takes
+ two parameters, as shown here:
<itemizedlist>
@@ -1171,10 +1153,8 @@
</para>
</formalpara>
-
- &mccge-warning-end-api;
- <formalpara>
+ <formalpara>
<title>Return Value</title>
Modified: trunk/ndbapi/class-ndbtransaction.xml
===================================================================
--- trunk/ndbapi/class-ndbtransaction.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/ndbapi/class-ndbtransaction.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 9, Lines Added: 12, Lines Deleted: 26; 3014 bytes
@@ -314,8 +314,8 @@
<literal>updateTuple()</literal>, <literal>writeTuple()</literal>,
<literal>deleteTuple()</literal>, <literal>scanTable()</literal>,
and <literal>scanIndex()</literal> require the use of
- <literal>NdbRecord</literal>, which is available only in
- &mccge-series; releases beginning with MySQL 5.1.19-ndb-6.2.3.
+ <literal>NdbRecord</literal>, which is available beginning with
+ MySQL Cluster NDB 6.2.3.
</para>
</important>
@@ -395,9 +395,9 @@
<literal>insertTuple()</literal>,
<literal>updateTuple()</literal>, <literal>writeTuple()</literal>,
<literal>deleteTuple()</literal>, <literal>scanTable()</literal>,
- and <literal>scanIndex()</literal> (available only in
- &mccge-series; releases beginning with MySQL 5.1.19-ndb-6.2.3) are
- not shown in the diagram due to space cosniderations.
+ and <literal>scanIndex()</literal> (available beginning with MySQL
+ Cluster NDB 6.2.3) are not shown in the diagram due to space
+ cosniderations.
</para>
</note>
@@ -1943,10 +1943,8 @@
<indexterm>
<primary>readTuple() (method of NdbTransaction)</primary>
</indexterm>
-
- &mccge-warning-section;
- <formalpara>
+ <formalpara>
<title>Description</title>
@@ -2083,10 +2081,8 @@
<indexterm>
<primary>insertTuple() (method of NdbTransaction)</primary>
</indexterm>
-
- &mccge-warning-section;
- <formalpara>
+ <formalpara>
<title>Description</title>
@@ -2185,10 +2181,8 @@
<indexterm>
<primary>updateTuple() (method of NdbTransaction)</primary>
</indexterm>
-
- &mccge-warning-section;
- <formalpara>
+ <formalpara>
<title>Description</title>
@@ -2324,10 +2318,8 @@
<indexterm>
<primary>writeTuple() (method of NdbTransaction)</primary>
</indexterm>
-
- &mccge-warning-section;
- <formalpara>
+ <formalpara>
<title>Description</title>
@@ -2462,10 +2454,8 @@
<indexterm>
<primary>deleteTuple() (method of NdbTransaction)</primary>
</indexterm>
-
- &mccge-warning-section;
- <formalpara>
+ <formalpara>
<title>Description</title>
@@ -2565,10 +2555,8 @@
<indexterm>
<primary>scanTable() (method of NdbTransaction)</primary>
</indexterm>
-
- &mccge-warning-section;
- <formalpara>
+ <formalpara>
<title>Description</title>
@@ -2711,10 +2699,8 @@
<indexterm>
<primary>scanIndex() (method of NdbTransaction)</primary>
</indexterm>
-
- &mccge-warning-section;
- <formalpara>
+ <formalpara>
<title>Description</title>
Modified: trunk/ndbapi/interface-ndbrecord.xml
===================================================================
--- trunk/ndbapi/interface-ndbrecord.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/ndbapi/interface-ndbrecord.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 3, Lines Added: 6, Lines Deleted: 8; 1787 bytes
@@ -6,16 +6,14 @@
<section id="interface-ndbrecord">
<title>The <literal>NdbRecord</literal> Interface</title>
-
- &mccge-warning-section;
<para>
<literal>NdbRecord</literal> is an interface which provides a
mapping to a full or a partial record stored in
<literal>NDB</literal>. In the latter case, it can be used in
conjunction with a bitmap to assist in access.
- <literal>NdbRecord</literal> is available in &mccge-series; releases
- beginning with MySQL 5.1.19-ndb-6.2.3.
+ <literal>NdbRecord</literal> is available beginning with MySQL
+ Cluster NDB 6.2.3.
</para>
<para>
@@ -61,8 +59,8 @@
<literal>createRecord()</literal> method of the
<literal>NdbDictionary</literal> class. In addition, a number of
<literal>NDB</literal> API methods have additional declarations in
- MySQL 5.1.19-ndb-6.2.3 and later &mccge-series; releases that allow
- the programmer to leverage <literal>NdbRecord</literal>:
+ MySQL Cluster NDB 6.2.3 and later MySQL Cluster NDB 6.x releases
+ that allow the programmer to leverage <literal>NdbRecord</literal>:
<itemizedlist>
@@ -147,8 +145,8 @@
</itemizedlist>
In addition, new members of <literal>NdbIndexScanOperation</literal>
- and <literal>NdbDictionary</literal> are introduced in MySQL
- 5.1.19-ndb-6.2.3 for use with <literal>NdbRecord</literal> scans:
+ and <literal>NdbDictionary</literal> are introduced in MySQL Cluster
+ NDB 6.2.3 for use with <literal>NdbRecord</literal> scans:
<itemizedlist>
Modified: trunk/ndbapi/ndb-examples.xml
===================================================================
--- trunk/ndbapi/ndb-examples.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/ndbapi/ndb-examples.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 7; 1097 bytes
@@ -2383,8 +2383,6 @@
<primary>NdbRecord</primary>
<secondary>example</secondary>
</indexterm>
-
- &mccge-warning-section;
<abstract>
@@ -3860,16 +3858,14 @@
<primary>NdbRecord</primary>
<secondary>example</secondary>
</indexterm>
-
- &mccge-warning-section;
-
- <abstract>
+ <abstract>
+
<para>
This example illustrates the manipulation of a
<literal>BLOB</literal> column in the <literal>NDB</literal> API
using the <literal>NdbRecord</literal> interface available
- beginning with MySQL 5.1.19-ndb-6.2.3. It demonstrates how to
+ beginning with MySQL Cluster NDB 6.2.3. It demonstrates how to
perform insert, read, and update operations, using both inline
value buffers as well as read and write methods. It can be found
in the file
Modified: trunk/ndbapi/ndb-internals.xml
===================================================================
--- trunk/ndbapi/ndb-internals.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/ndbapi/ndb-internals.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 9, Lines Added: 10, Lines Deleted: 20; 2760 bytes
@@ -3089,10 +3089,8 @@
<section id="ndb-internals-dump-command-2350">
<title><literal>DUMP 2350</literal></title>
-
- &mccge-warning-section;
- <informaltable>
+ <informaltable>
<tgroup cols="3">
<colspec colwidth="15*"/>
<colspec colwidth="30*"/>
@@ -3454,8 +3452,8 @@
</formalpara>
<para>
- This command was added in MySQL 5.1.15-ndb-6.1.12 and MySQL
- 5.1.18-ndb-6.2.2.
+ This command was added in MySQL Cluster NDB 6.1.12 and MySQL
+ Cluster NDB 6.2.2.
</para>
</section>
@@ -3540,8 +3538,8 @@
</formalpara>
<para>
- This command was added in MySQL 5.1.15-ndb-6.1.12 and MySQL
- 5.1.18-ndb-6.2.2.
+ This command was added in MySQL Cluster NDB 6.1.12 and MySQL
+ Cluster NDB 6.2.2.
</para>
</section>
@@ -5305,8 +5303,6 @@
<section id="ndb-internals-dump-command-2550">
<title><literal>DUMP 2550</literal></title>
-
- &mccge-warning-section;
<informaltable>
<tgroup cols="3">
@@ -5401,8 +5397,8 @@
</formalpara>
<para>
- This command was added in MySQL 5.1.15-ndb-6.1.12 and MySQL
- 5.1.18-ndb-6.2.2.
+ This command was added in MySQL Cluster NDB 6.1.12 and MySQL
+ Cluster NDB 6.2.2.
</para>
</section>
@@ -7404,10 +7400,8 @@
<section id="ndb-internals-dump-command-7901">
<title><literal>DUMP 7901</literal></title>
-
- &mccge-warning-section;
- <informaltable>
+ <informaltable>
<tgroup cols="3">
<colspec colwidth="15*"/>
<colspec colwidth="30*"/>
@@ -7454,9 +7448,7 @@
<title>Additional Information</title>
<para>
- Currently available only in MySQL 5.1.15-ndb-6.1.19 and
- later &mccge-series; 6.1.<replaceable>x</replaceable>
- releases.
+ Available beginning with MySQL Cluster NDB 6.1.19.
</para>
</formalpara>
@@ -7605,8 +7597,6 @@
<section id="ndb-internals-dump-command-8011">
<title><literal>DUMP 8011</literal></title>
-
- &mccge-warning-section;
<informaltable>
<tgroup cols="3">
@@ -7672,7 +7662,7 @@
<title>Additional Information</title>
<para>
- Added in MySQL 5.1.22-ndb-6.2.9.
+ Added in MySQL Cluster NDB 6.2.9.
</para>
</formalpara>
Modified: trunk/ndbapi/struct-indexbound.xml
===================================================================
--- trunk/ndbapi/struct-indexbound.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/ndbapi/struct-indexbound.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 5; 796 bytes
@@ -6,9 +6,7 @@
<section id="struct-indexbound">
<title>The <literal>IndexBound</literal> Structure</title>
-
- &mccge-warning-section;
-
+
<formalpara>
<title>Parent class</title>
@@ -26,8 +24,7 @@
<para>
<literal>IndexBound</literal> is a structure used to describe
index scan bounds for <literal>NdbRecord</literal> scans. It is
- available in &mccge-series; releases begining with MySQL
- 5.1.19-ndb-6.2.3.
+ available beginning with MySQL Cluster NDB 6.2.3.
</para>
</formalpara>
Modified: trunk/ndbapi/struct-recordspecification.xml
===================================================================
--- trunk/ndbapi/struct-recordspecification.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/ndbapi/struct-recordspecification.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 1; 424 bytes
@@ -7,7 +7,6 @@
<title>The <literal>RecordSpecification</literal> Structure</title>
- &mccge-warning-section;
<formalpara>
Modified: trunk/pt/refman-5.1/Makefile.depends
===================================================================
--- trunk/pt/refman-5.1/Makefile.depends 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/pt/refman-5.1/Makefile.depends 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 16, Lines Added: 11, Lines Deleted: 41; 8380 bytes
@@ -728,7 +728,6 @@
../../refman-5.1/metadata/installing-core.idmap \
../../refman-5.1/metadata/introduction.idmap \
../../refman-5.1/metadata/mysql-cluster-backup.idmap \
- ../../refman-5.1/metadata/mysql-cluster-cge.idmap \
../../refman-5.1/metadata/mysql-cluster-configuration.idmap \
../../refman-5.1/metadata/mysql-cluster-limitations.idmap \
../../refman-5.1/metadata/mysql-cluster-management.idmap \
@@ -736,11 +735,11 @@
../../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.idmap \
- ../../refman-5.1/metadata/mysql-cluster-upgrade-downgrade.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../../refman-5.1/metadata/mysql-cluster-utilities.idmap \
+ ../../refman-5.1/metadata/mysql-cluster.idmap \
../../refman-5.1/metadata/news-5.1-core.idmap \
- ../../refman-5.1/metadata/sql-syntax.idmap \
- ../../refman-6.0/metadata/mysql-cluster-cge.idmap
+ ../../refman-5.1/metadata/sql-syntax.idmap
dynxml-local-mysql-cluster-news.validpure: $(dynxml_local_mysql_cluster_news_SOURCES)
dynxml-local-mysql-cluster-news.titles: $(dynxml_local_mysql_cluster_news_SOURCES)
dynxml-local-mysql-cluster-news.useless: $(dynxml_local_mysql_cluster_news_SOURCES)
@@ -763,7 +762,6 @@
dynxml_local_mysql_cluster_optvar_SOURCES = dynxml-local-mysql-cluster-optvar.xml $(dynxml_local_mysql_cluster_optvar_INCLUDES)
dynxml_local_mysql_cluster_optvar_IDMAPS = \
../../refman-5.1/metadata/dba-core.idmap \
- ../../refman-5.1/metadata/mysql-cluster-cge.idmap \
../../refman-5.1/metadata/mysql-cluster-configuration.idmap \
../../refman-5.1/metadata/mysql-cluster-optvar-core.idmap \
../../refman-5.1/metadata/mysql-cluster-process-management.idmap \
@@ -804,7 +802,6 @@
../../refman-5.1/metadata/introduction.idmap \
../../refman-5.1/metadata/language-structure-core.idmap \
../../refman-5.1/metadata/mysql-cluster-backup.idmap \
- ../../refman-5.1/metadata/mysql-cluster-cge.idmap \
../../refman-5.1/metadata/mysql-cluster-configuration.idmap \
../../refman-5.1/metadata/mysql-cluster-interconnects.idmap \
../../refman-5.1/metadata/mysql-cluster-management.idmap \
@@ -1270,6 +1267,7 @@
../../refman-5.1/metadata/language-structure-core.idmap \
../../refman-5.1/metadata/mysql-cluster-disk-data.idmap \
../../refman-5.1/metadata/mysql-cluster-replication.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-roadmap.idmap \
../../refman-5.1/metadata/mysql-cluster.idmap \
../../refman-5.1/metadata/news.idmap \
../../refman-5.1/metadata/optimization.idmap \
@@ -1286,8 +1284,7 @@
../../refman-5.1/metadata/stored-procedures.idmap \
../../refman-5.1/metadata/triggers.idmap \
../../refman-5.1/metadata/tutorial.idmap \
- ../../refman-5.1/metadata/views.idmap \
- ../../refman-6.0/metadata/mysql-cluster-cge.idmap
+ ../../refman-5.1/metadata/views.idmap
introduction.validpure: $(introduction_SOURCES)
introduction.titles: $(introduction_SOURCES)
introduction.useless: $(introduction_SOURCES)
@@ -1585,7 +1582,6 @@
language-structure-core.xml \
legalnotice.en.xml \
mysql-cluster-backup.xml \
- mysql-cluster-cge.xml \
mysql-cluster-configuration.xml \
mysql-cluster-disk-data.xml \
mysql-cluster-glossary.xml \
@@ -1778,7 +1774,6 @@
../../refman-5.1/metadata/introduction.idmap \
../../refman-5.1/metadata/language-structure-core.idmap \
../../refman-5.1/metadata/mysql-cluster-backup.idmap \
- ../../refman-5.1/metadata/mysql-cluster-cge.idmap \
../../refman-5.1/metadata/mysql-cluster-configuration.idmap \
../../refman-5.1/metadata/mysql-cluster-disk-data.idmap \
../../refman-5.1/metadata/mysql-cluster-glossary.idmap \
@@ -1832,8 +1827,7 @@
../../refman-5.1/metadata/tutorial.idmap \
../../refman-5.1/metadata/views.idmap \
../../refman-6.0/metadata/dba-core.idmap \
- ../../refman-6.0/metadata/manual.idmap \
- ../../refman-6.0/metadata/mysql-cluster-cge.idmap
+ ../../refman-6.0/metadata/manual.idmap
manual.validpure: $(manual_SOURCES)
manual.titles: $(manual_SOURCES)
manual.useless: $(manual_SOURCES)
@@ -1866,29 +1860,6 @@
mysql-cluster-backup-manprepped.xml: $(mysql_cluster_backup_SOURCES) $(mysql_cluster_backup_IDMAPS)
mysql-cluster-backup-remprepped.xml: $(mysql_cluster_backup_SOURCES) $(mysql_cluster_backup_IDMAPS)
-mysql_cluster_cge_INCLUDES = \
- ../common/fixedchars.ent \
- ../common/phrases.ent \
- ../refman-common/urls.ent \
- all-entities.ent \
- versions.ent
-mysql_cluster_cge_IMAGES =
-mysql_cluster_cge_SOURCES = mysql-cluster-cge.xml $(mysql_cluster_cge_INCLUDES)
-mysql_cluster_cge_IDMAPS = \
- ../../ndbapi/metadata/ndbapi.idmap \
- ../../refman-5.1/metadata/installing-core.idmap \
- ../../refman-5.1/metadata/mysql-cluster-news-core.idmap \
- ../../refman-5.1/metadata/news-5.1-core.idmap \
- ../../refman-6.0/metadata/mysql-cluster-cge.idmap
-mysql-cluster-cge.validpure: $(mysql_cluster_cge_SOURCES)
-mysql-cluster-cge.titles: $(mysql_cluster_cge_SOURCES)
-mysql-cluster-cge.useless: $(mysql_cluster_cge_SOURCES)
-mysql-cluster-cge.valid: $(mysql_cluster_cge_SOURCES) $(mysql_cluster_cge_IDMAPS)
-mysql-cluster-cge.validwarn: $(mysql_cluster_cge_SOURCES) $(mysql_cluster_cge_IDMAPS)
-mysql-cluster-cge-prepped.xml: $(mysql_cluster_cge_SOURCES) $(mysql_cluster_cge_IDMAPS)
-mysql-cluster-cge-manprepped.xml: $(mysql_cluster_cge_SOURCES) $(mysql_cluster_cge_IDMAPS)
-mysql-cluster-cge-remprepped.xml: $(mysql_cluster_cge_SOURCES) $(mysql_cluster_cge_IDMAPS)
-
mysql_cluster_configuration_INCLUDES = \
../common/fixedchars.ent \
../common/phrases.ent \
@@ -2058,8 +2029,8 @@
../../refman-5.1/metadata/mysql-cluster-multi-computer.idmap \
../../refman-5.1/metadata/mysql-cluster-process-management.idmap \
../../refman-5.1/metadata/mysql-cluster-security.idmap \
- ../../refman-5.1/metadata/mysql-cluster-utilities.idmap \
- ../../refman-5.1/metadata/programs-using.idmap
+ ../../refman-5.1/metadata/mysql-cluster-upgrade-downgrade.idmap \
+ ../../refman-5.1/metadata/mysql-cluster-utilities.idmap
mysql-cluster-multi-computer.validpure: $(mysql_cluster_multi_computer_SOURCES)
mysql-cluster-multi-computer.titles: $(mysql_cluster_multi_computer_SOURCES)
mysql-cluster-multi-computer.useless: $(mysql_cluster_multi_computer_SOURCES)
@@ -2283,6 +2254,7 @@
../refman-common/images/published/ndb-size-pl-1.png
mysql_cluster_utilities_SOURCES = mysql-cluster-utilities.xml $(mysql_cluster_utilities_INCLUDES)
mysql_cluster_utilities_IDMAPS = \
+ ../../ndbapi/metadata/ndb-internals.idmap \
../../ndbapi/metadata/ndbapi.idmap \
../../refman-5.1/metadata/installing-core.idmap \
../../refman-5.1/metadata/mysql-cluster-backup.idmap \
@@ -2327,7 +2299,6 @@
dynxml-local-mysql-cluster-news.xml \
dynxml-local-mysql-cluster-optvar.xml \
mysql-cluster-backup.xml \
- mysql-cluster-cge.xml \
mysql-cluster-configuration.xml \
mysql-cluster-disk-data.xml \
mysql-cluster-glossary.xml \
@@ -2378,7 +2349,6 @@
../../refman-5.1/metadata/installing-core.idmap \
../../refman-5.1/metadata/introduction.idmap \
../../refman-5.1/metadata/mysql-cluster-backup.idmap \
- ../../refman-5.1/metadata/mysql-cluster-cge.idmap \
../../refman-5.1/metadata/mysql-cluster-configuration.idmap \
../../refman-5.1/metadata/mysql-cluster-disk-data.idmap \
../../refman-5.1/metadata/mysql-cluster-glossary.idmap \
@@ -2395,6 +2365,7 @@
../../refman-5.1/metadata/mysql-cluster-security.idmap \
../../refman-5.1/metadata/mysql-cluster-upgrade-downgrade.idmap \
../../refman-5.1/metadata/mysql-cluster-utilities.idmap \
+ ../../refman-5.1/metadata/mysql-cluster.idmap \
../../refman-5.1/metadata/news-5.1-core.idmap \
../../refman-5.1/metadata/partitioning.idmap \
../../refman-5.1/metadata/programs-client-core.idmap \
@@ -2402,8 +2373,7 @@
../../refman-5.1/metadata/replication-configuration.idmap \
../../refman-5.1/metadata/replication-notes.idmap \
../../refman-5.1/metadata/replication.idmap \
- ../../refman-5.1/metadata/sql-syntax.idmap \
- ../../refman-6.0/metadata/mysql-cluster-cge.idmap
+ ../../refman-5.1/metadata/sql-syntax.idmap
mysql-cluster.validpure: $(mysql_cluster_SOURCES)
mysql-cluster.titles: $(mysql_cluster_SOURCES)
mysql-cluster.useless: $(mysql_cluster_SOURCES)
Modified: trunk/pt/refman-5.1/introduction.xml
===================================================================
--- trunk/pt/refman-5.1/introduction.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/pt/refman-5.1/introduction.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 7, Lines Added: 60, Lines Deleted: 116; 8563 bytes
@@ -497,25 +497,7 @@
</formalpara>
</listitem>
-<!--
<listitem>
- <para>
- <emphasis role="bold">The Instance Manager (IM)</emphasis>
- now has some additional functionality: <literal>SHOW
- <replaceable>instance_name</replaceable> LOG FILES</literal>
- provides a listing of all log files, <literal>SHOW
- <replaceable>instance_name</replaceable> LOG {ERROR | SLOW |
- GENERAL} <replaceable>size</replaceable></literal> retrieves
- a part of the specified log file, and <literal>SET
- <replaceable>instance_name</replaceable>.<replaceable>option_name</replaceable>=<replaceable>option_value</replaceable></literal>
- sets an option to the specified value and writes it to the
- configuration file. See <xref linkend="instance-manager"/>.
- (Author: Petr Chardin)
- </para>
- </listitem>
--->
-
- <listitem>
<formalpara>
<title>Upgrade program</title>
@@ -586,6 +568,22 @@
<listitem>
<formalpara>
+ <title>MySQL Cluster NDB 6.x</title>
+
+ <para>
+ Many new features and other improvements have been made to
+ the <literal>NDBCLUSTER</literal> storage engine in MySQL
+ Cluster NDB 6.x (formerly known as <quote>MySQL Cluster
+ Carrier Grade Edition</quote>); for an overview of these,
+ see <xref linkend="mysql-cluster-roadmap"/>.
+ </para>
+
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+
<title>Backup of tablespaces</title>
<para>
@@ -682,24 +680,34 @@
<listitem>
<para>
- Improvements in the <literal>INFORMATION_SCHEMA</literal>
- database, with new columns added to
- <literal>INFORMATION_SCHEMA.ROUTINES</literal>, and the
- addition of the
- <literal>INFORMATION_SCHEMA.PARAMETERS</literal> table.
+ Support for additional Unicode character sets:
+ <literal>utf16</literal>, <literal>utf32</literal>, and
+ 4-byte <literal>utf8</literal>. These character sets
+ support supplementary Unicode characters; that is,
+ characters outside the Basic Multilingual Plane (BMP).
</para>
</listitem>
-<!--
<listitem>
<para>
- A tool for online backup.
+ <literal>BACKUP DATABASE</literal> and
+ <literal>RESTORE</literal> statements for backup and
+ restore operations.
</para>
</listitem>
--->
<listitem>
<para>
+ Improvements in the <literal>INFORMATION_SCHEMA</literal>
+ database, with the addition of the
+ <literal>INFORMATION_SCHEMA.PARAMETERS</literal> table,
+ and new columns added to
+ <literal>INFORMATION_SCHEMA.ROUTINES</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Optimizer enhancements for faster subqueries and joins,
including batched index access of table rows for sequences
of disjoint ranges by the <literal>MyISAM</literal> and
@@ -717,16 +725,27 @@
<listitem>
<para>
- The <literal>LOCK TABLE</literal> statement no longer
- commits transactions automatically. Following
- <literal>LOCK TABLE</literal>, you can now access tables
- not mentioned in the <literal>LOCK TABLE</literal>
- statement. You can now also issue <literal>LOCK
- TABLE</literal> many times in succession, adding
- additional tables to the locked set, and without unlocking
- any tables that were locked previously; tables are not
- unlocked until the transaction is committed.
+ The syntax for the <literal>LOCK TABLES</literal>
+ statement is extended to support transactional table locks
+ that do not commit transactions automatically. Following
+ <literal>LOCK TABLES ... IN SHARE MODE</literal> or
+ <literal>LOCK TABLES ... IN EXCLUSIVE MODE</literal>, you
+ can access tables not mentioned in the <literal>LOCK
+ TABLES</literal> statement. You can now also issue these
+ extended <literal>LOCK TABLES</literal> statements many
+ times in succession, adding additional tables to the
+ locked set, and without unlocking any tables that were
+ locked previously. When using <literal>LOCK
+ TABLES</literal> with <literal>IN SHARE MODE</literal> or
+ <literal>IN EXCLUSIVE MODE</literal>, tables are not
+ unlocked until the transaction ends.
</para>
+
+ <para>
+ The behavior of <literal>LOCK TABLES</literal> when not
+ using <literal>IN SHARE MODE</literal> or <literal>IN
+ EXCLUSIVE MODE</literal> remains unchanged.
+ </para>
</listitem>
<listitem>
@@ -746,83 +765,6 @@
</itemizedlist>
</para>
- <para>
- Several improvements for MySQL Cluster, made in &mccge-series;,
- will become generally available for MySQL Cluster in MySQL 6.0:
-
- <itemizedlist>
-
- <listitem>
- <para>
- Replication conflict detection and resolution.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Online <literal>ADD COLUMN</literal>, <literal>ADD
- INDEX</literal>, and <literal>DROP INDEX</literal>
- operations.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Batch operations, resulting in significant speed
- improvements.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Replication heartbeats, which enable real-time detection
- of replication failures and real-time failover.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The ability to bind client applications and replication
- slaves to specific network interfaces.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Enhancements to take advantage of real-time scheduling and
- to bind processes to specific CPUs on data node hosts
- having multiple processors.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <literal>NDB</literal> API supports a new
- <literal>NdbRecord</literal> interface.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The ability to use multiple cluster connections in
- <command>mysqld</command> using the
- <option>--ndb-cluster-connection-pool</option> option.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Backup status reporting.
- </para>
- </listitem>
-
- </itemizedlist>
-
- See <xref linkend="mysql-cluster-cge-differences"/> for
- additional &mccge-series; features that are expected to be made
- available in MySQL 6.0.
- </para>
-
<!--
<itemizedlist>
<listitem>
@@ -854,9 +796,10 @@
-->
<para>
- The following constructs are deprecated and have been removed in
- MySQL 6.0. Where alternatives are shown, applications should be
- updated to use them.
+ The following constructs are deprecated and have been removed
+ for MySQL 6.0 (they were actually removed in 5.2.5). Where
+ alternatives are shown, applications should be updated to use
+ them.
<itemizedlist>
@@ -1707,7 +1650,8 @@
<listitem>
<para>
- <literal>LIKE</literal> is allowed on numeric values.
+ <function role="sqlop">LIKE</function> is allowed on
+ numeric values.
</para>
</listitem>
Modified: trunk/pt/refman-5.1/mysql-cluster-backup.xml
===================================================================
--- trunk/pt/refman-5.1/mysql-cluster-backup.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/pt/refman-5.1/mysql-cluster-backup.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 5, Lines Added: 4, Lines Deleted: 13; 1889 bytes
@@ -652,9 +652,7 @@
unspecified and is subject to change without
notice</emphasis>. (Bug #24363)
</para>
-
- &mccge-warning-begin;
-
+
<para>
<indexterm>
<primary>attribute promotion (MySQL Cluster)</primary>
@@ -812,8 +810,6 @@
columns to <literal>BINARY</literal>.
</para>
</note>
-
- &mccge-warning-end-cluster;
<para>
The <option>-b</option> option is used to specify the ID or
@@ -1109,8 +1105,7 @@
<row>
<entry><option>--skip-table-check</option></entry>
<entry><option>-s</option></entry>
- <entry>Do not check table schemas (Added in MySQL 5.1.17; <emphasis>not
- supported in &mccge-series;</emphasis>)</entry>
+ <entry>Do not check table schemas (Added in MySQL 5.1.17)</entry>
<entry><literal>FALSE</literal></entry>
</row>
<row>
@@ -1123,9 +1118,7 @@
</tgroup>
</informaltable>
- &mccge-warning-unsupported-begin;
-
- <para>
+ <para>
Beginning with MySQL 5.1.18, several additional options are
available for use with the <option>--print_data</option>
option in generating data dumps, either to
@@ -1238,9 +1231,7 @@
</itemizedlist>
</para>
- &mccge-warning-end-cluster;
-
- <indexterm>
+ <indexterm>
<primary>ndb_restore</primary>
<secondary>errors</secondary>
</indexterm>
Modified: trunk/pt/refman-5.1/mysql-cluster-configuration.xml
===================================================================
--- trunk/pt/refman-5.1/mysql-cluster-configuration.xml 2008-05-23 15:30:03 UTC (rev 10831)
+++ trunk/pt/refman-5.1/mysql-cluster-configuration.xml 2008-05-23 15:40:20 UTC (rev 10832)
Changed blocks: 43, Lines Added: 72, Lines Deleted: 156; 21250 bytes
@@ -81,31 +81,7 @@
<xref linkend="installing-source-tree"/>.
</para>
- &mccge-warning-begin;
-
- <warning>
- <para>
- <command>BUILD/compile-pentium-max</command> by default builds
- the MySQL Server with support for the <literal>InnoDB</literal>
- storage engine. <emphasis>You must not deploy or make use of
- &mccge-series; employing the <literal>InnoDB</literal> storage
- engine without prior written permission to do so from MySQL
- AB</emphasis>.
- </para>
-
- <para>
- If you wish to use <literal>InnoDB</literal> technology in
- conjunction with your use of &mccge-series; and do not already
- have authorization to do so as part of your MySQL Server
- license, contact your MySQL AB salesperson or other authorized
- MySQL AB representative for assistance in upgrading your MySQL
- Server license.
- </para>
- </warning>
-
- &mccge-warning-end-cluster;
-
- <para>
+ <para>
<command>BUILD/compile-pentium-max</command> also includes
OpenSSL, so you must either have or obtain OpenSSL to build
successfully, or else modify
@@ -1212,11 +1188,10 @@
</para>
<para>
- Beginning with MySQL 5.1.16
- (<emphasis>&mccge-series;</emphasis>: MySQL
- 5.1.15-ndb-6.1.3), it is possible to disable arbitration
- completely by setting <literal>ArbitrationRank</literal> to
- 0 on all management and SQL nodes.
+ Beginning with MySQL 5.1.16 and MySQL Cluster NDB 6.1.3, it
+ is possible to disable arbitration completely by setting
+ <literal>ArbitrationRank</literal> to 0 on all management
+ and SQL nodes.
</para>
</listitem>
@@ -1417,10 +1392,7 @@
</listitem>
<listitem>
-
- &mccge-warning-begin;
-
- <para id="mysql-cluster-param-ndbd-definition-tcpbind-inaddr-any">
+ <para id="mysql-cluster-param-ndbd-definition-tcpbind-inaddr-any">
<literal>TcpBind_INADDR_ANY</literal>
</para>
@@ -1433,13 +1405,10 @@
</para>
<para>
- This parameter was added in MySQL 5.1.16-ndb-6.2.0.
+ This parameter was added in MySQL Cluster NDB 6.2.0.
</para>
+ </listitem>
- &mccge-warning-end-cluster;
-
- </listitem>
-
<listitem>
<indexterm>
<primary>NoOfReplicas</primary>
@@ -1676,20 +1645,14 @@
4</literal> new pages are allocated, so the total number of
pages allocated to the table is now 22.
</para>
-
- &mccge-warning-begin;
-
+
<note>
<para>
The <quote>18.75% + 1</quote> overhead is no longer
- required in &mccge-series;
- 6.2.<replaceable>x</replaceable> and
- 6.3.<replaceable>x</replaceable> releases, beginning with
- MySQL 5.1.19-ndb-6.2.3 and MySQL 5.1.19-ndb-6.3.0.
+ required beginning with MySQL Cluster NDB 6.2.3 and MySQL
+ Cluster NDB 6.3.0.
</para>
</note>
-
- &mccge-warning-end-cluster;
<para>
Once a page has been allocated, it is currently not possible
@@ -2389,9 +2352,8 @@
</para>
<para>
- This parameter was introduced in MySQL 5.1.20, and in
- &mccge-series;, in MySQL 5.1.15-ndb-6.1.12 and MySQL
- 5.1.19-ndb-6.2.3.
+ This parameter was introduced in MySQL 5.1.20, MySQL Cluster NDB
+ 6.1.12 and MySQL MySQL Cluster NDB 6.2.3.
</para>
<formalpara>
@@ -2478,10 +2440,8 @@
<indexterm>
<primary>FragmentLogFileSize</primary>
</indexterm>
