| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | December 6 2006 12:43pm |
| Subject: | svn commit - mysqldoc@docsrva: r4121 - in trunk: refman-4.1 refman-5.0 refman-5.1 | ||
| View as plain text | |||
Author: jstephens Date: 2006-12-06 12:43:46 +0100 (Wed, 06 Dec 2006) New Revision: 4121 Log: Documenting Cluster bugfixes: Bug #18487, Bug #18647, Bug #19808, Bug #20065, Bug #21495, Bug #21519, Bug #22548, Bug #24039, Bug #24105, Bug #24301, Bug #24303, Bug #24470, Bug #24476, Bug #24543, Bug #24544, Bug #24655, Bug #24717, Bug #24752 Bug #20839 (Disk Data) Bug #24011 (Cluster APIs) Modified: trunk/refman-4.1/mysql-cluster.xml 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-4.1/mysql-cluster.xml =================================================================== --- trunk/refman-4.1/mysql-cluster.xml 2006-12-06 11:38:09 UTC (rev 4120) +++ trunk/refman-4.1/mysql-cluster.xml 2006-12-06 11:43:46 UTC (rev 4121) Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 1004 bytes @@ -12017,9 +12017,9 @@ <filename>BACKUP</filename> subdirectory of the <literal>DataDir</literal> on each data node. This can be overridden for one or more data nodes individually, or for all - cluster data nodes in the config.ini file using the - <literal>BackupDataDir</literal> configuration parameter as - discussed in + cluster data nodes in the <filename>config.ini</filename> file + using the <literal>BackupDataDir</literal> configuration + parameter as discussed in <link linkend="mysql-cluster-identifying-data-nodes">Identifying Data Nodes</link>. The backup files created for a backup with a given <replaceable>backup_id</replaceable> are stored in a Modified: trunk/refman-5.0/mysql-cluster.xml =================================================================== --- trunk/refman-5.0/mysql-cluster.xml 2006-12-06 11:38:09 UTC (rev 4120) +++ trunk/refman-5.0/mysql-cluster.xml 2006-12-06 11:43:46 UTC (rev 4121) Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 1004 bytes @@ -12079,9 +12079,9 @@ <filename>BACKUP</filename> subdirectory of the <literal>DataDir</literal> on each data node. This can be overridden for one or more data nodes individually, or for all - cluster data nodes in the config.ini file using the - <literal>BackupDataDir</literal> configuration parameter as - discussed in + cluster data nodes in the <filename>config.ini</filename> file + using the <literal>BackupDataDir</literal> configuration + parameter as discussed in <link linkend="mysql-cluster-identifying-data-nodes">Identifying Data Nodes</link>. The backup files created for a backup with a given <replaceable>backup_id</replaceable> are stored in a Modified: trunk/refman-5.0/releasenotes-es-5.0.xml =================================================================== --- trunk/refman-5.0/releasenotes-es-5.0.xml 2006-12-06 11:38:09 UTC (rev 4120) +++ trunk/refman-5.0/releasenotes-es-5.0.xml 2006-12-06 11:43:46 UTC (rev 4121) Changed blocks: 2, Lines Added: 28, Lines Deleted: 2; 1693 bytes @@ -45,7 +45,7 @@ </para> <itemizedlist> - + <listitem> <para> <literal>DROP TRIGGER</literal> now supports an <literal>IF @@ -63,10 +63,36 @@ <listitem> <para> + <literal>NDB Cluster</literal>: The failure of a data node + failure during a schema operation could lead to additional + node failures. (Bug #24752) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: A committed read could be + attempted before a data node had time to connect, causing a + timeout error. (Bug #24717) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal> (Cluster APIs): Some MGM API + function calls could yield incorrect return values in certain + cases where the cluster was operating under a very high load, + or experienced timeouts in inter-node communications. (Bug + #24011) + </para> + </listitem> + + <listitem> + <para> <literal>NDB Cluster</literal>: A unique constraint violation was not ignored by an <literal>UPDATE IGNORE</literal> statement when the constraint violation occurred on a - non-primary key. (Bug #18487) + non-primary key. (Bug #18487, Bug #24303) </para> </listitem> Modified: trunk/refman-5.1/mysql-cluster.xml =================================================================== --- trunk/refman-5.1/mysql-cluster.xml 2006-12-06 11:38:09 UTC (rev 4120) +++ trunk/refman-5.1/mysql-cluster.xml 2006-12-06 11:43:46 UTC (rev 4121) Changed blocks: 2, Lines Added: 10, Lines Deleted: 3; 1514 bytes @@ -12109,6 +12109,13 @@ received and processed the backup request. It does <emphasis>not</emphasis> mean that the backup has finished. </para> + + <para> + <emphasis role="bold">Note</emphasis>: Backup messages were + not recorded in the cluster log in MySQL 5.1.12 or 5.1.13. + The logging of backup operations was restored in MySQL + 5.1.14 (see Bug #24544). + </para> </listitem> <listitem> @@ -12126,9 +12133,9 @@ <filename>BACKUP</filename> subdirectory of the <literal>DataDir</literal> on each data node. This can be overridden for one or more data nodes individually, or for all - cluster data nodes in the config.ini file using the - <literal>BackupDataDir</literal> configuration parameter as - discussed in + cluster data nodes in the <filename>config.ini</filename> file + using the <literal>BackupDataDir</literal> configuration + parameter as discussed in <link linkend="mysql-cluster-identifying-data-nodes">Identifying Data Nodes</link>. The backup files created for a backup with a given <replaceable>backup_id</replaceable> are stored in a Modified: trunk/refman-5.1/news-5.1.xml =================================================================== --- trunk/refman-5.1/news-5.1.xml 2006-12-06 11:38:09 UTC (rev 4120) +++ trunk/refman-5.1/news-5.1.xml 2006-12-06 11:43:46 UTC (rev 4121) Changed blocks: 3, Lines Added: 172, Lines Deleted: 4; 7667 bytes @@ -82,6 +82,38 @@ </para> <itemizedlist> + + <listitem> + <para> + <literal>NDB Cluster</literal>: Backup messages are now + printed to the Cluster log. (Bug #24544) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: The error message + <errortext>Management server closed connection</errortext>, + when recorded in the MySQL error log, now includes a timestamp + indicating when the error took place. (Bug #21519) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal> (Disk Data): The output of + <command>mysqldump</command> now includes by default all + tablespace and logfile group definitions used by any tables or + databases that are dumped. (Bug #20839) + </para> + + <para> + <emphasis role="bold">Note</emphasis>: The working of the + <option>--all-tablespaces</option> or <option>-Y</option> + option for <command>mysqldump</command> remains unaffected by + this change. + </para> + </listitem> <listitem> <para> @@ -114,19 +146,148 @@ <listitem> <para> + <literal>NDB Cluster</literal>: The failure of a data node + failure during a schema operation could lead to additional + node failures. (Bug #24752) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: A committed read could be + attempted before a data node had time to connect, causing a + timeout error. (Bug #24717) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: The simultaneous shutdown of + <command>mysqld</command> and <command>ndbd</command> + processes caused unnecessary locking. (Bug #24655) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: The failure of the master node + in a node group during the allocation of node IDs could cause + <command>ndb_mgmd</command> to hang. (Bug #24543) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: In certain rare cases, a data + node could crash due to a typographical error in the MySQL + Cluster source code. (Bug #24476) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: Creating a new tables + containing a <literal>BLOB</literal> column when the server + was short of memory could cause the server to crash. (Bug + #24470) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: Any statement following the + execution of <literal>CREATE TABLE ... LIKE + <replaceable>ndb_table</replaceable></literal> (where + <replaceable>ndb_table</replaceable> was a table using the + <literal>NDB</literal> storage engine), would cause the + <command>mysql</command> client to hang. (Bug #24301) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: When the management client + command <literal>ALL RESTART -i</literal> was executed while + one data node was not running, all data nodes in the cluster + were shut down. (Bug #24105) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: A query using an index scan + followed by a delete operation, and then a rollback could + cause one or more data nodes to crash. (Bug #24039) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal> (Cluster APIs): Some MGM API + function calls could yield incorrect return values in certain + cases where the cluster was operating under a very high load, + or experienced timeouts in inter-node communications. (Bug + #24011) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: It was possible for the sum of + the <literal>MaxNoOfTables</literal>, + <literal>MaxNoOfOrderedIndexes</literal>, and + <literal>MaxNoOfUniqueHashIndexes</literal> configuration + parameters, plus the number of system tables to exceed the + maximum value for a <literal>Uint32</literal> number. In such + a case, the cluster's data nodes failed to start, and no + reason for this could easily be determined from the error + messages provided. (Bug #22548) + </para> + </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: Given a table + <literal>mytbl</literal> in a database <literal>mydb</literal> + on a MySQL Server acting as an SQL node in a MySQL Cluster, + then, following multiple <literal>ALTER TABLE mytbl + ENGINE=<replaceable>engine</replaceable></literal> + statements — first, to change the storage engine used + for a table to <literal>NDB</literal>, and then again to + change the table to use a non-<literal>NDB</literal> storage + engine — a <literal>DROP DATABASE mydb</literal> + statement executed on any SQL node in the cluster would cause + <literal>mydb</literal> to be dropped on + <emphasis>all</emphasis> SQL nodes in the cluster, even if + <literal>mydb</literal> contained non-<literal>NDB</literal> + tables. (Bug #21495) + </para> + </listitem> + + <listitem> + <para> <literal>NDB Cluster</literal>: An incorrect error message was - displayed in the event that the <literal>DataMemory</literal> - parameter value was was insufficient for the amount of data to - be stored by the cluster. (Bug #19808) + displayed in the event that the value of the + <literal>MaxNoOfOrderedIndexes</literal> parameter was set too + low. (Bug #20065) </para> </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: An incorrect error message was + displayed in the event that the value of the + <literal>DataMemory</literal> parameter was insufficient for + the amount of data to be stored by the cluster. (Bug #19808) + </para> + </listitem> <listitem> <para> <literal>NDB Cluster</literal>: A unique constraint violation was not ignored by an <literal>UPDATE IGNORE</literal> statement when the constraint violation occurred on a - non-primary key. (Bug #18487) + non-primary key. (Bug #18487, Bug #24303) </para> </listitem> @@ -1552,6 +1713,13 @@ be specified for processing binary log files. (Bug #18351) </para> </listitem> + + <listitem> + <para> + <literal>NDB Cluster</literal>: Backup messages are no longer + printed to the Cluster log. + </para> + </listitem> <listitem> <para>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r4121 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 6 Dec |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.612 sec. using MySQL 5.1.14-beta-log