From: jon Date: October 23 2007 4:52pm Subject: svn commit - mysqldoc@docsrva: r8267 - trunk/dynamic-docs/changelog List-Archive: http://lists.mysql.com/commits/36170 Message-Id: <200710231652.l9NGqOVl005341@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: jstephens Date: 2007-10-23 18:52:23 +0200 (Tue, 23 Oct 2007) New Revision: 8267 Log: Re-fixing Cluster changelog entry fixups (Thanks, MC!) Modified: trunk/dynamic-docs/changelog/mysqld.xml Modified: trunk/dynamic-docs/changelog/mysqld.xml =================================================================== --- trunk/dynamic-docs/changelog/mysqld.xml 2007-10-23 16:50:13 UTC (rev 8266) +++ trunk/dynamic-docs/changelog/mysqld.xml 2007-10-23 16:52:23 UTC (rev 8267) Changed blocks: 58, Lines Added: 214, Lines Deleted: 336; 26066 bytes @@ -64,7 +64,7 @@ - + @@ -12282,6 +12282,7 @@ + @@ -12294,16 +12295,11 @@ - + + mysqld processes did not reconnect to the + cluster following a restart of ndb_mgmd. + - MySQL Cluster - - mysqld processes did not reconnect to the - cluster following a restart of ndb_mgmd. - - - - @@ -12346,6 +12342,7 @@ + @@ -12358,16 +12355,11 @@ - + + A DELETE performed as part of a transaction + caused an erroneous result. + - MySQL Cluster - - A DELETE performed as part of a transaction - caused an erroneous result. - - - - @@ -14904,6 +14896,7 @@ + @@ -14916,16 +14909,11 @@ - + + Setting TransactionInactiveTimeout = 0 did + not result in an infinite timeout. + - MySQL Cluster - - Setting TransactionInactiveTimeout = 0 did - not result in an infinite timeout. - - - - @@ -16935,6 +16923,7 @@ + @@ -16947,15 +16936,10 @@ - + + Data nodes failed to restart on 64-bit Solaris. + - MySQL Cluster - - Data nodes failed to restart on 64-bit Solaris - - - - @@ -26483,6 +26467,7 @@ + @@ -26496,17 +26481,12 @@ - + + When trying to open a table that could not be discovered or + unpacked, the cluster returned error codes which the MySQL + server falsely interpreted as operating system errors. + - MySQL Cluster - - When trying to open a table that could not be discovered or - unpacked, the cluster would return error codes which the MySQL - server falsely interpreted as operating system errors. - - - - @@ -26574,6 +26554,7 @@ + @@ -26582,19 +26563,14 @@ - + + Methods were added to the + Ndb_cluster_connection class to faciliate + iterating over existing Ndb objects. See + , + for more information. + - Cluster APIs - - New methods have been added to the - Ndb_cluster_connection class to faciliate - iterating over existing Ndb objects. See - , - for more information. - - - - @@ -37129,6 +37105,7 @@ + @@ -37142,16 +37119,11 @@ - + + A BIT column whose offset and length totaled + 32 caused the cluster to crash. + - MySQL Cluster - - A BIT column whose offset and length - totaled 32 caused the cluster to crash. - - - - @@ -45640,6 +45612,7 @@ + @@ -45654,18 +45627,13 @@ - + + Upon the completion of a scan where a key request remained + outstanding on the primary replica and a starting node died, the + scan did not terminate. This caused incompleted error handling + of the failed node. + - MySQL Cluster - - Upon the completion of a scan where a key request remained - outstanding on the primary replica and a starting node died, - the scan did not terminate. This caused incompleted error - handling of the failed node. - - - - @@ -48845,6 +48813,7 @@ + @@ -48857,18 +48826,13 @@ - + + A trigger updating the value of an + AUTO_INCREMENT column in an + NDB table would insert an error code rather + than the expected value into the column. + - MySQL Cluster - - A trigger updating the value of an - AUTO_INCREMENT column in an - NDB table would insert an error code rather - than the expected value into the column. - - - - @@ -62874,16 +62838,11 @@ - + + On 64-bit Solaris 9, the cluster would time out and crash after + the first query was made. + - MySQL Cluster - - The cluster would time out and crash after first query on - 64-bit Solaris 9. - - - - @@ -72721,6 +72680,7 @@ + @@ -72733,19 +72693,14 @@ - + + Not allowing sufficient parallelism in the cluster's + configuration (for example, by setting + NoOfTransactions too small) caused + ndb_restore to fail without providing any + error messages. + - MySQL Cluster - - Not allowing sufficient parallelism in the cluster's - configuration (for example, by setting - NoOfTransactions too small) caused - ndb_restore to fail without providing any - error messages. - - - - @@ -75306,6 +75261,7 @@ + @@ -75318,17 +75274,12 @@ - + + Insert records were incorrectly applied by + ndb_restore, thus making restoration from + backup inconsistent if the binlog contained inserts. + - MySQL Cluster - - Insert records were incorrectly applied by - ndb_restore, thus making restoration from - backup inconsistent if the binlog contained inserts. - - - - @@ -80568,6 +80519,7 @@ + @@ -80576,18 +80528,13 @@ - + + The Ndb::startTransaction() method now + provides an alternative interface for starting a transaction. + See , for more + information. + - Cluster APIs - - The Ndb::startTransaction() method now - provides an alternative interface for starting a transaction. - See , for more - information. - - - - @@ -81691,6 +81638,7 @@ + @@ -81703,16 +81651,11 @@ - + + When using dynamically allocated ports on Linux, the cluster + would hang on initial startup. + - MySQL Cluster - - When using dynamically allocated ports on Linux, the cluster - would hang on initial startup. - - - - @@ -87510,6 +87453,7 @@ + @@ -87522,21 +87466,16 @@ - + + Trying to run ndbd as system + root when connecting to a + mysqld process running as the + mysql system user via SHM caused the + ndbd process to crash. + (ndbd should now exit gracefully with an + appropriate error message instead.) + - MySQL Cluster - - Trying to run ndbd as system - root when connecting to a - mysqld process running as the - mysql system user via SHM caused the - ndbd process to crash. - (ndbd should now exit gracefully with an - appropriate error message instead.) - - - - @@ -90899,6 +90838,7 @@ + @@ -90912,18 +90852,13 @@ - + + Placing multiple [TCP DEFAULT] sections in + the cluster's config.ini file crashed + ndb_mgmd. (The process now exits gracefully + in such cases, with an appropriate error message.) + - MySQL Cluster - - Placing multiple [TCP DEFAULT] sections in - the cluster's config.ini file - crashed ndb_mgmd. (The process now exits - gracefully in such cases, with an appropriate error message.) - - - - @@ -93994,6 +93929,7 @@ + @@ -94006,23 +93942,17 @@ - + + A new smart node allocation algorithm means that + it is no longer necessary to use sequential IDs for cluster + nodes, and that nodes not explicitly assigned IDs should now + have IDs allocated automatically in most cases. In practical + terms, this means that it is now possible to assign a set of + node IDs such as 1, 2, + 4, 5 without an error + being generated due to the missing 3. + - MySQL Cluster - - A new smart node allocation algorithm means - that it is no longer necessary to use sequential IDs for - cluster nodes, and that nodes not explicitly assigned IDs - should now have IDs allocated automatically in most cases. In - practical terms, this means that it is now possible to assign - a set of node IDs such as 1, - 2, 4, - 5 without an error being generated due to - the missing 3. - - - - @@ -98249,6 +98179,7 @@ + @@ -98261,17 +98192,12 @@ - + + The ndb_mgm client' + SHOW command displayed incorrect output after + master data node failure. + - MySQL Cluster - - The ndb_mgm client SHOW - command displayed incorrect output after master data node - failure. - - - - @@ -106786,6 +106712,7 @@ + @@ -106799,19 +106726,13 @@ - + + When deleting a great many (tens of thousands of) rows at once + from an NDB table, an improperly dereferenced + pointer could cause the mysqld process to + crash. + - MySQL Cluster - - NDBCluster: When deleting a great many - (tens of thousands of) rows at once from an - NDB table, an improperly dereferenced - pointer could cause the mysqld process to - crash. - - - - @@ -108482,6 +108403,7 @@ + @@ -108494,17 +108416,11 @@ - + + Connections between data nodes and management nodes were not + being closed following shutdown of ndb_mgmd. + - MySQL Cluster - - Connections between data nodes and management nodes were not - being closed following shutdown of - ndb_mgmd. - - - - @@ -117319,6 +117235,7 @@ + @@ -117335,18 +117252,13 @@ - + + A number of new or improved error messages have been implemented + in this release in order to provide better and more accurate + diagnostic information regarding cluster configuration issues + and problems. + - MySQL Cluster - - A number of new or improved error messages have been - implemented in this release in order to provide better and - more accurate diagnostic information regarding cluster - configuration issues and problems. - - - - @@ -117989,6 +117901,7 @@ + @@ -118002,35 +117915,30 @@ - + + When running more than one management process in a cluster: + - MySQL Cluster - - When running more than one management process in a cluster: - + + + ndb_mgm -c + host:port + -e "node_id + stop" would stop a management process + running only on the same system on which the command was + issued. + + + + + ndb_mgm -e "shutdown" failed + to shut down any management processes at all. + + - - - ndb_mgm -c - host:port - -e "node_id - stop" would stop a management process - running only on the same system on which the command was - issued. - - - - - ndb_mgm -e "shutdown" - failed to shut down any management processes at all. - - + + - - - - - @@ -119166,6 +119074,7 @@ + @@ -119178,16 +119087,11 @@ - + + Calling ndb_select_count() crashed the + cluster when running on Red Hat Enterprise 4/64-bit/Opteron. + - MySQL Cluster - - Calling ndb_select_count() crashed the - cluster when running on Red Hat Enterprise 4/64-bit/Opteron. - - - - @@ -127528,6 +127432,7 @@ + @@ -127540,23 +127445,17 @@ - + + Updating a TEXT-type column during a cluster + backup could cause the ndbd process to crash, + due to the incorrect use of charset-normalized reads for. This + could also lead to wrong data in the backup if + such a column was updated during the backup; for example, + supposing that the column used latin_ci, then + aAa might be stored in the + backup as AAA. + - MySQL Cluster - - Updating a TEXT-type column during a - cluster backup could cause the ndbd process - to crash, due to the incorrect use of charset-normalized reads - for. This could also lead to wrong data in the - backup if such a column was updated during the backup; for - example, supposing that the column used - latin_ci, then - aAa might be stored in the - backup as AAA. - - - - @@ -129242,6 +129141,7 @@ + @@ -129255,17 +129155,11 @@ - + + The ndb_autodiscover test failed sporadically + due to a node not being permitted to connect to the cluster. + - MySQL Cluster - - The ndb_autodiscover test failed - sporadically due to a node not being permitted to connect to - the cluster. - - - - @@ -129348,6 +129242,7 @@ + @@ -129360,18 +129255,13 @@ - + + The perror utility included with the + MySQL-Server RPM now provides support for the + option, and so can be used to obtain + error message text for MySQL Cluster error codes. + - MySQL Cluster - - The perror utility included with the - MySQL-Server RPM now provides support for - the option, and so can be used to - obtain error message text for MySQL Cluster error codes. - - - - @@ -131228,6 +131118,7 @@ + @@ -131240,16 +131131,11 @@ - + + The server left core files following shutdown if data nodes had + failed. + - MySQL Cluster - - The server left core files following shutdown if data nodes - had failed. - - - - @@ -133365,6 +133251,7 @@ + @@ -133377,20 +133264,15 @@ - + + ndb_mgmd would allow a node to be stopped or + restarted while another node was still starting up, which could + crash the cluster. It should now not be possible to issue a node + stop or restart while a different node is still restarting, and + the cluster management client issues an error if an attempt is + made to do so. + - MySQL Cluster - - ndb_mgmd would allow a node to be stopped - or restarted while another node was still starting up, which - could crash the cluster. It should now not be possible to - issue a node stop or restart while a different node is still - restarting, and the cluster management client issues an error - if an attempt is made to do so. - - - - @@ -134493,6 +134375,7 @@ + @@ -134505,25 +134388,20 @@ - + + The average row size for Cluster tables was being calculated + incorrectly. This affected the values shown for the + Data_length and + Avg_row_length columns in the output + generated by SHOW TABLE STATUS as well as the + values for the data_length and + data_length/table_rows columns shown in the + TABLES table of the + INFORMATION_SCHEMA database with respect to + Cluster tables (tables using other storage engines were not + affected by this bug). + - MySQL Cluster - - The average row size for Cluster tables was being calculated - incorrectly. This affected the values shown for the - Data_length and - Avg_row_length columns in the output - generated by SHOW TABLE STATUS as well as - the values for the data_length and - data_length/table_rows columns shown in the - TABLES table of the - INFORMATION_SCHEMA database with respect to - Cluster tables (tables using other storage engines were not - affected by this bug). - - - -