| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | October 23 2007 2:49pm |
| Subject: | svn commit - mysqldoc@docsrva: r8254 - trunk/dynamic-docs/changelog | ||
| View as plain text | |||
Author: jstephens Date: 2007-10-23 14:49:51 +0200 (Tue, 23 Oct 2007) New Revision: 8254 Log: A few more cleanups of old Cluster changelog entries. Modified: trunk/dynamic-docs/changelog/mysqld.xml Modified: trunk/dynamic-docs/changelog/mysqld.xml =================================================================== --- trunk/dynamic-docs/changelog/mysqld.xml 2007-10-23 12:36:20 UTC (rev 8253) +++ trunk/dynamic-docs/changelog/mysqld.xml 2007-10-23 12:49:51 UTC (rev 8254) Changed blocks: 19, Lines Added: 201, Lines Deleted: 159; 15909 bytes @@ -5896,39 +5896,7 @@ <logentry entrytype="bug"> - <tags> - <manual type="cluster"/> - <manual type="ndb_mgmd"/> - <manual type="config.ini"/> - <manual type="NDBCluster"/> - </tags> - <bugs> - <fixes bugid="13611"/> - </bugs> - - <versions> - <version ver="5.0.15"/> - </versions> - - <message> - - <para> - <literal>NDBCluster</literal>: Placing multiple <literal>[TCP - DEFAULT]</literal> sections in the cluster - <filename>config.ini</filename> file crashed - <command>ndb_mgmd</command>. (The <command>ndb_mgmd</command> - process now exits gracefully with an appropriate error message - instead.) - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <bugs> <fixes bugid="20393"/> </bugs> @@ -5941,7 +5909,7 @@ <message> <para> - Usernames have a maximum length of 16 characters (even if they + User names have a maximum length of 16 characters (even if they contain multi-byte characters), but were being truncated to 16 bytes. </para> @@ -37170,11 +37138,16 @@ <message> - <para> - <literal>NDBCluster</literal>: A bitfield whose offset and - length totaled 32 would crash the cluster. - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + A <literal>BIT</literal> column whose offset and length + totaled 32 caused the cluster to crash. + </para> + + </formalpara> + </message> </logentry> @@ -45677,13 +45650,18 @@ <message> - <para> - <literal>NDBCluster</literal>: 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. - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + 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. + </para> + + </formalpara> + </message> </logentry> @@ -48875,13 +48853,18 @@ <message> - <para> - <literal>NDBCluster</literal>: A trigger updating the value of - an <literal>AUTO_INCREMENT</literal> column in a Cluster table - would insert an error code rather than the expected value into - the column. - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + A trigger updating the value of an + <literal>AUTO_INCREMENT</literal> column in an + <literal>NDB</literal> table would insert an error code rather + than the expected value into the column. + </para> + + </formalpara> + </message> </logentry> @@ -64378,7 +64361,7 @@ <message> <para> - <literal>NDB_MGMD</literal> was leaking file descriptors. + <command>ndb_mgmd</command> was leaking file descriptors. </para> </message> @@ -87535,16 +87518,21 @@ <message> - <para> - <literal>NDBCluster</literal>: Trying to run - <command>ndbd</command> as system <literal>root</literal> when - connecting to a <command>mysqld</command> process running as the - <literal>mysql</literal> system user via SHM caused the - <command>ndbd</command> process to crash. - (<command>ndbd</command> should now exit gracefully with an - appropriate error message instead.) - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + Trying to run <command>ndbd</command> as system + <literal>root</literal> when connecting to a + <command>mysqld</command> process running as the + <literal>mysql</literal> system user via SHM caused the + <command>ndbd</command> process to crash. + (<command>ndbd</command> should now exit gracefully with an + appropriate error message instead.) + </para> + + </formalpara> + </message> </logentry> @@ -90915,18 +90903,23 @@ <versions> <version ver="4.1.16"/> + <version ver="5.0.15"/> </versions> <message> - <para> - <literal>NDBCluster</literal>: Placing multiple <literal>[TCP - DEFAULT]</literal> sections in the cluster - <filename>config.ini</filename> file crashed - <command>ndb_mgmd</command>. (The process now exits gracefully - with an appropriate error message.) - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + Placing multiple <literal>[TCP DEFAULT]</literal> sections in + the cluster's <filename>config.ini</filename> file + crashed <command>ndb_mgmd</command>. (The process now exits + gracefully in such cases, with an appropriate error message.) + </para> + + </formalpara> + </message> </logentry> @@ -94009,18 +94002,23 @@ <message> - <para> - <literal>NDBCluster</literal>: A new <quote>smart</quote> 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 <literal>1</literal>, - <literal>2</literal>, <literal>4</literal>, <literal>5</literal> - without an error being generated due to the missing - <literal>3</literal>. - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + A new <quote>smart</quote> 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 <literal>1</literal>, + <literal>2</literal>, <literal>4</literal>, + <literal>5</literal> without an error being generated due to + the missing <literal>3</literal>. + </para> + + </formalpara> + </message> </logentry> @@ -98263,7 +98261,7 @@ <title>MySQL Cluster</title> <para> - The <literal>ndb_mgm</literal> client <literal>SHOW</literal> + The <command>ndb_mgm</command> client <literal>SHOW</literal> command displayed incorrect output after master data node failure. </para> @@ -106797,13 +106795,19 @@ <message> - <para> - <literal>NDBCluster</literal>: When performing a delete of a - great many (tens of thousands of) rows at once from a Cluster - table, an improperly dereferenced pointer could cause the - <command>mysqld</command> process to crash. - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + <literal>NDBCluster</literal>: When deleting a great many + (tens of thousands of) rows at once from an + <literal>NDB</literal> table, an improperly dereferenced + pointer could cause the <command>mysqld</command> process to + crash. + </para> + + </formalpara> + </message> </logentry> @@ -117327,13 +117331,18 @@ <message> - <para> - <literal>NDBCluster</literal>: 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. - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + 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. + </para> + + </formalpara> + </message> </logentry> @@ -117989,31 +117998,35 @@ <message> - <para> - <literal>NDBCluster</literal>: When running more than one - management process in a cluster: - </para> + <formalpara> - <itemizedlist> + <title>MySQL Cluster</title> + <para> + When running more than one management process in a cluster: + <itemizedlist> - <listitem> - <para> - <command>ndb_mgm -c - <replaceable>host</replaceable>:<replaceable>port</replaceable> - -e "<replaceable>node_id</replaceable> - stop"</command> would stop a management process running - only on the same system on which the command was issued. - </para> - </listitem> - <listitem> - <para> - <command>ndb_mgm -e "shutdown"</command> failed to - shut down any management processes at all. - </para> - </listitem> + <listitem> + <para> + <command>ndb_mgm -c + <replaceable>host</replaceable>:<replaceable>port</replaceable> + -e "<replaceable>node_id</replaceable> + stop"</command> would stop a management process + running only on the same system on which the command was + issued. + </para> + </listitem> + <listitem> + <para> + <command>ndb_mgm -e "shutdown"</command> + failed to shut down any management processes at all. + </para> + </listitem> - </itemizedlist> + </itemizedlist> + </para> + </formalpara> + </message> </logentry> @@ -127523,18 +127536,23 @@ <message> - <para> - <literal>NDBCluster</literal>: Updating a text-type column - during a cluster backup could cause the <command>ndbd</command> - process to crash, due to the incorrect use of charset-normalized - reads for. This could also lead to <quote>wrong</quote> data in - the backup if such a column was updated during the backup; for - example, supposing that the column used - <literal>latin_ci</literal>, then <quote> <literal>aAa</literal> - </quote> might be stored in the backup as <quote> - <literal>AAA</literal> </quote>. - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + Updating a <literal>TEXT</literal>-type column during a + cluster backup could cause the <command>ndbd</command> process + to crash, due to the incorrect use of charset-normalized reads + for. This could also lead to <quote>wrong</quote> data in the + backup if such a column was updated during the backup; for + example, supposing that the column used + <literal>latin_ci</literal>, then + <quote><literal>aAa</literal></quote> might be stored in the + backup as <quote><literal>AAA</literal></quote>. + </para> + + </formalpara> + </message> </logentry> @@ -129233,12 +129251,17 @@ <message> - <para> - <literal>NDBCluster</literal>: The - <literal>ndb_autodiscover</literal> test failed sporadically due - to a node not being permitted to connect to the cluster. - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + The <literal>ndb_autodiscover</literal> test failed + sporadically due to a node not being permitted to connect to + the cluster. + </para> + + </formalpara> + </message> </logentry> @@ -129333,14 +129356,18 @@ <message> - <para> - <literal>NDBCluster</literal>: The <command>perror</command> - utility included with the <literal>MySQL-Server</literal> RPM - now provides support for the <option>--ndb</option> option, and - so can be used to obtain error message text for MySQL Cluster - error codes. - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + The <command>perror</command> utility included with the + <literal>MySQL-Server</literal> RPM now provides support for + the <option>--ndb</option> option, and so can be used to + obtain error message text for MySQL Cluster error codes. + </para> + + </formalpara> + </message> </logentry> @@ -131209,11 +131236,16 @@ <message> - <para> - <literal>NDBCLuster</literal>: Server left core files following - shutdown if data nodes had failed. - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + The server left core files following shutdown if data nodes + had failed. + </para> + + </formalpara> + </message> </logentry> @@ -133341,15 +133373,20 @@ <message> - <para> - <literal>NDBCluster</literal>: <command>ndb_mgmd</command> 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. - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + <command>ndb_mgmd</command> 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. + </para> + + </formalpara> + </message> </logentry> @@ -134464,20 +134501,25 @@ <message> - <para> - <literal>NDBCluster</literal>: The average row size for Cluster - tables was being calculated incorrectly. This affected the - values shown for the <literal>Data_length</literal> and - <literal>Avg_row_length</literal> columns in the output - generated by <literal>SHOW TABLE STATUS</literal> as well as the - values for the <literal>data_length</literal> and - <literal>data_length/table_rows</literal> columns shown in the - <literal>TABLES</literal> table of the - <literal>INFORMATION_SCHEMA</literal> database with respect to - Cluster tables (tables using other storage engines were not - affected by this bug). - </para> + <formalpara> + <title>MySQL Cluster</title> + <para> + The average row size for Cluster tables was being calculated + incorrectly. This affected the values shown for the + <literal>Data_length</literal> and + <literal>Avg_row_length</literal> columns in the output + generated by <literal>SHOW TABLE STATUS</literal> as well as + the values for the <literal>data_length</literal> and + <literal>data_length/table_rows</literal> columns shown in the + <literal>TABLES</literal> table of the + <literal>INFORMATION_SCHEMA</literal> database with respect to + Cluster tables (tables using other storage engines were not + affected by this bug). + </para> + + </formalpara> + </message> </logentry>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r8254 - trunk/dynamic-docs/changelog | jon | 23 Oct |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.729 sec. using MySQL 5.1.14-beta-log