| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | June 19 2007 2:43pm |
| Subject: | svn commit - mysqldoc@docsrva: r6862 - in trunk: refman-5.0 refman-5.1 | ||
| View as plain text | |||
Author: jstephens Date: 2007-06-19 14:43:39 +0200 (Tue, 19 Jun 2007) New Revision: 6862 Log: Documented Cluster bugfixes: Bug #24793, Bug #26342, Bug #27640, Bug #28717, Bug #28949, Bug #28989, Bug #29063, Bug #29073, Bug #29074, Bug #29103 Modified: trunk/refman-5.0/mysql-cluster.xml trunk/refman-5.0/releasenotes-es-5.0.xml trunk/refman-5.1/mysql-cluster.xml trunk/refman-5.1/news-5.1.xml Modified: trunk/refman-5.0/mysql-cluster.xml =================================================================== --- trunk/refman-5.0/mysql-cluster.xml 2007-06-19 12:42:18 UTC (rev 6861) +++ trunk/refman-5.0/mysql-cluster.xml 2007-06-19 12:43:39 UTC (rev 6862) Changed blocks: 2, Lines Added: 16, Lines Deleted: 15; 1469 bytes @@ -17598,21 +17598,6 @@ </formalpara> </listitem> - <listitem> - <formalpara> - - <title><literal>auto_increment_increment</literal> and - <literal>auto_increment_offset</literal></title> - - <para> - The <literal>auto_increment_increment</literal> and - <literal>auto_increment_offset</literal> server system - variables are not supported for Cluster replication. - </para> - - </formalpara> - </listitem> - </itemizedlist> </para> @@ -18900,6 +18885,22 @@ </para> </listitem> + <listitem> + <formalpara> + + <title><literal>auto_increment_increment</literal> and + <literal>auto_increment_offset</literal></title> + + <para> + The <literal>auto_increment_increment</literal> and + <literal>auto_increment_offset</literal> server system + variables are supported for <literal>NDBCLUSTER</literal> + tables beginning with MySQL 5.0.46. + </para> + + </formalpara> + </listitem> + </itemizedlist> </section> Modified: trunk/refman-5.0/releasenotes-es-5.0.xml =================================================================== --- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-06-19 12:42:18 UTC (rev 6861) +++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-06-19 12:43:39 UTC (rev 6862) Changed blocks: 3, Lines Added: 85, Lines Deleted: 0; 3602 bytes @@ -31,6 +31,70 @@ <filename>refman-common</filename> directory. </remark> + <section id="releasenotes-es-5-0-46"> + + <title>Changes in release 5.0.46 (Not yet released)</title> + + <para role="release-level"> + This is a bugfix release for the current production release + family. + </para> + + <para> + This section documents all changes and bugfixes that have been + applied since the last official MySQL release. If you would like + to receive more fine-grained and personalized <emphasis>update + alerts</emphasis> about fixes that are relevant to the version and + features you use, please consider subscribing to <emphasis>MySQL + Network</emphasis> (a commercial MySQL offering). For more details + please see + <ulink url="http://www.mysql.com/network/advisors.html"/>. + </para> + + <para> + This section documents all changes and bug fixes that have been + applied since the last MySQL Enterprise Server release (5.0.44). + </para> + + <para> + Functionality added or changed: + </para> + + <itemizedlist> + + <listitem> + <para> + <literal>NDB Cluster</literal>: + <literal>auto_increment_increment</literal> and + <literal>auto_increment_offset</literal> are now supported for + <literal>NDB</literal> tables. (Bug #26342) + </para> + </listitem> + + </itemizedlist> + + <para> + Bugs fixed: + </para> + + <remark role="note"> + Leave any security or incompatible fixes first in the list. + </remark> + + <itemizedlist> + + <listitem> + <para> + <literal>NDB Cluster</literal>: The management client's + response to <literal>START BACKUP WAIT COMPLETED</literal> did + not include the backup ID. (Bug #27640) + </para> + </listitem> + + </itemizedlist> + + </section> + <section id="releasenotes-es-5-0-44"> <title>Changes in MySQL Enterprise 5.0.44 (Not yet released)</title> @@ -108,6 +172,15 @@ <listitem> <para> + <literal>NDB Cluster</literal>: A race condition could result + when non-master nodes (in addition to the master node) tried + to update active status due to a local checkpoint. Now only + the master updates the active status. (Bug #28717) + </para> + </listitem> + + <listitem> + <para> <literal>NDB Cluster</literal>: The actual value of <literal>MaxNoOfOpenFiles</literal> as used by the cluster was offset by 1 from the value set in @@ -1803,6 +1876,18 @@ <listitem> <para> + <literal>NDB Cluster</literal>: When a cluster node suffered a + <quote>hard</quote> failure (such as a power failure or loss + of a network connection) TCP sockets to the + <quote>vanished</quote> node were maintained indefinitely. Now + socket-based transporters check for a response and terminate + the socket if there is no activity on the socket after 2 + hours. (Bug #24793) + </para> + </listitem> + + <listitem> + <para> <literal>NDB Cluster</literal>: <literal>NDB</literal> tables having <literal>MEDIUMINT AUTO_INCREMENT</literal> columns were not restored correctly by <command>ndb_restore</command>, Modified: trunk/refman-5.1/mysql-cluster.xml =================================================================== --- trunk/refman-5.1/mysql-cluster.xml 2007-06-19 12:42:18 UTC (rev 6861) +++ trunk/refman-5.1/mysql-cluster.xml 2007-06-19 12:43:39 UTC (rev 6862) Changed blocks: 2, Lines Added: 16, Lines Deleted: 15; 1577 bytes @@ -21989,21 +21989,6 @@ </formalpara> </listitem> - <listitem> - <formalpara> - - <title><literal>auto_increment_increment</literal> and - <literal>auto_increment_offset</literal></title> - - <para> - The <literal>auto_increment_increment</literal> and - <literal>auto_increment_offset</literal> server system - variables are not supported for Cluster replication. - </para> - - </formalpara> - </listitem> - </itemizedlist> </para> @@ -23241,6 +23226,22 @@ </listitem> <listitem> + <formalpara> + + <title><literal>auto_increment_increment</literal> and + <literal>auto_increment_offset</literal></title> + + <para> + The <literal>auto_increment_increment</literal> and + <literal>auto_increment_offset</literal> server system + variables are supported for Cluster replication + beginning with MySQL 5.1.20. + </para> + + </formalpara> + </listitem> + + <listitem> <indexterm> <primary>MySQL Cluster limitations</primary> <secondary>autodiscovery</secondary> Modified: trunk/refman-5.1/news-5.1.xml =================================================================== --- trunk/refman-5.1/news-5.1.xml 2007-06-19 12:42:18 UTC (rev 6861) +++ trunk/refman-5.1/news-5.1.xml 2007-06-19 12:43:39 UTC (rev 6862) Changed blocks: 3, Lines Added: 87, Lines Deleted: 0; 3901 bytes @@ -117,6 +117,30 @@ <listitem> <para> + <literal>NDB Cluster</literal>: + <literal>auto_increment_increment</literal> and + <literal>auto_increment_offset</literal> are now supported for + <literal>NDB</literal> tables. (Bug #26342) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: The cluster management client + now stores command history between sessions. (Bug #29073) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: + <command>ndb_error_reporter</command> now preserves timestamps + on files. (Bug #29074) + </para> + </listitem> + + <listitem> + <para> <literal>NDB Cluster</literal>: The <literal>TimeBetweenWatchdogCheckInitial</literal> configuration parameter was added to allow setting of a @@ -176,6 +200,57 @@ <listitem> <para> + <literal>NDB Cluster</literal>: Attempting to restore a + <literal>NULL</literal> row to a <literal>VARBINARY</literal> + column caused <command>ndb_restore</command> to fail. (Bug + #29103) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: <command>ndb_mgm</command> + could hang when connecting to a nonexistent host. (Bug #28847) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal> (APIs): The timeout set using + the MGM API <literal>ndb_mgm_set_timeout()</literal> function + was incorrectly interpreted as seconds rather than as + milliseconds. (Bug #29063) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: When shutting down + <command>mysqld</command>, the <literal>NDB</literal> binlog + process was not shut down before log cleanup began. (Bug + #28949) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: A race condition could result + when non-master nodes (in addition to the master node) tried + to update active status due to a local checkpoint. Now only + the master updates the active status. (Bug #28717) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: The management client's + response to <literal>START BACKUP WAIT COMPLETED</literal> did + not include the backup ID. (Bug #27640) + </para> + </listitem> + + <listitem> + <para> <literal>NDB Cluster</literal>: A regression in the heartbeat monitoring code could lead to node failure under high load. This issue affected MySQL 5.1.19 only. (Bug #28783) @@ -2152,6 +2227,18 @@ <listitem> <para> + <literal>NDB Cluster</literal>: When a cluster node suffered a + <quote>hard</quote> failure (such as a power failure or loss + of a network connection) TCP sockets to the + <quote>vanished</quote> node were maintained indefinitely. Now + socket-based transporters check for a response and terminate + the socket if there is no activity on the socket after 2 + hours. (Bug #24793) + </para> + </listitem> + + <listitem> + <para> <literal>NDB Cluster</literal>: Under certain rare circumstances, <command>ndbd</command> could get caught in an infinite loop when one transaction took a read lock and then a
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r6862 - in trunk: refman-5.0 refman-5.1 | jon | 19 Jun |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.439 sec. using MySQL 5.1.14-beta-log