| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | May 5 2007 8:28am |
| Subject: | svn commit - mysqldoc@docsrva: r6344 - trunk/refman-5.1 | ||
| View as plain text | |||
Author: jstephens Date: 2007-05-05 08:28:29 +0200 (Sat, 05 May 2007) New Revision: 6344 Log: Documenting "fix" for Cluster Bug #28205... Modified: trunk/refman-5.1/mysql-cluster.xml trunk/refman-5.1/news-5.1.xml Modified: trunk/refman-5.1/mysql-cluster.xml =================================================================== --- trunk/refman-5.1/mysql-cluster.xml 2007-05-04 23:01:03 UTC (rev 6343) +++ trunk/refman-5.1/mysql-cluster.xml 2007-05-05 06:28:29 UTC (rev 6344) Changed blocks: 1, Lines Added: 99, Lines Deleted: 0; 3961 bytes @@ -9201,6 +9201,105 @@ <xref linkend="mysql-cluster-replication-schema"/>. </para> </listitem> + + <listitem> + <para id="mysql-cluster-upgrade-downgrade-compatibility-online-add-drop-column"> + The internal specifications for columns in + <literal>NDB</literal> tables changed in MySQL 5.1.18 to + allow compatibility with future MySQL Cluster releases that + are expected to implement online adding and dropping of + columns. This change is not backwards compatible with earlier + MySQL versions. + </para> + + <para> + In order to make tables created in MySQL 5.1.17 and earlier + compatible with online adding and dropping of columns when + this features becomes available, it is necessary force MySQL + 5.1.18 and later to convert the tables to the new format by + following this procedure: + + <orderedlist> + <listitem> + <para> + Upgrade the MySQL Cluster software on all data, + management, and SQL nodes + </para> + </listitem> + + <listitem> + <para> + Back up all <literal>NDB</literal> tables + </para> + </listitem> + + <listitem> + <para> + Shut down the cluster (all data, management, and SQL + nodes) + </para> + </listitem> + + <listitem> + <para> + Restart the cluster, starting all data nodes with the + <option>--initial</option> option (to clear and rebuild + the data node filesystems) + </para> + </listitem> + + <listitem> + <para> + Restore the tables from backup + </para> + </listitem> + </orderedlist> + </para> + + <para> + This is not necessary for <literal>NDB</literal> tables + created in MySQL 5.1.18 and later; such tables will + automatically be compatible with online adding and dropping of + columns when this feature is introduced. + </para> + + <para> + 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 + follows: + + <itemizedlist> + <listitem> + <formalpara> + <title>ndb-6.1.x series</title> + + <para> + The new table format is implemented beginning with + MySQL 5.1.15-ndb-6.1.7. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>ndb-6.2.x series</title> + + <para> + The new table format is implemented beginning with + MySQL 5.1.16-ndb-6.2.1. + </para> + </formalpara> + </listitem> + </itemizedlist> + + </para> + </listitem> </itemizedlist> Modified: trunk/refman-5.1/news-5.1.xml =================================================================== --- trunk/refman-5.1/news-5.1.xml 2007-05-04 23:01:03 UTC (rev 6343) +++ trunk/refman-5.1/news-5.1.xml 2007-05-05 06:28:29 UTC (rev 6344) Changed blocks: 7, Lines Added: 342, Lines Deleted: 46; 15777 bytes @@ -216,6 +216,30 @@ integer types. (Bug #27047) </para> </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: The internal specifications + for columns in <literal>NDB</literal> tables has changed to + allow compatibility with future MySQL Cluster releases that + are expected to implement online adding and dropping of + columns. This change is not backwards compatible with earlier + MySQL versions. + </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.18 or later from MySQL 5.1.17 or earlier. + </para> + + <para> + See also Bug #28205. + </para> + </listitem> </itemizedlist> @@ -4047,7 +4071,7 @@ <!-- <para> - Like all releases for MySQL &mccge-series;, this is a + Like all releases for &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 @@ -4075,55 +4099,38 @@ <xref linkend="news-5-1-16"/>. </para> -<!-- + <important> <formalpara> <title>Upgrading to MySQL 5.1.16-ndb-6.2.1 from a previous release</title> + <para> + 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> + </formalpara> + + <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> - <para> - This release is not binary compatible with releases previous - to MySQL 5.1.15-ndb-6.1.2. This means that: - - <itemizedlist> - - <listitem> - <para> - You cannot perform an online upgrade to this release - from MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, or - any of the mainline MySQL 5.1 releases. When upgrading - from one of these versions, you must shut down the - cluster, replace all binaries, then restart the cluster. - </para> - - <para> - However, you <emphasis>can</emphasis> perform an online - upgrade of a Cluster running MySQL 5.1.15-ndb-6.1.2 to - MySQL 5.1.15-ndb-6.1.3, using the rolling upgrade - procedure described in - <xref linkend="mysql-cluster-rolling-restart"/>. You - should replace all binaries for all data nodes, - management nodes, and SQL nodes as part of this process. - When upgrading the data nodes, you will need to restart - each data node with the <option>&ddash;initial</option> option. - </para> - </listitem> - - <listitem> - <para> - You must recompile all NDB API and MGM API applications - used with a previous version of MySQL Cluster, including - those compiled against MySQL 5.1.15-ndb-6.1.2. - </para> - </listitem> - - </itemizedlist> + See also Bug #28205. </para> - </formalpara> </important> ---> + <!-- <para> Functionality added or changed: @@ -4132,8 +4139,7 @@ <itemizedlist> <listitem> - <para> - </para> + <para></para> </listitem> </itemizedlist> @@ -5921,10 +5927,300 @@ This section contains change history information for &mccge-series; releases based on MySQL 5.1.15. </para> + + <section id="news-5-1-15-ndb-6-1-7"> + + <title>Changes in release MySQL 5.1.15-ndb-6.1.7-beta (Not yet released)</title> + + <para role="release-level"> + This is a new Beta development release, fixing recently + discovered bugs and incorporating improvements made since the + previous &mccge-series; release. + </para> + +<!-- + <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="ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.15-ndb-6.1.5/"/>. + The file + <filename>mysqlcom-5.1.15-ndb-6.1.5-telco.tar.gz</filename> in + this directory contains the complete source archive. + </para> +--> + + <para role="release-non-production"> + <emphasis role="bold">NOTE</emphasis>: Although MySQL has worked + very hard to ensure a high level of quality, protect your data + by making a backup as you would for any software beta release. + Please refer to our bug database at + <ulink url="http://bugs.mysql.com/"/> for more details about the + individual bugs fixed in this version. + </para> + + <para> + This Beta release incorporates all bugfixes and feature changes + made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL + 5.1.15-ndb-6.1.2, MySQL 5.1.15-ndb-6.1.3, MySQL + 5.1.15-ndb-6.1.4, 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> + + + <important> + <formalpara> + <title>Upgrading to MySQL 5.1.15-ndb-6.1.7 from a previous release</title> + + <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> + </formalpara> + + <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> + + <para> + See also Bug #28205. + </para> + </important> + + + + <para> + Functionality added or changed: + </para> + + <itemizedlist> + + <listitem> + <para> + <emphasis role="bold">Incompatible change</emphasis>: The + schema for the <literal>ndb_apply_status</literal> table in + the <literal>mysql</literal> system database has changed. When + upgrading to this release from a previous &mccge-series; or + mainline MySQL 5.1 release, you must drop the + <literal>mysql.ndb_apply_status</literal> table, then restart + the server in order for the table to be re-created with the + new schema. + </para> + + <para> + See <xref linkend="mysql-cluster-replication-schema"/>, for + additional information. + </para> + </listitem> + + </itemizedlist> + + + <para> + This release fixes the following bugs: + </para> + + <itemizedlist> + + <listitem> + <para> + <emphasis role="bold">Cluster Replication</emphasis>: It was + possible for API nodes to begin interacting with the cluster + subscription manager before they were fully connected to the + cluster. (Bug #27651) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster Replication</emphasis>: Under + very high loads, checkpoints could be read or written with + checkpoint indexes out of order. (Bug #27651) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Disk Data</emphasis>: When restarting + a data node following the creation of a large number (~200) + of Disk Data objects, the cluster could not assign a node ID + to the restarting node. (Bug #25741) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Disk Data</emphasis>: Changes to a + Disk Data table made as part of a transaction could not be + seen by the client performing the changes until the + transaction had been committed. (Bug #27757) + </para> + </listitem> + + <listitem> + <para> + An <literal>INSERT</literal> followed a delete + <literal>DELETE</literal> on the same <literal>NDB</literal> + table caused a memory leak. (Bug #27756) + </para> + + <para> + (This bug was introduced by the fix for Bug #20612.) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster APIs</emphasis>: An issue with + the way in which the + <literal>NdbDictionary::Dictionary::listEvents()</literal> + method freed resources could sometimes lead to memory + corruption. (Bug #27663) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster Replication</emphasis>: Trying + to replicate a large number of frequent updates with a + relatively small relay log + (<literal>max-relay-log-size</literal> set to 1M or less) + could cause the slave to crash. (Bug #27529) + </para> + </listitem> + + <listitem> + <para> + Under certain rare circumstances, <literal>DROP + TABLE</literal> or <literal>TRUNCATE</literal> of an + <literal>NDB</literal> table could cause a node failure or + forced cluster shutdown. (Bug #27581) + </para> + </listitem> + + <listitem> + <para> + Memory usage of a <command>mysqld</command> process grew + even while idle. (Bug #27560) + </para> + </listitem> + + <listitem> + <para> + A data node failing while another data node was restarting + could leave the cluster in an inconsistent state. In certain + rare cases, this could lead to a race condition and the + eventual forced shutdown of the cluster. (Bug #27466) + </para> + </listitem> + + <listitem> + <para> + A data node failing while another data node was restarting + could leave the cluster in an inconsistent state. In certain + rare cases, this could lead to a race condition and the + eventual forced shutdown of the cluster. (Bug #27466) + </para> + </listitem> + + <listitem> + <para> + <command>mysqld</command> could crash shortly after a data + node failure following certain DML operations. (Bug #27169) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Disk Data</emphasis>: <literal>DROP + INDEX</literal> on a Disk Data table did not always move + data from memory into the tablespace. (Bug #25877) + </para> + </listitem> + + <listitem> + <para> + It was not possible to set + <literal>LockPagesInMainMemory</literal> equal to + <literal>0</literal>. (Bug #27291) + </para> + </listitem> + + <listitem> + <para> + A race condition could sometimes occur if the node acting as + master failed while node IDs were still being allocated + during startup. (Bug #27286) + </para> + </listitem> + + <listitem> + <para> + When a data node was taking over as the master node, a race + condition could sometimes occur as the node was assuming + responsibility for handling of global checkpoints. (Bug + #27283) + </para> + </listitem> + + <listitem> + <para> + A delete operation using a scan following by an insert using + a scan could cause a data node to fail. (Bug #27203) + </para> + </listitem> + + <listitem> + <para> + The same failed request from an API node could be handled by + the cluster multiple times, resulting in reduced + performance. (Bug #27087) + </para> + </listitem> + + <listitem> + <para> + <command>mysqld</command> processes would sometimes crash + under high load. (Bug #26825) + </para> + + <para> + This improves on and replaces the fix for this bug that was + made in MySQL 5.1.15-ndb-6.1.5. + </para> + </listitem> + + <listitem> + <para> + The failure of a data node while restarting could cause + other data nodes to hang or crash. (Bug #27003) + </para> + </listitem> + + </itemizedlist> + + </section> + + <section id="news-5-1-15-ndb-6-1-6"> - <title>Changes in release MySQL 5.1.15-ndb-6.1.6-beta (Not yet released)</title> + <title>Changes in release MySQL 5.1.15-ndb-6.1.6-beta (Not released)</title> <para role="release-level"> This is a new Beta development release, fixing recently @@ -6010,7 +6306,7 @@ </important> --> -<!-- + <para> Functionality added or changed: </para> @@ -6036,8 +6332,8 @@ </listitem> </itemizedlist> ---> + <para> This release fixes the following bugs: </para>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r6344 - trunk/refman-5.1 | jon | 5 May |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.681 sec. using MySQL 5.1.14-beta-log