From: jon Date: November 6 2007 10:34pm Subject: svn commit - mysqldoc@docsrva: r8562 - trunk/dynamic-docs/changelog List-Archive: http://lists.mysql.com/commits/37229 Message-Id: <200711062234.lA6MYkpb006756@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: jstephens Date: 2007-11-06 23:34:45 +0100 (Tue, 06 Nov 2007) New Revision: 8562 Log: More Cluster changelog entry cleanups Modified: trunk/dynamic-docs/changelog/mysqld.xml Modified: trunk/dynamic-docs/changelog/mysqld.xml =================================================================== --- trunk/dynamic-docs/changelog/mysqld.xml 2007-11-06 20:37:15 UTC (rev 8561) +++ trunk/dynamic-docs/changelog/mysqld.xml 2007-11-06 22:34:45 UTC (rev 8562) Changed blocks: 123, Lines Added: 198, Lines Deleted: 184; 36905 bytes @@ -79776,8 +79776,6 @@ - - @@ -80177,7 +80175,7 @@ - + @@ -80192,9 +80190,9 @@ - (Disk Data): 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. + 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. @@ -81783,6 +81781,7 @@ + @@ -81798,7 +81797,8 @@ - Cluster failed to build with gcc 4.0. + NDB failed to build with + gcc 4.0. @@ -82314,7 +82314,6 @@ - @@ -84283,6 +84282,7 @@ + @@ -84426,7 +84426,7 @@ The cluster created a crashed replica of a table having an ordered index — or when logging was not enabled, of a table having a table or unique index — leading to a crash - of the cluster following 8 successibe restarts. + of the cluster following 8 successive restarts. @@ -84562,8 +84562,8 @@ When a schema was detected to be corrupt, ndb - neglected to close it, resulting in a file already - open error if the schema was opened again later. + neglected to close it, resulting in a file already + open error if the schema was opened again later. written. @@ -85715,7 +85715,6 @@ - @@ -86136,8 +86135,7 @@ - (Cluster APIs): A call to - CHECK_TIMEDOUT_RET() in + A call to CHECK_TIMEDOUT_RET() in mgmapi.cpp should have been a call to DBUG_CHECK_TIMEDOUT_RET(). @@ -86410,6 +86408,7 @@ + @@ -86565,7 +86564,7 @@ - + @@ -86580,8 +86579,8 @@ - (Disk Data): Trying to create Disk Data tables when running the - cluster in diskless mode would crash the cluster's data nodes. + Trying to create Disk Data tables when running the cluster in + diskless mode caused cluster data nodes to crash. @@ -87742,8 +87741,8 @@ + - @@ -88334,13 +88333,11 @@ + - - - @@ -89003,6 +89000,7 @@ + @@ -89273,14 +89271,15 @@ + + - @@ -90450,6 +90449,7 @@ + @@ -90461,10 +90461,10 @@ - Added [mysql_cluster] section to - my.cnf file for configuration settings - specific to MySQL Cluster. ndb-connectstring - variable moved here. + Added support for a [mysql_cluster] section + to the my.cnf file for configuration + settings specific to MySQL Cluster. The + ndb-connectstring variable was moved here. @@ -90617,7 +90617,7 @@ - + @@ -90627,8 +90627,8 @@ + - @@ -90636,8 +90636,7 @@ - (Cluster APIs): libndbclient.so was not - versioned. + libndbclient.so was not versioned. @@ -91582,11 +91581,10 @@ + - - @@ -91601,7 +91599,7 @@ - Placing multiple [TCP DEFAULT] sections in + 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.) @@ -92434,8 +92432,9 @@ - Wrong error message displayed when cluster management server - closed port while mysqld was connecting. + The wrong error message was displayed when the cluster + management server port was closed while a + mysqld process was trying to connect. @@ -93302,6 +93301,7 @@ + @@ -93730,7 +93730,7 @@ Using ORDER BY - primary_key_column when + primary_key_column when selecting from a table having the primary key on a VARCHAR column caused a forced shutdown of the cluster. @@ -93982,10 +93982,9 @@ - + - @@ -94520,9 +94519,9 @@ + - @@ -94548,6 +94547,7 @@ + @@ -94560,9 +94560,9 @@ - Added support for the CREATE INDEX and - DROP INDEX statements to the NDB - Cluster storage engine. + The NDB storage engine now supports the + CREATE INDEX and DROP + INDEX statements. @@ -94597,9 +94597,8 @@ + - - @@ -95027,11 +95026,12 @@ - Row-based replication was not being set up correctly if a backup - was already in progress. For example, connecting a + Row-based replication was not set up correctly if a backup was + already in progress. For example, connecting a mysqld instance to a cluster which was being backed up would result in the message NDB: skipping - setup table test.t1 being written to the error log. + setup table tbl_name + being written to the error log. @@ -95282,7 +95282,7 @@ - + @@ -95300,9 +95300,9 @@ - (Replication): Using the option - caused problems with CREATE TABLE on the - cluster acting as the replication master. + Using the option caused problems + with CREATE TABLE on the cluster acting as + the replication master. @@ -95389,6 +95389,7 @@ + @@ -96640,6 +96641,8 @@ + + @@ -96654,7 +96657,8 @@ Replication between MySQL Clusters is now supported. It is now also possible to replicate between a MySQL Cluster and a non-cluster database. See - . + , for more + information. @@ -97131,6 +97135,7 @@ + @@ -97147,11 +97152,10 @@ - NDB: Specifying the wrong nodegroup in a - CREATE TABLE using partitioning would lead to - the table name being locked after the CREATE - TABLE statement failed (that is, the table name could - not be re-used). + Specifying the wrong nodegroup in a CREATE + TABLE statement using partitioning would lead to the + table name being locked after the statement failed (that is, the + table name could not be re-used). @@ -97176,8 +97180,8 @@ - A memory allocation failure in the cluster Subscription Manager - could cause the cluster to crash. + A memory allocation failure in SUMA (the + cluster Subscription Manager) could cause the cluster to crash. @@ -97350,7 +97354,7 @@ - + @@ -97373,7 +97377,7 @@ As part of the fix for this bug, two new NDB API methods were added to the NdbDictionary::Object::Table - class. See the MySQL Cluster API documentation for details. + class. See , for details. @@ -97413,7 +97417,7 @@ - + @@ -97826,6 +97830,7 @@ + @@ -97960,7 +97965,7 @@ - Restarting a failed node could crash the cluster. + Restarting a failed node could sometimes crash the cluster. @@ -98270,6 +98275,7 @@ + @@ -98316,9 +98322,9 @@ + - @@ -98335,10 +98341,10 @@ - NDB: A cluster shutdown following the crash - of a data node would fail to terminate the remaining node - processes, even though ndb_mgm showed the - shutdown request as having been completed. + A cluster shutdown following the crash of a data node failed to + terminate any remaining node processes, even though + ndb_mgm showed the shutdown request as having + been completed. @@ -98348,7 +98354,7 @@ - + @@ -98364,10 +98370,10 @@ - (NDB API): When using the - NdbTransaction::execute() method, a very long - timeout (greater than 5 minutes) could result if the last data - node being polled was disconnected from the cluster. + When using the NdbTransaction::execute() + method, a very long timeout (greater than 5 minutes) could + result if the last data node being polled was disconnected from + the cluster. @@ -98670,7 +98676,7 @@ - Cluster backups would fail when there were more than 2048 schema + Cluster backups failed when there were more than 2048 schema objects in the cluster. @@ -98772,10 +98778,10 @@ + - @@ -98789,7 +98795,7 @@ - The ndb_mgm client' + The ndb_mgm client's SHOW command displayed incorrect output after master data node failure. @@ -99613,6 +99619,7 @@ + @@ -100541,10 +100548,10 @@ + + - - @@ -100912,6 +100919,7 @@ + @@ -101149,7 +101157,7 @@ - + @@ -101165,9 +101173,8 @@ - (Disk Data): Use of a tablespace whose - INITIAL_SIZE was greater than 1 GB could - cause the cluster to crash. + Use of a tablespace whose INITIAL_SIZE was + greater than 1 GB could cause the cluster to crash. @@ -101556,6 +101563,7 @@ + @@ -102241,8 +102249,9 @@ It is now possible to perform a partial start of a cluster. That - is, it is now possible to bring up the cluster without running - ndbd &ddash;initial on all configured data nodes first. + is, it is now possible to bring up the cluster without first + running ndbd on + all configured data nodes. @@ -102252,7 +102261,7 @@ - + @@ -103505,15 +103514,15 @@ + + - - - Hosts in clusters with a large number of nodes could experience + Hosts in clusters with large numbers of nodes could experience excessive CPU usage while obtaining configuration data. @@ -103524,8 +103533,8 @@ + - @@ -104181,6 +104190,7 @@ + @@ -104484,6 +104494,7 @@ + @@ -104500,11 +104511,11 @@ are now variable-sized; that is, they now only allocate as much space as required to store the data. Previously, a VARCHAR(n) column - allocated n+2 bytes (aligned to 4 bytes), regardless if the - actual inserted value required that much space. (In other words, - a VARCHAR column always required the same, - fixed, amount of storage as a CHAR column of - the same size.) + allocated n+2 bytes (aligned to 4 bytes), regardless of whether + the actual inserted value required that much space. (In other + words, a VARCHAR column always required the + same, fixed, amount of storage as a CHAR + column of the same size.) @@ -104514,6 +104525,7 @@ + @@ -104832,6 +104844,7 @@ + @@ -104847,9 +104860,9 @@ 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. + server, trying to drop an NDB table from a + second MySQL server connected to the same cluster would cause + the second MySQL server to hang. @@ -105156,7 +105169,7 @@ - + @@ -105243,6 +105256,7 @@ + @@ -105260,8 +105274,8 @@ The temporary tables created by an ALTER - TABLE on a cluster table were visible to all MySQL - servers. + TABLE on an NDB table were visible + to all SQL nodes in the cluster. @@ -105959,7 +105973,8 @@ - + + @@ -105975,8 +105990,8 @@ - (Cluster Replication / Disk Data): An issue with replication of - Disk Data tables could in some cases lead to node failure. + An issue with replication of Disk Data tables could in some + cases lead to node failure. @@ -106063,6 +106078,7 @@ + @@ -106075,8 +106091,8 @@ A single cluster can now support up to 255 API nodes, including MySQL servers acting as SQL nodes. See - Issues - exclusive to MySQL Cluster for more information. + , + for more information. @@ -106526,9 +106542,9 @@ + - @@ -106681,7 +106697,7 @@ - + @@ -106696,9 +106712,9 @@ - (Disk Data): Concurrent table schema operations and operations - on log files groups, tablespaces, data files, or undofiles could - lead to Cluster node failures. + Concurrent table schema operations and operations on log file + groups, tablespaces, data files, or undo files could lead to + data node failures. @@ -106972,10 +106988,9 @@ + - - @@ -107086,7 +107101,7 @@ - + @@ -107101,9 +107116,9 @@ - (Disk Data): When restoring from backup a cluster containing any - Disk Data tables with hidden primary keys, a node failure - resulted which could lead to a crash of the cluster. + When restoring from backup a cluster containing any Disk Data + tables with hidden primary keys, a node failure resulted which + could lead to a crash of the cluster. @@ -107225,7 +107240,7 @@ - + @@ -107240,8 +107255,8 @@ - (Disk Data): Extents that should have been available for re-use - following a DROP TABLE operation were not actually made + Extents that should have been available for re-use following a + DROP TABLE operation were not actually made available again until after the cluster performed a local checkpoint. @@ -107375,7 +107390,7 @@ A forced cluster shutdown occurred when the management daemon was restarted with a changed config.ini - file that added an API/SQL node. + file that added an API or SQL node. @@ -108393,7 +108408,6 @@ - @@ -108500,7 +108514,7 @@ - + @@ -108516,8 +108530,8 @@ - The mgm client command ALL - CLUSTERLOG STATISTICS=15; had no effect. + The ndb_mgm client command ALL + CLUSTERLOG STATISTICS=15 had no effect. @@ -108661,7 +108675,7 @@ Connections between data nodes and management nodes were not - being closed following shutdown of ndb_mgmd. + closed following shutdown of ndb_mgmd. @@ -108852,9 +108866,10 @@ - + + @@ -108871,9 +108886,9 @@ - Provide more informative error messages in clustered setting - when a query is issued against a table that has been modified by - another mysqld server. + More informative error messages are provided when a query is + issued against an NDB table that has been + modified by another mysqld server. @@ -109285,8 +109300,8 @@ + - @@ -109331,8 +109346,8 @@ Users who had the SHOW VIEW privilege for a - view and privileges on one of the view's base table could not - see records in INFORMATION_SCHEMA tables + view and privileges on one of the view's base tables could + not see records in INFORMATION_SCHEMA tables relating to the base table. @@ -109651,6 +109666,7 @@ + @@ -109816,7 +109832,7 @@ - + @@ -109832,8 +109848,8 @@ - (Replication): Following a restart of the master cluster, the - latest GCI was set to 0 upon reconnection to the slave. + Following a restart of the master cluster, the latest GCI was + set to 0 upon reconnection to the slave. @@ -109989,9 +110005,9 @@ A new startup option for - ndbd makes it possible to skip - specific nodes without waiting for them to start when starting - the cluster. See + ndbd makes it possible to skip specified + nodes without waiting for them to start when starting the + cluster. See . @@ -110161,6 +110177,7 @@ + @@ -110397,10 +110414,10 @@ + - @@ -110809,7 +110826,7 @@ - + @@ -110825,9 +110842,9 @@ - (Disk Data): Issuing a CREATE LOGFILE GROUP - statement during the drop of an NDB table - would cause database corruption. + Issuing a CREATE LOGFILE GROUP statement + during the drop of an NDB table would cause + database corruption. @@ -111050,8 +111067,8 @@ Unused open handlers for tables in which the metadata had changed were not properly closed. This could result in stale - results from Cluster tables following an ALTER - TABLE. + results from NDB tables following an + ALTER TABLE statement. @@ -112503,9 +112520,9 @@ - + @@ -113460,6 +113477,7 @@ + @@ -114076,8 +114094,8 @@ An excessive number of ALTER TABLE operations - could cause the cluster to fail with NDB error code 773 - (Out of string memory, please modify + could cause the cluster to fail with NDB + error code 773 (Out of string memory, please modify StringMemory). @@ -115732,7 +115750,7 @@ - + @@ -115747,9 +115765,9 @@ - (Disk Data): An issue with disk allocation could sometimes cause - a forced shutdown of the cluster when running a mix of memory - and Disk Data tables. + An issue with disk allocation could sometimes cause a forced + shutdown of the cluster when running a mix of memory and Disk + Data tables. @@ -115940,9 +115958,9 @@ - + @@ -116020,16 +116038,16 @@ - + - The cluster's data nodes would fail while trying to load data - when NoOfFrangmentLogFiles was equal to 1. + The cluster's data nodes failed while trying to load data when + NoOfFrangmentLogFiles was set equal to 1. @@ -117223,9 +117241,8 @@ + - - @@ -117795,15 +117812,15 @@ + - - A potential memory leak in the NDB storage - engine's handling of file operations was uncovered. + The NDB storage engine could leak memory + during file operations. @@ -117864,10 +117881,9 @@ + - - @@ -118165,7 +118181,6 @@ - @@ -118564,12 +118579,11 @@ - When a cluster node suffered a hard failure (such - as a power failure or loss of a network connection) TCP sockets - to the vanished 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. + When a cluster data node suffered a hard failure + (such as a power failure or loss of a network connection) TCP + sockets to the missing 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. @@ -118924,7 +118938,7 @@ - + @@ -118939,11 +118953,10 @@ - (Disk Data): It was possible to execute a statement for creating - a Disk Data table that referred to a nonexistent tablespace, in - which case the table was an in-memory NDB - table. Such a statement instead now fails with an appropriate - error message. + It was possible to execute a statement for creating a Disk Data + table that referred to a nonexistent tablespace, in which case + the table was an in-memory NDB table. Such a + statement instead now fails with an appropriate error message. @@ -118983,9 +118996,9 @@ + - @@ -118999,8 +119012,8 @@ - Calling ndb_select_count() crashed the - cluster when running on Red Hat Enterprise 4/64-bit/Opteron. + Running ndb_select_count crashed the cluster + when running on Red Hat Enterprise 4/64-bit/Opteron. @@ -119090,7 +119103,6 @@ - @@ -119365,6 +119377,7 @@ + @@ -119380,16 +119393,17 @@ - NDB: Trying to use a greater number of tables - then specified by the value of MaxNoOfTables - caused table corruption such that data nodes could not be - restarted. + Trying to use a greater number of tables than specified by the + value of MaxNoOfTables caused table + corruption such that data nodes could not be restarted. + +