| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | May 21 2007 6:20pm |
| Subject: | svn commit - mysqldoc@docsrva: r6553 - trunk/refman-5.1 | ||
| View as plain text | |||
Author: jstephens Date: 2007-05-21 18:20:49 +0200 (Mon, 21 May 2007) New Revision: 6553 Log: Sorted out errors in MCCGE changelogs: 5.1.15/6.1.7 5.1.15/6.1.8 5.1.16/6.2.0 5.1.18/6.2.1 5.1.18/6.2.2 Modified: trunk/refman-5.1/news-5.1.xml trunk/refman-5.1/renamed-nodes.txt Modified: trunk/refman-5.1/news-5.1.xml =================================================================== --- trunk/refman-5.1/news-5.1.xml 2007-05-21 10:46:43 UTC (rev 6552) +++ trunk/refman-5.1/news-5.1.xml 2007-05-21 16:20:49 UTC (rev 6553) Changed blocks: 10, Lines Added: 551, Lines Deleted: 295; 32183 bytes @@ -925,7 +925,7 @@ <literal>NDB Cluster</literal> (Replication): It was possible for API nodes to begin interacting with the cluster subscription manager before they were fully connected to the - cluster. (Bug #27651) + cluster. (Bug #27728) </para> </listitem> @@ -963,7 +963,7 @@ <literal>NDB Cluster</literal> (Disk Data): 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) + been committed. (Bug #) </para> </listitem> @@ -2424,7 +2424,314 @@ </listitem> </itemizedlist> - + + <section id="news-5-1-18-cge"> + + <title>Changes in MySQL 5.1.16 Carrier Grade Edition</title> + + <para> + This section contains change history information for + &mccge-series; releases based on MySQL 5.1.16. + </para> + + <section id="news-5-1-18-ndb-6-2-2"> + <title>Changes in release MySQL 5.1.18-ndb-6.2.2-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 &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.16-ndb-6.2.0"/>. + The file + <filename>mysqlcom-5.1.16-ndb-6.2.0-telco.tar.gz</filename> in + this directory contains the complete source archive. + </para> + + <para role="release-non-production"> + <emphasis role="bold">NOTE</emphasis>: Although MySQL has worked + very hard to ensure a high level of quality, protect your data by + making a backup as you would for any software beta release. Please + refer to our bug database at <ulink url="http://bugs.mysql.com/"/> + for more details about the individual bugs fixed in this version. + </para> + --> + + <para> + This Beta release incorporates all bugfixes and feature changes + made in MySQL 5.1.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> +<!-- + <important> + <formalpara> + + <title>Upgrading to MySQL 5.1.18-ndb-6.2.1 from a previous release</title> + + <para> + + </para> + + </formalpara> + + </important> +--> + +<!-- + <para> + Functionality added or changed: + </para> + + <itemizedlist> + <listitem> + <para></para> + </listitem> + </itemizedlist> +--> + + <para> + This release fixes the following bugs: + </para> + + <itemizedlist> + <listitem> + <para></para> + </listitem> + </itemizedlist> + </section> + + + <section id="news-5-1-18-ndb-6-2-1"> + + <title>Changes in release MySQL 5.1.18-ndb-6.2.1-beta (Released + 30 April 2007)</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> + + <warning> + <para> + This release was withdrawn after production and should no + longer be used. + </para> + </warning> + + <!-- + <para> + 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 + source code archive for this release from the MySQL FTP site at + <ulink url="ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.16-ndb-6.2.0"/>. + The file + <filename>mysqlcom-5.1.16-ndb-6.2.0-telco.tar.gz</filename> in + this directory contains the complete source archive. + </para> + + <para role="release-non-production"> + <emphasis role="bold">NOTE</emphasis>: Although MySQL has worked + very hard to ensure a high level of quality, protect your data by + making a backup as you would for any software beta release. Please + refer to our bug database at <ulink url="http://bugs.mysql.com/"/> + for more details about the individual bugs fixed in this version. + </para> + --> + + <para> + This Beta release incorporates all bugfixes and feature changes + made in MySQL 5.1.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> + + <important> + <formalpara> + + <title>Upgrading to MySQL 5.1.18-ndb-6.2.1 from a previous release</title> + + <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> + + </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></para> + </listitem> + + </itemizedlist> + --> + + <para> + This release fixes the following bugs: + </para> + + <itemizedlist> + + <listitem> + <para> + Multiple operations involving deletes followed by reads were + not handled correctly. (Bug #28276) + </para> + + <note> + <para> + This issue could also affect MySQL Cluster Replication. + </para> + </note> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster APIs</emphasis>: Using + <literal>NdbBlob::writeData()</literal> to write data in the + middle of an existing blob value (that is, updating the + value) could overwrite some data past the end of the data to + be changed. (Bug #27018) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster Replication</emphasis>: Trying + to replicate a large number of frequent updates with a + relatively small relay log + (<literal>max-relay-log-size</literal> set to 1M or less) + could cause the slave to crash. (Bug #27529) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster Replication</emphasis>: An SQL + node acting as a replication master server could be a single + point of failure; that is, if it failed, the replication + slave had no way of knowing this, which could result in a + mismatch of data between the master and the slave. (Bug + #21494) + </para> + </listitem> + + <listitem> + <para> + Memory usage of a <command>mysqld</command> process grew + even while idle. (Bug #27560) + </para> + </listitem> + + <listitem> + <para> + The Cluster table handler did not set bits in null bytes + correctly. (Bug #26591) + </para> + </listitem> + + <listitem> + <para> + When trying to create tables on an SQL node not connected to + the cluster, a misleading error message <errortext>Table + '<replaceable>tbl_name</replaceable>' already + exists</errortext> was generated. The error now generated is + <errortext>Could not connect to storage engine</errortext>. + (Bug #18676) + </para> + </listitem> + + <listitem> + <para> + Incorrect handling of fragmentation in a node takeover + during a restart could cause stale data to be copied to the + starting node, leading eventually to failure of the node. + (Bug #27434) + </para> + </listitem> + + <listitem> + <para> + Incorrect handling of fragmentation in a node takeover + during a restart could cause stale data to be copied to the + starting node, leading eventually to failure of the node. + (Bug #27434) + </para> + </listitem> + + <listitem> + <para> + After putting the cluster in single user mode from one MySQL + server, trying to drop an NDB table from a second MySQL + server also connected to the cluster would cause the second + MySQL server to hang. (Bug #27254) + </para> + </listitem> + + <listitem> + <para> + <command>mysqld</command> could crash shortly after a data + node failure following certain DML operations. (Bug #27169) + </para> + </listitem> + + <listitem> + <para> + An incorrect assertion was made when sending a + <literal>TCKEYFAILREF</literal> or + <literal>TCKEYCONF</literal> message to a failed data node. + (Bug #26814) + </para> + </listitem> + + </itemizedlist> + + </section> + </section> + + </section> <section id="news-5-1-17"> @@ -4580,7 +4887,7 @@ <listitem> <para> The <option>--with-readline</option> option for - <command>configure</command> does not work for commercial + <command>configure</command> did not work for commercial source packages, but no error message was printed to that effect. Now a message is printed. (Bug #25530) </para> @@ -4719,225 +5026,8 @@ &mccge-series; releases based on MySQL 5.1.16. </para> - <section id="news-5-1-16-ndb-6-2-1"> + - <title>Changes in release MySQL 5.1.16-ndb-6.2.1-beta (Not yet released)</title> - - <para role="release-level"> - This is a new Beta development release, fixing recently - discovered bugs and incorporating improvements made since the - previous &mccge-series; release. - </para> - -<!-- - <para> - 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 - source code archive for this release from the MySQL FTP site at - <ulink url="ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.16-ndb-6.2.0"/>. - The file - <filename>mysqlcom-5.1.16-ndb-6.2.0-telco.tar.gz</filename> in - this directory contains the complete source archive. - </para> - - <para role="release-non-production"> - <emphasis role="bold">NOTE</emphasis>: Although MySQL has worked - very hard to ensure a high level of quality, protect your data by - making a backup as you would for any software beta release. Please - refer to our bug database at <ulink url="http://bugs.mysql.com/"/> - for more details about the individual bugs fixed in this version. - </para> ---> - - <para> - This Beta release incorporates all bugfixes and feature changes - made in MySQL 5.1.16-ndb-6.2.0, which includes all bugfixes and - feature changes which were added in the mainline 5.1.16 release; - information about these can be found in - <xref linkend="news-5-1-16"/>. - </para> - - <important> - <formalpara> - - <title>Upgrading to MySQL 5.1.16-ndb-6.2.1 from a previous release</title> - - <para> - 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></para> - </listitem> - - </itemizedlist> ---> - - <para> - This release fixes the following bugs: - </para> - - <itemizedlist> - - <listitem> - <para> - Multiple operations involving deletes followed by reads were - not handled correctly. (Bug #28276) - </para> - - <note> - <para> - This issue could also affect MySQL Cluster Replication. - </para> - </note> - </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 APIs</emphasis>: Using - <literal>NdbBlob::writeData()</literal> to write data in the - middle of an existing blob value (that is, updating the - value) could overwrite some data past the end of the data to - be changed. (Bug #27018) - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Cluster Replication</emphasis>: Trying - to replicate a large number of frequent updates with a - relatively small relay log - (<literal>max-relay-log-size</literal> set to 1M or less) - could cause the slave to crash. (Bug #27529) - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Cluster Replication</emphasis>: An SQL - node acting as a replication master server could be a single - point of failure; that is, if it failed, the replication - slave had no way of knowing this, which could result in a - mismatch of data between the master and the slave. (Bug - #21494) - </para> - </listitem> - - <listitem> - <para> - Memory usage of a <command>mysqld</command> process grew - even while idle. (Bug #27560) - </para> - </listitem> - - <listitem> - <para> - The Cluster table handler did not set bits in null bytes - correctly. (Bug #26591) - </para> - </listitem> - - <listitem> - <para> - When trying to create tables on an SQL node not connected to - the cluster, a misleading error message <errortext>Table - '<replaceable>tbl_name</replaceable>' already - exists</errortext> was generated. The error now generated is - <errortext>Could not connect to storage engine</errortext>. - (Bug #18676) - </para> - </listitem> - - <listitem> - <para> - Incorrect handling of fragmentation in a node takeover - during a restart could cause stale data to be copied to the - starting node, leading eventually to failure of the node. - (Bug #27434) - </para> - </listitem> - - <listitem> - <para> - Incorrect handling of fragmentation in a node takeover - during a restart could cause stale data to be copied to the - starting node, leading eventually to failure of the node. - (Bug #27434) - </para> - </listitem> - - <listitem> - <para> - After putting the cluster in single user mode from one MySQL - server, trying to drop an NDB table from a second MySQL - server also connected to the cluster would cause the second - MySQL server to hang. (Bug #27254) - </para> - </listitem> - - <listitem> - <para> - <command>mysqld</command> could crash shortly after a data - node failure following certain DML operations. (Bug #27169) - </para> - </listitem> - - <listitem> - <para> - An incorrect assertion was made when sending a - <literal>TCKEYFAILREF</literal> or - <literal>TCKEYCONF</literal> message to a failed data node. - (Bug #26814) - </para> - </listitem> - - </itemizedlist> - - </section> - <section id="news-5-1-16-ndb-6-2-0"> <title>Changes in release MySQL 5.1.16-ndb-6.2.0-beta (03 March 2007)</title> @@ -6601,10 +6691,118 @@ 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-8"> + <title>Changes in release MySQL 5.1.15-ndb-6.1.7-beta (Released 05 + May 2007)</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, 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> +<!-- + <important> + <formalpara> + + <title>Upgrading to MySQL 5.1.15-ndb-6.1.8 from a previous release</title> + + <para> + + </para> + + </formalpara> + </important> +--> + + + <para> + Functionality added or changed: + </para> + + <itemizedlist> + <listitem> + <para></para> + </listitem> + </itemizedlist> + + + <para> + This release fixes the following bugs: + </para> + + <itemizedlist> + + <listitem> + <para> + <emphasis role="bold">Disk Data</emphasis>: Extremely large + inserts into Disk Data tables could lead to data node + failure in some circumstances. (Bug #27942) + </para> + </listitem> + + <listitem> + <para> + Repeated insertion of data generated by + <command>mysqldump</command> into <literal>NDB</literal> + tables could eventually lead to failure of the cluster. (Bug + #27437) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster APIs</emphasis>: In a + multi-operation transaction, a delete operation followed by + the insertion of an implicit <literal>NULL</literal> failed + to overwrite an existing value. (Bug #20535) + </para> + </listitem> + </itemizedlist> + + + </section> + + <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> + <title>Changes in release MySQL 5.1.15-ndb-6.1.7-beta (Released 05 + May 2007)</title> <para role="release-level"> This is a new Beta development release, fixing recently @@ -6710,23 +6908,128 @@ </para> <itemizedlist> - + <listitem> <para> - <emphasis role="bold">Disk Data</emphasis>: Extremely large - inserts into Disk Data tables could lead to data node - failure in some circumstances. (Bug #27942) + 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> - <emphasis role="bold">Cluster APIs</emphasis>: In a - multi-operation transaction, a delete operation followed by - the insertion of an implicit <literal>NULL</literal> failed - to overwrite an existing value. (Bug #20535) + Memory usage of a <command>mysqld</command> process grew + even while idle. (Bug #27560) </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>: Under + very high loads, checkpoints could be read or written with + checkpoint indexes out of order. (Bug #27651) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster Replication</emphasis>: It was + possible for API nodes to begin interacting with the cluster + subscription manager before they were fully connected to the + cluster. (Bug #27728) + </para> + </listitem> + + <listitem> + <para> + Some queries that updated multiple tables were not backed up + or replicated correctly. (Bug #27748) + </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> + Under some circumstances, a node restart could fail to + update the Global Checkpoint Index (GCI). (Bug #28023) + </para> + </listitem> + + <listitem> + <para> + Under certain rare circumstances, <command>ndbd</command> + could get caught in an infinite loop when one transaction took + a read lock and then a second transaction attempted to obtain + a write lock on the same tuple in the lock queue. (Bug #28073) + </para> + </listitem> + + <listitem> + <para> + The cluster waited 30 seconds instead of 30 milliseconds + before reading table statistics. (Bug #28093) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Disk Data</emphasis>: Changing a + column specification or issuing a + <literal>TRUNCATE</literal> statement on a Disk Data table + caused the table to become an in-memory table. (Bug #24667) + </para> + </listitem> + + <listitem> + <para> + Performing a delete followed by an insert during a local + checkpoint could cause a <errortext>Rowid already + allocated</errortext> error. (Bug #27205) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">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> @@ -6736,6 +7039,22 @@ node failure. (Bug #28161) </para> </listitem> + + <listitem> + <para> + <command>mysqldump</command> could not dump log tables. (Bug + #26121) + </para> + </listitem> + + <listitem> + <para> + The <option>--with-readline</option> option for + <command>configure</command> did not work for commercial + source packages, but no error message was printed to that + effect. Now a message is printed. (Bug #25530) + </para> + </listitem> </itemizedlist> @@ -6863,53 +7182,6 @@ <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> @@ -6930,22 +7202,6 @@ <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 Modified: trunk/refman-5.1/renamed-nodes.txt =================================================================== --- trunk/refman-5.1/renamed-nodes.txt 2007-05-21 10:46:43 UTC (rev 6552) +++ trunk/refman-5.1/renamed-nodes.txt 2007-05-21 16:20:49 UTC (rev 6553) Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 651 bytes @@ -383,4 +383,5 @@ thread-packages http://dev.mysql.com/doc/internals/en/thread-packages tips miscellaneous-optimization-tips faqs-stored-routines-triggers-replication faqs-stored-procs -mysql-cluster-limitations-resolved-in-5-1 mysql-cluster-limitations-resolved +mysql-cluster-limitations-resolved-in-5-1 mysql-cluster-limitations-resolved +news-5-1-16-ndb-6-2-1 news-5-1-18-ndb-6-2-1
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r6553 - trunk/refman-5.1 | jon | 21 May |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.891 sec. using MySQL 5.1.14-beta-log