Author: jstephens
Date: 2007-11-07 10:58:59 +0100 (Wed, 07 Nov 2007)
New Revision: 8564
Log:
Finished fixups of Cluster changelog entries.
Modified:
trunk/dynamic-docs/changelog/mysqld.xml
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2007-11-07 00:00:13 UTC (rev 8563)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2007-11-07 09:58:59 UTC (rev 8564)
Changed blocks: 188, Lines Added: 348, Lines Deleted: 298; 60164 bytes
@@ -3889,6 +3889,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="ndbd"/>
</tags>
@@ -4073,6 +4074,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="ndb_mgm"/>
</tags>
@@ -4083,8 +4085,8 @@
<message>
<para>
- <command>ndb_mgm -e "shutdown"</command> failed to
- shut down any management processes at all.
+ <command>ndb_mgm -e "SHUTDOWN"</command> failed to shut down any
+ management processes at all.
</para>
</message>
@@ -8914,10 +8916,10 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="clusterreplication"/>
<manual type="replication"/>
<manual type="cluster"/>
<manual type="ndb_conflict_fn_max"/>
- <highlight type="clusterreplication"/>
</tags>
<versions>
@@ -12170,7 +12172,7 @@
<logentry entrytype="feature">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<manual type="cluster"/>
<manual type="ndb_mgm_get_clusterlog_loglevel"/>
</tags>
@@ -12182,9 +12184,8 @@
<message>
<para>
- (Cluster APIs): A new
- <literal>ndb_mgm_get_clusterlog_loglevel()</literal> function
- was added to the MGM API.
+ A new <literal>ndb_mgm_get_clusterlog_loglevel()</literal>
+ function was added to the MGM API.
</para>
<para>
@@ -14803,7 +14804,7 @@
<logentry entrytype="feature">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<manual type="cluster"/>
<manual type="ndb_mgm_number_of_mgmd_in_connect_string"/>
<manual type="ndb_mgm_set_timeout"/>
@@ -14816,9 +14817,9 @@
<message>
<para>
- (APIs): The MGM API now supports explicit setting of network
- timeouts using the <literal>ndb_mgm_set_timeout()</literal>
- function. A utility function
+ The MGM API now supports explicit setting of network timeouts
+ using the <literal>ndb_mgm_set_timeout()</literal> function. A
+ utility function
<literal>ndb_mgm_number_of_mgmd_in_connect_string()</literal> is
also implemented to facilitate calculation of timeouts based on
the number of management servers in the cluster.
@@ -15657,7 +15658,6 @@
<tags>
<highlight type="cluster"/>
<manual type="ndb-connectstring"/>
- <manual type="c"/>
<manual type="ndb_config"/>
</tags>
@@ -15666,9 +15666,9 @@
</bugs>
<versions>
+ <version ver="5.0.30"/>
<version ver="5.0.33"/>
<version ver="5.1.12"/>
- <version ver="5.0.30"/>
</versions>
<message>
@@ -15985,7 +15985,7 @@
<message>
<para>
- Receipt of several <literal>enter single user mode</literal>
+ Receipt of several <literal>ENTER SINGLE USER MODE</literal>
commands by multiple <command>ndb_mgmd</command> processes
within a short period of time resulted in cluster shutdown.
</para>
@@ -16502,6 +16502,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="ndb-use-copying-alter-table"/>
<manual type="cluster"/>
<manual type="mysqld"/>
@@ -16518,7 +16519,7 @@
Added the <option>--ndb-use-copying-alter-table</option> option
to <command>mysqld</command> to provide a fallback in case of
problems with online <literal>ALTER TABLE</literal> operations
- on <literal>NDBCluster</literal> tables.
+ on <literal>NDB</literal> tables.
</para>
</message>
@@ -16664,6 +16665,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="bind-address"/>
<manual type="ndb_mgmd"/>
@@ -16910,7 +16912,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<manual type="ndb_mgm_listen_event"/>
</tags>
@@ -16925,7 +16927,7 @@
<message>
<para>
- (Direct APIss): Invoking the MGM API function
+ Invoking the MGM API function
<literal>ndb_mgm_listen_event()</literal> caused a memory leak.
</para>
@@ -17252,20 +17254,22 @@
</bugs>
<versions>
+ <version ver="4.1.22"/>
<version ver="5.0.33"/>
<version ver="5.1.12"/>
- <version ver="4.1.22"/>
</versions>
<message>
<para>
The output for the <option>--help</option> option used with
- <literal>NDB</literal> executable programs
- (<command>ndbd</command>, <command>ndb_mgm</command>,
+ <literal>NDB</literal> executable programs (such as
+ <command>ndbd</command>, <command>ndb_mgm</command>,
<command>ndb_restore</command>, <command>ndb_config</command>,
- and so on) referred to the <filename>Ndb.cfg</filename> file,
- instead of <filename>my.cnf</filename>.
+ and others mentioned in
+ <xref linkend="mysql-cluster-utilities"/>) referred to the
+ <filename>Ndb.cfg</filename> file, instead of to
+ <filename>my.cnf</filename>.
</para>
</message>
@@ -19595,9 +19599,10 @@
<message>
<para>
- Trying to perform a <literal>DELETE</literal> from a Cluster
- table following a <literal>LOCK TABLES</literal> would cause the
- <command>ndbd</command> processes to hang.
+ Trying to perform a <literal>DELETE</literal> from an
+ <literal>NDB</literal> table following a <literal>LOCK
+ TABLES</literal> caused the <command>ndbd</command> processes to
+ hang.
</para>
</message>
@@ -20382,9 +20387,9 @@
</bugs>
<versions>
+ <version ver="4.1.22"/>
+ <version ver="5.0.25"/>
<version ver="5.1.12"/>
- <version ver="5.0.25"/>
- <version ver="4.1.22"/>
</versions>
<message>
@@ -21303,7 +21308,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<manual type="NdbApi.h"/>
<manual type="my_config.h"/>
</tags>
@@ -21319,7 +21324,7 @@
<message>
<para>
- (NDB API): The inclusion of <filename>my_config.h</filename> in
+ The inclusion of <filename>my_config.h</filename> in
<filename>NdbApi.h</filename> required anyone wishing to write
NDB API applications against MySQL 5.1 to have a complete copy
of the 5.1 sources.
@@ -22549,8 +22554,8 @@
<message>
<para>
- The output from <command>ndb_config</command>
- <option>--config-file=<replaceable>file</replaceable> </option>
+ The output from <command>ndb_config
+ <option>--config-file=<replaceable>file</replaceable></option></command>
was sent to <literal>stdout</literal> rather than
<literal>stderr</literal>.
</para>
@@ -23421,10 +23426,28 @@
It is now possible to iterate over all existing
<literal>Ndb</literal> objects using three new methods of the
<literal>Ndb_cluster_connection</literal> class:
- <literal>lock_ndb_objects()</literal>,
- <literal>get_next_ndb_object()</literal>, and
- <literal>unlock_ndb_objects()</literal>. For more information
- about these methods and their use, see
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>lock_ndb_objects()</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>get_next_ndb_object()</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>unlock_ndb_objects()</literal>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ For more information about these methods and their use, see
<xref linkend="class-ndb-cluster-connection-get-next-ndb-object"/>,
in the MySQL Cluster API Guide.
</para>
@@ -25154,6 +25177,7 @@
<tags>
<highlight type="cluster"/>
+ <highlight type="importantchange"/>
<manual type="Ndb_config_from_host"/>
<manual type="Ndb_connected_host"/>
<manual type="Ndb_config_from_port"/>
@@ -27398,6 +27422,7 @@
<tags>
<highlight type="clusterapi"/>
+ <highlight type="importantchange"/>
<manual type="cluster"/>
<manual type="NdbRecord"/>
</tags>
@@ -27411,7 +27436,8 @@
<para>
A new <literal>NdbRecord</literal> object has been added to the
<literal>NDB</literal> API. This object provides mapping to a
- record stored in <literal>NDB</literal>.
+ record stored in <literal>NDB</literal>. See
+ <xref linkend="interface-ndbrecord"/>, for more information.
</para>
</message>
@@ -28116,7 +28142,6 @@
<highlight type="cluster"/>
<manual type="cluster"/>
<manual type="VARCHAR"/>
- <manual type="u"/>
<manual type="no-upgrade"/>
<manual type="ndb_restore"/>
</tags>
@@ -28135,10 +28160,10 @@
Formerly, restoring a cluster backup made on a MySQL 5.0 Cluster
to a 5.1 cluster using a 5.1 version of
<command>ndb_restore</command> did not resize
- <literal>VARCHAR</literal> columns as might be expected, but now
+ <literal>VARCHAR</literal> columns as might be expected; now,
the default behavior of <command>ndb_restore</command> in such
cases is to resize the <literal>VARCHAR</literal> columns. This
- new default behavior can be overridden using the
+ changed default behavior can be overridden using the
<option>--no-upgrade</option> (or <option>-u</option>) option
when invoking <command>ndb_restore</command>.
</para>
@@ -28441,7 +28466,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="diskdata"/>
<manual type="ndb_restore"/>
</tags>
@@ -28456,9 +28481,9 @@
<message>
<para>
- (Disk Data): <command>ndb_restore</command> could sometimes fail
- when attempting to restore Disk Data tables due to data node
- failure caused by accessing uninitialized memory.
+ <command>ndb_restore</command> sometimes failed when attempting
+ to restore Disk Data tables due to data node failure caused by
+ accessing uninitialized memory.
</para>
</message>
@@ -28608,9 +28633,9 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="clusterapi"/>
<manual type="Ndb_cluster_connection"/>
<manual type="cluster"/>
- <highlight type="clusterapi"/>
</tags>
<versions>
@@ -28826,10 +28851,10 @@
</bugs>
<versions>
+ <version ver="4.1.22"/>
+ <version ver="5.0.30"/>
<version ver="5.0.33"/>
<version ver="5.1.12"/>
- <version ver="5.0.30"/>
- <version ver="4.1.22"/>
</versions>
<message>
@@ -29835,9 +29860,9 @@
</bugs>
<versions>
+ <version ver="5.0.32"/>
<version ver="5.0.33"/>
<version ver="5.1.15"/>
- <version ver="5.0.32"/>
</versions>
<message>
@@ -32114,8 +32139,8 @@
</bugs>
<versions>
+ <version ver="5.0.32"/>
<version ver="5.0.33"/>
- <version ver="5.0.32"/>
<version ver="5.1.14"/>
</versions>
@@ -32123,8 +32148,8 @@
<para>
Using <literal>BIT</literal> values with any of the comparison
- methods of the <literal>NdbScanFilter</literal> class caused the
- cluster's data nodes to fail.
+ methods of the <literal>NdbScanFilter</literal> class caused
+ data nodes to fail.
</para>
</message>
@@ -32719,7 +32744,8 @@
<para>
Using the <option>--ndb-cluster-connection-pool</option> option
- could cause DDL statements to be executed twice.
+ for <command>mysqld</command> caused DDL statements to be
+ executed twice.
</para>
</message>
@@ -33979,13 +34005,12 @@
<message>
<para>
- The <command>ndb_mgm</command> client commands <literal>
- <replaceable>node_id</replaceable> START</literal> and <literal>
- <replaceable>node_id</replaceable> STOP</literal> now work with
- management nodes as well as data nodes. (However, using
- <literal>ALL</literal> for the
- <replaceable>node_id</replaceable> continues to affect all data
- nodes only.)
+ The <command>ndb_mgm</command> client commands
+ <literal><replaceable>node_id</replaceable> START</literal> and
+ <literal><replaceable>node_id</replaceable> STOP</literal> now
+ work with management nodes as well as data nodes. However, using
+ <literal>ALL</literal> for <replaceable>node_id</replaceable>
+ continues to affect all data nodes only.
</para>
</message>
@@ -34107,9 +34132,9 @@
</bugs>
<versions>
+ <version ver="5.0.34"/>
+ <version ver="5.0.37"/>
<version ver="5.1.15"/>
- <version ver="5.0.37"/>
- <version ver="5.0.34"/>
</versions>
<message>
@@ -34389,8 +34414,8 @@
<versions>
<version ver="5.0.33"/>
+ <version ver="5.0.30"/>
<version ver="5.1.12"/>
- <version ver="5.0.30"/>
</versions>
<message>
@@ -34399,8 +34424,8 @@
The <literal>HELP</literal> command in the Cluster management
client now provides command-specific help. For example,
<literal>HELP RESTART</literal> in <command>ndb_mgm</command>
- provides detailed information about the <literal>START</literal>
- command.
+ provides detailed information about the
+ <literal>RESTART</literal> command.
</para>
</message>
@@ -35051,6 +35076,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="diskdata"/>
<manual type="ndb_restore"/>
</tags>
@@ -35065,8 +35091,9 @@
<message>
<para>
- Status messages added to <command>ndb_restore</command> to allow
- users to know that data files for Disk Data are being created.
+ Status messages have been added to
+ <command>ndb_restore</command> to enable users to know that data
+ files for Disk Data are being created.
</para>
</message>
@@ -35468,8 +35495,9 @@
<para>
The <command>ndb_show_tables</command> utility now displays
- information about table events. (See
- <xref linkend="mysql-cluster-utilities-ndb-show-tables"/>.)
+ information about table events. See
+ <xref linkend="mysql-cluster-utilities-ndb-show-tables"/>, for
+ more information.
</para>
</message>
@@ -36176,7 +36204,7 @@
</logentry>
- <logentry entrytype="bug">
+ <logentry entrytype="feature">
<tags>
<highlight type="cluster"/>
@@ -36197,8 +36225,9 @@
<message>
<para>
- Corrected the parsing of the <literal>CLUSTERLOG</literal>
- command by <command>ndb_mgm</command> to allow multiple items.
+ The parsing of the <literal>CLUSTERLOG</literal> command by
+ <command>ndb_mgm</command> was corrected to allow multiple
+ items.
</para>
</message>
@@ -38154,7 +38183,7 @@
<tags>
<highlight type="cluster"/>
- <manual type="NDBD DEFAULT"/>
+ <manual type="ndbd default"/>
<manual type="Hostname"/>
<manual type="cluster"/>
</tags>
@@ -40763,8 +40792,8 @@
<message>
<para>
- <command>ndbd</command> could sometimes fail to start with the
- error <errortext>Node failure handling not completed</errortext>
+ <command>ndbd</command> sometimes failed to start with the error
+ <errortext>Node failure handling not completed</errortext>
following a graceful restart.
</para>
@@ -45100,15 +45129,15 @@
</bugs>
<versions>
+ <version ver="5.1.15-ndb-6.1.18"/>
<version ver="5.1.19-ndb-6.2.4"/>
- <version ver="5.1.15-ndb-6.1.18"/>
</versions>
<message>
<para>
Disk data meta-information that existed in
- <command>ndbd</command> might not be visible to
+ <command>ndbd</command> was not always visible to
<command>mysqld</command>.
</para>
@@ -45742,9 +45771,9 @@
</bugs>
<versions>
+ <version ver="5.0.30"/>
<version ver="5.0.33"/>
<version ver="5.1.12"/>
- <version ver="5.0.30"/>
</versions>
<message>
@@ -46077,9 +46106,9 @@
</bugs>
<versions>
+ <version ver="4.1.22"/>
+ <version ver="5.0.24"/>
<version ver="5.1.12"/>
- <version ver="5.0.24"/>
- <version ver="4.1.22"/>
</versions>
<message>
@@ -49223,7 +49252,6 @@
<highlight type="cluster"/>
<manual type="cluster"/>
<manual type="ndb_mgmd"/>
- <manual type="P"/>
<manual type="stdout"/>
</tags>
@@ -49442,6 +49470,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="ndb_error_reporter"/>
</tags>
@@ -52174,10 +52203,9 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="ndb_mgm"/>
- <manual type="a"/>
<manual type="help"/>
- <highlight type="cluster"/>
</tags>
<bugs>
@@ -52185,8 +52213,8 @@
</bugs>
<versions>
+ <version ver="5.1.22-ndb-6.2.7"/>
<version ver="5.1.22-ndb-6.3.4"/>
- <version ver="5.1.22-ndb-6.2.7"/>
<version ver="5.1.23"/>
<version ver="6.0.4"/>
</versions>
@@ -52920,8 +52948,9 @@
<message>
<para>
- Running out of DataMemory could sometimes crash
- <command>ndbd</command> and <command>mysqld</command> processes.
+ Running out of <literal>DataMemory</literal> could sometimes
+ crash <command>ndbd</command> and <command>mysqld</command>
+ processes.
</para>
</message>
@@ -54811,6 +54840,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="NDB_LE_Connected"/>
<manual type="STOP"/>
<manual type="NDB_LE_Disconnected"/>
@@ -56055,17 +56085,17 @@
</bugs>
<versions>
- <version ver="5.1.8"/>
<version ver="4.1.19"/>
<version ver="5.0.20"/>
+ <version ver="5.1.8"/>
</versions>
<message>
<para>
Inserting and deleting <literal>BLOB</literal> column values
- while a backup was in process could cause the loss of an
- <command>ndbd</command> node.
+ while a backup was in process could cause data nodes to shut
+ down.
</para>
</message>
@@ -57177,6 +57207,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="ndbd"/>
<manual type="transactions"/>
</tags>
@@ -57537,6 +57568,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="ndb_mgm"/>
</tags>
@@ -57549,9 +57581,9 @@
<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.
+ -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>
</message>
@@ -60289,8 +60321,8 @@
</bugs>
<versions>
+ <version ver="5.0.38"/>
<version ver="5.0.41"/>
- <version ver="5.0.38"/>
<version ver="5.1.16"/>
</versions>
@@ -60854,9 +60886,9 @@
</bugs>
<versions>
+ <version ver="5.0.30"/>
<version ver="5.0.33"/>
<version ver="5.1.12"/>
- <version ver="5.0.30"/>
</versions>
<message>
@@ -62089,10 +62121,10 @@
</bugs>
<versions>
+ <version ver="4.1.22"/>
+ <version ver="5.0.30"/>
<version ver="5.0.33"/>
<version ver="5.1.12"/>
- <version ver="5.0.30"/>
- <version ver="4.1.22"/>
</versions>
<message>
@@ -63526,7 +63558,7 @@
<para>
Multiple <command>ndb_mgmd</command> processes in a cluster did
- not know each other's IP addresses.
+ not know each other's IP addresses.
</para>
</message>
@@ -65802,7 +65834,8 @@
<logentry entrytype="bug">
<tags>
- <manual type="NDB_MGMD"/>
+ <highlight type="cluster"/>
+ <manual type="ndb_mgmd"/>
</tags>
<bugs>
@@ -65817,7 +65850,7 @@
<message>
<para>
- <command>ndb_mgmd</command> was leaking file descriptors.
+ <command>ndb_mgmd</command> leaked file descriptors.
</para>
</message>
@@ -68866,6 +68899,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="ndbd"/>
<manual type="times"/>
</tags>
@@ -69650,7 +69684,7 @@
<message>
<para>
- Server did not accept some fully-qualified trigger names.
+ The server did not accept some fully-qualified trigger names.
</para>
</message>
@@ -69660,6 +69694,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="ndb_mgm"/>
</tags>
@@ -69668,15 +69703,15 @@
</bugs>
<versions>
+ <version ver="5.0.25"/>
<version ver="5.1.12"/>
- <version ver="5.0.25"/>
</versions>
<message>
<para>
- A memory leak was found when running <literal>
- <command>ndb_mgm</command> -e "SHOW"</literal>.
+ A memory leak occurred when running <command>ndb_mgm -e
+ "SHOW"</command>.
</para>
</message>
@@ -73265,7 +73300,7 @@
<para>
The output from <command>ndb_restore
- <option>--print_data</option> </command> was incorrect for a
+ <option>--print_data</option></command> was incorrect for a
backup made of a database containing tables with
<literal>TINYINT</literal> or <literal>SMALLINT</literal>
columns.
@@ -75072,7 +75107,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="diskdata"/>
<manual type="CREATE UNIQUE INDEX"/>
</tags>
@@ -75087,7 +75122,7 @@
<message>
<para>
- (Disk Data): <literal>CREATE UNIQUE INDEX</literal> failed with
+ <literal>CREATE UNIQUE INDEX</literal> failed with
<errortext>Error 4243: Index not found</errortext>.
</para>
@@ -75226,7 +75261,7 @@
<message>
<para>
- Added a new <command>mysqld</command> option
+ Added the <command>mysqld</command> option
<option>--ndb-cluster-connection-pool</option> that allows a
single MySQL server to use multiple connections to the cluster.
This allows for scaling out using multiple MySQL clients per SQL
@@ -79546,8 +79581,8 @@
<message>
<para>
- Fixed reduced subquery processing in <literal>ORDER
- BY</literal>/<literal>GROUP BY</literal> clauses.
+ Fixed reduced subquery processing in <literal>ORDER BY</literal>
+ and <literal>GROUP BY</literal> clauses.
</para>
</message>
@@ -79557,7 +79592,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<manual type="ndb_mgm_listen_event"/>
</tags>
@@ -79572,7 +79607,7 @@
<message>
<para>
- (Direct APIs): Invoking the MGM API function
+ Invoking the MGM API function
<literal>ndb_mgm_listen_event()</literal> caused a memory leak.
</para>
@@ -80360,7 +80395,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="diskdata"/>
<manual type="ndbd"/>
<manual type="mysqld"/>
</tags>
@@ -80376,7 +80411,7 @@
<message>
<para>
- (Disk Data): Disk data meta-information that existed in
+ Disk data meta-information that existed in
<command>ndbd</command> might not be visible to
<command>mysqld</command>.
</para>
@@ -81694,7 +81729,7 @@
<message>
<para>
- <literal>LEFT OUTER JOIN</literal> between an empty base table
+ A <literal>LEFT OUTER JOIN</literal> between an empty base table
and a view on an empty base table caused a server crash.
</para>
@@ -81705,6 +81740,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="help"/>
<manual type="ndb_restore"/>
<manual type="print"/>
@@ -81722,8 +81758,8 @@
<para>
The description of the <option>--print</option> option in the
- output from <command>ndb_restore <option>--help</option>
- </command> was incorrect.
+ output from <command>ndb_restore
+ <option>--help</option></command> was incorrect.
</para>
</message>
@@ -85123,7 +85159,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<manual type="ndb_mgm_set_timeout"/>
</tags>
@@ -85138,7 +85174,7 @@
<message>
<para>
- (APIs): The timeout set using the MGM API
+ The timeout set using the MGM API
<literal>ndb_mgm_set_timeout()</literal> function was
incorrectly interpreted as seconds rather than as milliseconds.
</para>
@@ -88807,6 +88843,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="ndb_restore"/>
</tags>
@@ -89018,9 +89055,9 @@
<message>
<para>
- While loading data to the cluster after a version upgrade, the
- data nodes failed due to <literal>ndbrequire</literal> failures
- in <literal>PGMAN</literal>.
+ While loading data to the cluster after a version upgrade, data
+ nodes failed due to <literal>ndbrequire</literal> failures in
+ <literal>PGMAN</literal>.
</para>
</message>
@@ -92454,8 +92491,8 @@
</bugs>
<versions>
+ <version ver="5.0.25"/>
<version ver="5.1.12"/>
- <version ver="5.0.25"/>
</versions>
<message>
@@ -92589,7 +92626,7 @@
<message>
<para>
- <command>ndbd</command> restart could sometimes fail due to
+ <command>ndbd</command> restarts could sometimes fail due to
incorrect memory access.
</para>
@@ -98328,14 +98365,14 @@
</tags>
<bugs>
- <fixes bugid="11623"/>
<fixes bugid="9996"/>
<fixes bugid="10938"/>
+ <fixes bugid="11623"/>
</bugs>
<versions>
+ <version ver="4.1.15"/>
<version ver="5.0.13"/>
- <version ver="4.1.15"/>
</versions>
<message>
@@ -98687,7 +98724,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="diskdata"/>
<manual type="CREATE LOGFILE GROUP"/>
<manual type="ndbd"/>
<manual type="gcc"/>
@@ -98704,8 +98741,8 @@
<message>
<para>
- (Disk Data): On some platforms, <command>ndbd</command> compiled
- with <command>gcc</command> 4 would crash when attempting to run
+ On some platforms, <command>ndbd</command> compiled with
+ <command>gcc</command> 4 would crash when attempting to run
<literal>CREATE LOGFILE GROUP</literal>.
</para>
@@ -99095,6 +99132,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="print_data"/>
<manual type="ndb_restore"/>
</tags>
@@ -99399,6 +99437,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="BackupReportFrequency"/>
<manual type="ndb_restore"/>
@@ -100122,7 +100161,7 @@
<message>
<para>
- Fragment IDs were not being logged correctly, causing
+ Fragment IDs were not logged correctly, causing
<command>ndb_restore_log</command> to fail.
</para>
@@ -101765,6 +101804,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="NULL"/>
<manual type="VARBINARY"/>
<manual type="ndb_restore"/>
@@ -105704,7 +105744,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<manual type="ndb_logevent_get_fd"/>
</tags>
@@ -105713,16 +105753,15 @@
</bugs>
<versions>
+ <version ver="5.0.25"/>
<version ver="5.1.12"/>
- <version ver="5.0.25"/>
</versions>
<message>
<para>
- (Direct APIs): The MGM API function
- <literal>ndb_logevent_get_fd()</literal> was not actually
- implemented.
+ The MGM API function <literal>ndb_logevent_get_fd()</literal>
+ was not implemented.
</para>
</message>
@@ -106102,6 +106141,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="FLOAT"/>
<manual type="ndb_size.pl"/>
</tags>
@@ -108522,9 +108562,9 @@
</bugs>
<versions>
- <version ver="5.1.12"/>
<version ver="4.1.21"/>
<version ver="5.0.23"/>
+ <version ver="5.1.12"/>
</versions>
<message>
@@ -108658,9 +108698,9 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="ndb_mgmd"/>
- <highlight type="cluster"/>
</tags>
<bugs>
@@ -108761,6 +108801,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="transactions"/>
<manual type="mysqld"/>
<manual type="ndb_optimized_node_selection"/>
@@ -108828,8 +108869,8 @@
</bugs>
<versions>
+ <version ver="5.0.50"/>
<version ver="5.1.23"/>
- <version ver="5.0.50"/>
</versions>
<message>
@@ -109432,7 +109473,7 @@
<message>
<para>
- In some cases, a single <command>ndbd</command> node would fail
+ In some cases, a single <command>ndbd</command> node failed
following a system restart.
</para>
@@ -109713,7 +109754,7 @@
<tags>
<highlight type="cluster"/>
- <manual type="ndb_mdmd"/>
+ <manual type="ndb_mgmd"/>
<manual type="config.ini"/>
</tags>
@@ -109729,8 +109770,8 @@
<message>
<para>
- Bad values in <filename>config.ini</filename> caused
- <command>ndb_mdmd</command> to crash.
+ Invalid values in <filename>config.ini</filename> caused
+ <command>ndb_mgmd</command> to crash.
</para>
</message>
@@ -109997,15 +110038,15 @@
</tags>
<versions>
+ <version ver="5.0.21"/>
<version ver="5.1.9"/>
- <version ver="5.0.21"/>
</versions>
<message>
<para>
- A new <option>--nowait-nodes</option> startup option for
- <command>ndbd</command> makes it possible to skip specified
+ Added the <option>--nowait-nodes</option> startup option for
+ <command>ndbd</command>, making it possible to skip specified
nodes without waiting for them to start when starting the
cluster. See
<xref linkend="mysql-cluster-ndbd-command-options"/>.
@@ -111078,6 +111119,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="ndb_extra_logging"/>
</tags>
@@ -115466,8 +115508,8 @@
</bugs>
<versions>
+ <version ver="5.0.30"/>
<version ver="5.0.33"/>
- <version ver="5.0.30"/>
</versions>
<message>
@@ -116204,6 +116246,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="ndb_mgmd"/>
</tags>
@@ -116213,16 +116256,15 @@
</bugs>
<versions>
+ <version ver="5.0.23"/>
<version ver="5.1.12"/>
- <version ver="5.0.23"/>
</versions>
<message>
<para>
- For <command>ndb_mgmd</command>, Valgrind revealed problems that
- were corrected: A memory leak; a dependency on an uninitialized
- variable.
+ For <command>ndb_mgmd</command>, Valgrind revealed problems with
+ a memory leak and a dependency on an uninitialized variable.
</para>
</message>
@@ -116391,15 +116433,15 @@
<versions>
<version ver="4.1.19"/>
+ <version ver="5.0.19"/>
<version ver="5.1.6"/>
- <version ver="5.0.19"/>
</versions>
<message>
<para>
- <command>ndb_delete_all</command> would run out of memory on
- tables containing <literal>BLOB</literal> columns.
+ <command>ndb_delete_all</command> ran out of memory when
+ processing tables containing <literal>BLOB</literal> columns.
</para>
</message>
@@ -117887,8 +117929,8 @@
</tags>
<bugs>
+ <fixes bugid="12045"/>
<fixes bugid="12124"/>
- <fixes bugid="12045"/>
</bugs>
<versions>
@@ -117905,17 +117947,16 @@
<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.
+ -e "<replaceable>node_id</replaceable> STOP"</command>
+ stopped a management process running only on the same
+ system where the command was issued.
</para>
</listitem>
<listitem>
<para>
- <command>ndb_mgm -e "shutdown"</command> failed
- to shut down any management processes at all.
+ <command>ndb_mgm -e "SHUTDOWN"</command> failed to shut
+ down any management processes at all.
</para>
</listitem>
@@ -118511,9 +118552,9 @@
</bugs>
<versions>
+ <version ver="5.0.30"/>
<version ver="5.0.33"/>
<version ver="5.1.12"/>
- <version ver="5.0.30"/>
</versions>
<message>
@@ -118713,8 +118754,9 @@
<para>
Several options have been added for use with
- <command>ndb_restore <option>--print_data</option> </command> to
- facilitate the creation of data dump files.
+ <command>ndb_restore <option>--print_data</option></command> to
+ facilitate the creation of data dump files. See
+ <xref linkend="mysql-cluster-restore"/>, for more information.
</para>
</message>
@@ -119402,8 +119444,6 @@
</logentry>
-<!-- END CLUSTER FIXUPS -->
-
<logentry entrytype="bug">
<tags>
@@ -119426,8 +119466,8 @@
<message>
<para>
- Fixed that <option>--replicate-wild-*-table</option> rules apply
- to <literal>ALTER DATABASE</literal> when the table pattern is
+ <option>--replicate-wild-*-table</option> rules now apply to
+ <literal>ALTER DATABASE</literal> when the table pattern is
<literal>%</literal>, as is the case for <literal>CREATE
DATABASE</literal> and <literal>DROP DATABASE</literal>.
</para>
@@ -119973,6 +120013,8 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
+ <highlight type="packaging"/>
<manual type="ndb_mgm"/>
</tags>
@@ -119981,8 +120023,8 @@
</bugs>
<versions>
+ <version ver="5.0.25"/>
<version ver="5.1.12"/>
- <version ver="5.0.25"/>
</versions>
<message>
@@ -120376,6 +120418,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="ndb-wait-connected"/>
<manual type="mysqld"/>
@@ -120388,8 +120431,8 @@
<message>
<para>
- A new <option>--ndb-wait-connected</option> option has been
- added for <command>mysqld</command>, which causes
+ An <option>--ndb-wait-connected</option> option has been added
+ for <command>mysqld</command>, which causes
<command>mysqld</command> to wait for the specified amount of
time to connect to the cluster before starting to accept MySQL
client connections.
@@ -121050,7 +121093,6 @@
<tags>
<highlight type="cluster"/>
<manual type="cluster"/>
- <manual type="cluster"/>
</tags>
<bugs>
@@ -122966,9 +123008,9 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="mgmd"/>
- <highlight type="cluster"/>
</tags>
<bugs>
@@ -122986,8 +123028,8 @@
<message>
<para>
- In some cases, the cluster managment server could log entries
- multiple times folowing a restart of <command>mgmd</command>.
+ In some cases, the cluster managment server logged entries
+ multiple times following a restart of <command>mgmd</command>.
</para>
</message>
@@ -123793,7 +123835,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterreplication"/>
<manual type="replication"/>
<manual type="cluster"/>
</tags>
@@ -123809,9 +123851,9 @@
<message>
<para>
- (Replication): It was possible for API nodes to begin
- interacting with the cluster subscription manager before they
- were fully connected to the cluster.
+ It was possible for API nodes to begin interacting with the
+ cluster subscription manager before they were fully connected to
+ the cluster.
</para>
</message>
@@ -124855,6 +124897,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -125353,6 +125396,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="print_data"/>
<manual type="mysqldump"/>
<manual type="ndb_restore"/>
@@ -125542,7 +125586,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="diskdata"/>
<manual type="cluster"/>
</tags>
@@ -125557,9 +125601,9 @@
<message>
<para>
- (Disk Data): When loading data into a cluster following a
- version upgrade, the data nodes could forcibly shut down due to
- page and buffer management failures.
+ When loading data into a cluster following a version upgrade,
+ the data nodes could forcibly shut down due to page and buffer
+ management failures.
</para>
</message>
@@ -125952,7 +125996,6 @@
<highlight type="cluster"/>
<manual type="cluster"/>
<manual type="mysqldump"/>
- <manual type="cluster"/>
</tags>
<bugs>
@@ -126813,7 +126856,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<manual type="cluster"/>
<manual type="Ndb_cluster_connection"/>
</tags>
@@ -126823,17 +126866,16 @@
</bugs>
<versions>
- <version ver="5.1.15"/>
<version ver="5.0.36"/>
<version ver="5.0.37"/>
+ <version ver="5.1.15"/>
</versions>
<message>
<para>
- (Cluster APIs): Deletion of an
- <literal>Ndb_cluster_connection</literal> object took a very
- long time.
+ Deletion of an <literal>Ndb_cluster_connection</literal> object
+ took a very long time.
</para>
</message>
@@ -127029,13 +127071,10 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="ndbd"/>
- <manual type="AAA"/>
- <manual type="aAa"/>
<manual type="latin_ci"/>
- <manual type="cluster"/>
- <highlight type="cluster"/>
</tags>
<bugs>
@@ -127049,12 +127088,13 @@
<message>
<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
+ Updating a column of one of the <literal>TEXT</literal> types
+ during a cluster backup could cause the <command>ndbd</command>
+ process to crash, due to the incorrect use of charset-normalized
+ reads. This could also lead to character data having the wrong
+ lettercase 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>
@@ -127066,6 +127106,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="ndb-wait-connected"/>
<manual type="mysqld"/>
@@ -127078,11 +127119,11 @@
<message>
<para>
- A new option <option>--ndb-wait-connected</option> has been
- added for <command>mysqld</command>. It causes
+ An <option>--ndb-wait-connected</option> option has been added
+ for <command>mysqld</command>. It causes
<command>mysqld</command> wait a specified amount of time to be
- connected to the cluster before starting to accept client
- connections. See
+ connected to the cluster before accepting client connections.
+ See
<link linkend="option_mysqld_ndb_wait_connected">here</link>,
for more information.
</para>
@@ -127231,7 +127272,8 @@
<logentry entrytype="feature">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterreplication"/>
+ <highlight type="incompatiblechange"/>
<manual type="replication"/>
<manual type="cluster"/>
</tags>
@@ -127243,12 +127285,11 @@
<message>
<para>
- (Replication)/<emphasis role="bold">Incompatible
- Change</emphasis>: The definition of the
- <literal>mysql.ndb_apply_status</literal> table has changed such
- that an online upgrade is not possible from MySQL 5.1.17 or
- earlier for a replication slave cluster; you must shut down all
- SQL nodes as part of the upgrade procedure. See
+ The definition of the <literal>mysql.ndb_apply_status</literal>
+ table has changed such that an online upgrade is not possible
+ from MySQL 5.1.17 or earlier for a replication slave cluster;
+ you must shut down all SQL nodes as part of the upgrade
+ procedure. See
<xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>
before upgrading for details.
</para>
@@ -127403,7 +127444,7 @@
<para>
<command>ndb_mgmd</command> failed silently when the cluster
- configuration file contained invalid <literal>[TCP]</literal>
+ configuration file contained invalid <literal>[tcp]</literal>
entries.
</para>
@@ -127737,6 +127778,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -128661,10 +128703,9 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="ndb_autodiscover"/>
- <manual type="cluster"/>
- <highlight type="cluster"/>
</tags>
<bugs>
@@ -128672,8 +128713,8 @@
</bugs>
<versions>
+ <version ver="5.0.19"/>
<version ver="5.1.6"/>
- <version ver="5.0.19"/>
</versions>
<message>
@@ -128758,14 +128799,12 @@
</logentry>
- <logentry entrytype="feature">
+ <logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="perror"/>
- <manual type="cluster"/>
- <manual type="cluster"/>
- <highlight type="cluster"/>
</tags>
<bugs>
@@ -128781,9 +128820,10 @@
<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.
+ <literal>MySQL-Server</literal> RPM did not provide support for
+ the <option>--ndb</option> option. It now supports this option,
+ and so can be used to obtain error message text for MySQL
+ Cluster error codes.
</para>
</message>
@@ -128826,7 +128866,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="diskdata"/>
<manual type="cluster"/>
<manual type="CREATE LOGFILE GROUP"/>
<manual type="UNDO BUFFER SIZE"/>
@@ -128843,9 +128883,9 @@
<message>
<para>
- (Disk Data): Setting the value of the <literal>UNDO BUFFER
- SIZE</literal> to 64K or less in a <literal>CREATE LOGFILE
- GROUP</literal> statement led to failure of cluster data nodes.
+ Setting the value of the <literal>UNDO BUFFER SIZE</literal> to
+ 64K or less in a <literal>CREATE LOGFILE GROUP</literal>
+ statement led to failure of cluster data nodes.
</para>
</message>
@@ -129424,6 +129464,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -129434,8 +129475,8 @@
<message>
<para>
- A new <literal>REPORT BackupStatus</literal> command has been
- added in the cluster management client which allows you to
+ A <literal>REPORT BackupStatus</literal> command has been added
+ in the cluster management client. This command allows you to
obtain a backup status report at any time during a backup. For
more about this command, see
<xref linkend="mysql-cluster-mgm-client-commands"/>.
@@ -130018,7 +130059,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterreplication"/>
<manual type="BLOB"/>
<manual type="replication"/>
<manual type="cluster"/>
@@ -130036,10 +130077,10 @@
<message>
<para>
- (Replication): When taking part in Cluster replication of tables
- containing <literal>BLOB</literal> columns,
- <command>mysqld</command> falsely reported a large memory leak
- in the replication buffers when there was none.
+ When taking part in Cluster replication of tables containing
+ <literal>BLOB</literal> columns, <command>mysqld</command>
+ falsely reported a large memory leak in the replication buffers
+ when there was none.
</para>
</message>
@@ -130067,9 +130108,10 @@
<para>
Truncating a table on one <command>mysqld</command> caused other
- <command>mysqld</command> processes in the cluster to return
- <errortext>ERROR 1412 (HY000): Table definition has changed,
- please retry transaction</errortext> on subsequent queries.
+ <command>mysqld</command> processes connected to the cluster to
+ return <errortext>ERROR 1412 (HY000): Table definition has
+ changed, please retry transaction</errortext> on subsequent
+ queries.
</para>
</message>
@@ -130125,8 +130167,8 @@
<para>
When using the <literal>NdbTransaction::execute()</literal>
method, a very long timeout (greater than 5 minutes) could
- result if the last data node being polled was disconnected from
- the cluster.
+ result if the last data node polled was disconnected from the
+ cluster.
</para>
</message>
@@ -130513,9 +130555,8 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
- <manual type="cluster"/>
- <highlight type="cluster"/>
</tags>
<bugs>
@@ -130529,8 +130570,8 @@
<message>
<para>
- The server left core files following shutdown if data nodes had
- failed.
+ The MySQL Server left core files following shutdown if data
+ nodes had failed.
</para>
</message>
@@ -130651,7 +130692,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<manual type="BLOB"/>
<manual type="LM_Read"/>
<manual type="cluster"/>
@@ -130671,10 +130712,10 @@
<message>
<para>
- (APIs): For <literal>BLOB</literal> reads on operations with
- lock mode <literal>LM_CommittedRead</literal>, the lock mode was
- not upgraded to <literal>LM_Read</literal> before the state of
- the <literal>BLOB</literal> had already been calculated. The
+ For <literal>BLOB</literal> reads on operations with lock mode
+ <literal>LM_CommittedRead</literal>, the lock mode was not
+ upgraded to <literal>LM_Read</literal> before the state of the
+ <literal>BLOB</literal> had already been calculated. The
<literal>NDB</literal> API methods affected by this problem
included the following:
<itemizedlist>
@@ -130936,7 +130977,7 @@
<para>
For <literal>InnoDB</literal> tables, the server could crash
- when executing <literal>NOT IN ()</literal> subqueries.
+ when executing <literal>NOT IN(...)</literal> subqueries.
</para>
</message>
@@ -130964,8 +131005,8 @@
<para>
In a cluster with more than 2 replicas, a manual restart of one
- of the data nodes could fail and cause the other nodes in its
- nodegroup to shut down.
+ of the data nodes could fail and cause the other nodes in the
+ same node group to shut down.
</para>
</message>
@@ -130998,6 +131039,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="ndb_size.pl"/>
</tags>
@@ -131457,8 +131499,6 @@
<highlight type="cluster"/>
<manual type="cluster"/>
<manual type="ndb-connectstring"/>
- <manual type="cluster"/>
- <manual type="cluster"/>
<manual type="mysqld"/>
</tags>
@@ -131948,8 +131988,8 @@
</bugs>
<versions>
+ <version ver="5.0.32"/>
<version ver="5.0.33"/>
- <version ver="5.0.32"/>
<version ver="5.1.14"/>
</versions>
@@ -131958,10 +131998,15 @@
<para>
It is now possible to create a unique hashed index on a column
that is not defined as <literal>NOT NULL</literal>.
- <emphasis>Note that this change applies only to tables using the
- <literal>NDB</literal> storage engine</emphasis>.
</para>
+ <note>
+ <para>
+ This change applies only to tables using the
+ <literal>NDB</literal> storage engine.
+ </para>
+ </note>
+
<para>
Unique indexes on columns in <literal>NDB</literal> tables do
not store null values because they are mapped to primary keys in
@@ -131989,9 +132034,9 @@
</para>
<para>
- Note that a warning is returned if one creates a unique nullable
- hash index, since the query optimizer should be provided a hint
- not to use it with <literal>NULL</literal> values if this can be
+ A warning is returned if one creates a unique nullable hash
+ index, since the query optimizer should be provided a hint not
+ to use it with <literal>NULL</literal> values if this can be
avoided.
</para>
@@ -132019,7 +132064,7 @@
<para>
<literal>SHOW ENGINE NDB STATUS</literal> could sometimes return
an incorrect value of <literal>0</literal> for the latest epoch,
- which could cause problems with synchronising the binlog.
+ which could cause problems with synchronizing the binlog.
</para>
</message>
@@ -132622,10 +132667,9 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="ndb_mgmd"/>
- <manual type="cluster"/>
- <highlight type="cluster"/>
</tags>
<bugs>
@@ -132639,12 +132683,12 @@
<message>
<para>
- <command>ndb_mgmd</command> would allow a node to be stopped or
+ <command>ndb_mgmd</command> allowed 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.
+ the cluster management client should issue an error when such an
+ attempt is made.
</para>
</message>
@@ -133337,9 +133381,9 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="diskdata"/>
<manual type="cluster"/>
<manual type="ADD UNDOFILE"/>
- <manual type="cluster"/>
</tags>
<bugs>
@@ -133353,9 +133397,8 @@
<message>
<para>
- <literal>NDBCluster</literal> (Disk Data): The error message
- generated by a failed <literal>ADD UNDOFILE</literal> did not
- provide any reasons for the failure.
+ The error message generated by a failed <literal>ADD
+ UNDOFILE</literal> did not provide any reasons for the failure.
</para>
</message>
@@ -133620,7 +133663,7 @@
<para>
When attempting to restart the cluster following a data import,
- the cluster would fail during Phase 4 of the restart with
+ the cluster failed during Phase 4 of the restart with
<errortext>Error 2334: Job buffer congestion</errortext>.
</para>
@@ -133694,14 +133737,14 @@
</bugs>
<versions>
+ <version ver="5.0.23"/>
<version ver="5.1.12"/>
- <version ver="5.0.23"/>
</versions>
<message>
<para>
- Cluster system status variables were not updated.
+ Cluster system status variables were not updated properly.
</para>
</message>
@@ -133711,15 +133754,13 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
- <manual type="data_length"/>
<manual type="TABLES"/>
<manual type="INFORMATION_SCHEMA"/>
<manual type="Data_length"/>
<manual type="Avg_row_length"/>
<manual type="SHOW TABLE STATUS"/>
- <manual type="cluster"/>
- <highlight type="cluster"/>
</tags>
<bugs>
@@ -133733,7 +133774,7 @@
<message>
<para>
- The average row size for Cluster tables was being calculated
+ The average row size for Cluster tables was calculated
incorrectly. This affected the values shown for the
<literal>Data_length</literal> and
<literal>Avg_row_length</literal> columns in the output
@@ -133742,10 +133783,14 @@
<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).
+ Cluster tables.
</para>
+ <para>
+ Tables using storage engines other than <literal>NDB</literal>
+ were not affected by this bug.
+ </para>
+
</message>
</logentry>
@@ -133999,7 +134044,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterreplication"/>
<manual type="replication"/>
<manual type="cluster"/>
</tags>
@@ -134015,9 +134060,9 @@
<message>
<para>
- (Replication): Connecting an API node to the cluster during a
- node restart while performing database operations could cause
- the restarting node to fail.
+ Connecting an API node to the cluster during a node restart
+ while performing database operations could cause the restarting
+ node to fail.
</para>
</message>
@@ -134190,7 +134235,7 @@
<para>
A memory leak occurred when performing ordered index scans using
- indexes a columns larger than 32 bytes, which would eventually
+ indexes on columns larger than 32 bytes. This would eventually
lead to the forced shutdown of all <command>mysqld</command>
server processes used with the cluster.
</para>
@@ -135026,9 +135071,10 @@
</logentry>
- <logentry entrytype="feature">
+ <logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -135044,8 +135090,9 @@
<message>
<para>
- The output of <literal>perror --help</literal> now displays the
- <option>--ndb</option> option.
+ The output of <command>perror <option>--help</option></command>
+ did not display any information about the <option>--ndb</option>
+ option.
</para>
</message>
@@ -135830,7 +135877,7 @@
<message>
<para>
- It is now possible to restore a Cluster backup between
+ It is now possible to restore a MySQL Cluster backup between
big-endian and little-endian machines.
</para>
@@ -135962,6 +136009,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="MemReportFrequency"/>
</tags>
@@ -135973,9 +136021,9 @@
<message>
<para>
- Support was added for a new
- <literal>MemReportFrequency</literal> configuration parameter
- that provides for periodic reports of memory usage. See
+ Support was added for the <literal>MemReportFrequency</literal>
+ configuration parameter, which provides for periodic reports of
+ memory usage. See
<xref linkend="mysql-cluster-config-params-mgm"/>, for
information about using this parameter.
</para>
@@ -137026,6 +137074,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -137041,8 +137090,8 @@
<message>
<para>
- <literal>NDB</literal>: Attempting to create or drop tables
- during a backup would cause the cluster to shut down.
+ Attempting to create or drop tables during a backup would cause
+ the cluster to shut down.
</para>
</message>
@@ -137440,6 +137489,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="with-ndb-ccflags"/>
</tags>
@@ -137506,16 +137556,16 @@
</bugs>
<versions>
+ <version ver="5.0.23"/>
<version ver="5.1.12"/>
- <version ver="5.0.23"/>
</versions>
<message>
<para>
- Restoring a backup made using <command>ndb_restore</command>
- failed when the backup had been taken from a cluster whose data
- memory was full.
+ Restoring a backup with <command>ndb_restore</command> failed
+ when the backup had been taken from a cluster whose
+ <literal>DataMemory</literal> had been completely used up.
</para>
</message>
@@ -137590,9 +137640,9 @@
<message>
<para>
- When a disk full condition occurred, <command>ndbd</command>
- exited without printing a message about the condition to the
- error log. Now the message is written.
+ When a <errortext>Disk is full</errortext> condition occurred,
+ <command>ndbd</command> exited without reporting this condition
+ in the error log.
</para>
</message>
@@ -137651,11 +137701,11 @@
<message>
<para>
- / A delete and a read peformed in the same operation could cause
- one or more of the cluster's data nodes to crash. This could
- occur when the operation affected more than 5 columns
- concurrently, or when one or more of the columns was of the
- VARCHAR type and was stored on disk.
+ A delete and a read performed in the same operation could cause
+ one or more data nodes to crash. This could occur when the
+ operation affected more than 5 columns concurrently, or when one
+ or more of the columns was of the <literal>VARCHAR</literal>
+ type and was stored on disk.
</para>
</message>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8564 - trunk/dynamic-docs/changelog | jon | 7 Nov |
