Author: jstephens
Date: 2007-11-06 15:46:49 +0100 (Tue, 06 Nov 2007)
New Revision: 8553
Log:
More fixups of Cluster changelog items.
Modified:
trunk/dynamic-docs/changelog/mysqld.xml
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2007-11-06 14:01:29 UTC (rev 8552)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2007-11-06 14:46:49 UTC (rev 8553)
Changed blocks: 108, Lines Added: 186, Lines Deleted: 142; 31488 bytes
@@ -39099,8 +39099,6 @@
</logentry>
-<!-- END CLUSTER CLEANUPS -->
-
<logentry entrytype="feature">
<tags>
@@ -40473,7 +40471,7 @@
<message>
<para>
- Backup messages are no longer printed to the Cluster log.
+ Backup messages are no longer printed to the cluster log.
</para>
</message>
@@ -41057,6 +41055,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="TransactionBufferMemory"/>
<manual type="transactions"/>
@@ -41091,6 +41090,7 @@
<tags>
<highlight type="cluster"/>
+ <highlight type="clusterreplication"/>
<manual type="replication"/>
<manual type="cluster"/>
</tags>
@@ -41298,6 +41298,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -41879,6 +41880,7 @@
<tags>
<highlight type="cluster"/>
+ <highlight type="incompatiblechange"/>
<manual type="cluster"/>
<manual type="false"/>
<manual type="true"/>
@@ -42636,7 +42638,6 @@
<highlight type="cluster"/>
<manual type="cluster"/>
<manual type="ALL START"/>
- <manual type="cluster"/>
</tags>
<bugs>
@@ -43802,6 +43803,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="clusterapi"/>
<manual type="cluster"/>
</tags>
@@ -43812,7 +43814,7 @@
<message>
<para>
- an <literal>Ndb</literal> object in the NDB API was initialized
+ An <literal>Ndb</literal> object in the NDB API was initialized
with insufficient parallellism
</para>
@@ -43823,6 +43825,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -44035,6 +44038,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="mysqldump"/>
<manual type="partitioning"/>
<manual type="cluster"/>
@@ -44971,15 +44975,21 @@
<message>
<para>
- <literal>VARCHAR</literal> columns now remember end space. A
- <literal>VARCHAR()</literal> column can now contain up to 65535
- bytes. For more details, see <xref linkend="news-5-0-x"/>. If
- the table handler doesn't support the new
- <literal>VARCHAR</literal> type, then it's converted to a
- <literal>CHAR</literal> column. Currently this happens for
- <literal>NDB</literal> tables.
+ A <literal>VARCHAR</literal> column can now contain up to 65535
+ bytes. In addition, <literal>VARCHAR</literal> columns now
+ remember trailing spaces. For more details, see
+ <xref linkend="news-5-0-x"/>.
</para>
+ <note>
+ <para>
+ If the table handler does not support the new
+ <literal>VARCHAR</literal> type, then it is converted to a
+ <literal>CHAR</literal> column. Currently this happens for
+ <literal>NDB</literal> tables.
+ </para>
+ </note>
+
</message>
</logentry>
@@ -45193,6 +45203,8 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
+ <manual type="cluster"/>
<manual type="SHOW"/>
<manual type="START BACKUP"/>
</tags>
@@ -45209,8 +45221,9 @@
<message>
<para>
- The NDB <literal>START BACKUP</literal> command could be
- interrupted by a <literal>SHOW</literal> command.
+ The cluster management client <literal>START BACKUP</literal>
+ command could be interrupted by a <literal>SHOW</literal>
+ command.
</para>
</message>
@@ -45225,7 +45238,6 @@
<manual type="InnoDB"/>
<manual type="stored procedure"/>
<manual type="AUTO_INCREMENT"/>
- <manual type="cluster"/>
<manual type="TRUNCATE"/>
</tags>
@@ -45251,10 +45263,11 @@
<note>
<para>
This bug did not affect <literal>InnoDB</literal> tables.
- Also, <literal>TRUNCATE</literal> does not reset the
+ </para>
+ <para>
+ In addition, <literal>TRUNCATE</literal> does not reset the
<literal>AUTO_INCREMENT</literal> counter for
- <literal>NDBCluster</literal> tables regardless of when it is
- called.
+ <literal>NDB</literal> tables regardless of when it is called.
</para>
</note>
@@ -45378,6 +45391,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="AUTO_INCREMENT"/>
<manual type="SHOW TABLE STATUS"/>
@@ -45464,6 +45478,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="BLOB"/>
<manual type="CREATE"/>
<manual type="DROP"/>
@@ -45520,6 +45535,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="replication"/>
<manual type="cluster"/>
</tags>
@@ -46361,7 +46377,7 @@
<para>
Under certain circumstances, when <command>mysqld</command>
- connects to a cluster management server, the connection would
+ connected to a cluster management server, the connection would
fail before a node ID could be allocated.
</para>
@@ -47052,10 +47068,11 @@
<para>
Performing multiple <literal>ALTER TABLE</literal> operations on
- the same NDB table from different <command>mysqld</command>
- processes in the same cluster led to schema versioning errors
- when trying to access the table again following the restart of
- one of the <command>mysqld</command> processes.
+ the same <literal>NDB</literal> table from different
+ <command>mysqld</command> processes in the same cluster led to
+ schema versioning errors when trying to access the table again
+ following the restart of one of the <command>mysqld</command>
+ processes.
</para>
</message>
@@ -47381,6 +47398,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="MaxNoOfOpenFiles"/>
<manual type="InitialNoOpenFiles"/>
@@ -47413,6 +47431,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="LockPagesInMemory"/>
</tags>
@@ -47493,7 +47512,6 @@
<tags>
<manual type="cluster"/>
- <manual type="cluster"/>
<highlight type="clusterapi"/>
</tags>
@@ -47512,8 +47530,8 @@
<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.
+ scan did not terminate. This caused incomplete error handling
+ for the failed node.
</para>
</message>
@@ -47523,6 +47541,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="COLUMN_FORMAT"/>
<manual type="STORAGE"/>
<manual type="cluster"/>
@@ -49224,6 +49243,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="ndb_mgmd"/>
<manual type="P"/>
@@ -49238,11 +49258,10 @@
<message>
<para>
- <literal>MySQL Cluster</literal>: A new <option>-P</option>
- option is available for use with the <command>ndb_mgmd</command>
- client. When called with this option,
- <command>ndb_mgmd</command> prints all configuration data to
- <literal>stdout</literal>, then exits.
+ A new <option>-P</option> option is available for use with the
+ <command>ndb_mgmd</command> client. When called with this
+ option, <command>ndb_mgmd</command> prints all configuration
+ data to <literal>stdout</literal>, then exits.
</para>
</message>
@@ -49252,6 +49271,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="diskdata"/>
<manual type="cluster"/>
<manual type="ndbd"/>
<manual type="DROP LOGFILE GROUP"/>
@@ -49269,10 +49289,9 @@
<message>
<para>
- <literal>NDBCluster</literal> (Disk Data): <literal>DROP LOGFILE
- GROUP</literal> corrupted the cluster file system and caused
- <command>ndbd</command> to fail when running more than one node
- on the same system.
+ <literal>DROP LOGFILE GROUP</literal> corrupted the cluster file
+ system and caused <command>ndbd</command> to fail when running
+ more than one node on the same system.
</para>
</message>
@@ -49329,7 +49348,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<manual type="cluster"/>
</tags>
@@ -49344,10 +49363,10 @@
<message>
<para>
- (Direct APIs): The <filename>storage/ndb</filename> directory
- was missing from the server binary distribution, making it
- impossible to compile <literal>NDB</literal> API and MGM API
- applications. This directory can be found as
+ The <filename>storage/ndb</filename> directory was missing from
+ the server binary distribution, making it impossible to compile
+ <literal>NDB</literal> API and MGM API applications. This
+ directory can be found as
<filename>/usr/include/storage/ndb</filename> after installing
that distribution.
</para>
@@ -50061,10 +50080,10 @@
<message>
<para>
- Under some circumstances, following the restart of a management,
- all cluster data nodes would connect to it normally, but some of
- them subsequently failed to log any events to the management
- node.
+ Under some circumstances, following the restart of a management
+ node, all cluster data nodes would connect to it normally, but
+ some of them subsequently failed to log any events to the
+ management node.
</para>
</message>
@@ -50225,7 +50244,7 @@
<para>
An invalid subselect on an <literal>NDB</literal> table could
- cause mysqld to crash.
+ cause <command>mysqld</command> to crash.
</para>
</message>
@@ -50479,10 +50498,9 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterreplication"/>
<manual type="replication"/>
<manual type="cluster"/>
- <manual type="cluster"/>
<manual type="character sets"/>
<manual type="mysqld"/>
</tags>
@@ -50498,10 +50516,10 @@
<message>
<para>
- (Replication): <command>mysqld</command> would segfault on
- startup when the <literal>NDB</literal> storage engine was
- enabled and the default character set was a strictly multi-byte
- character set such as UCS2.
+ <command>mysqld</command> would segfault on startup when the
+ <literal>NDB</literal> storage engine was enabled and the
+ default character set was a strictly multi-byte character set
+ such as UCS2.
</para>
<para>
@@ -50615,7 +50633,6 @@
<tags>
<highlight type="cluster"/>
<manual type="cluster"/>
- <manual type="cluster"/>
<manual type="mysqld"/>
</tags>
@@ -50645,11 +50662,10 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="triggers"/>
<manual type="AUTO_INCREMENT"/>
- <manual type="cluster"/>
- <highlight type="cluster"/>
</tags>
<bugs>
@@ -50815,6 +50831,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="diskdata"/>
<manual type="cluster"/>
<manual type="ACC"/>
</tags>
@@ -51420,7 +51437,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterreplication"/>
<manual type="replication"/>
<manual type="cluster"/>
<manual type="mysqld"/>
@@ -51437,10 +51454,10 @@
<message>
<para>
- (Replication): One or more of the <command>mysqld</command>
- processes could fail when subjecting a Cluster replication setup
- with multiple <command>mysqld</command> processes on both the
- master and slave clusters to high loads.
+ One or more of the <command>mysqld</command> processes could
+ fail when subjecting a Cluster replication setup with multiple
+ <command>mysqld</command> processes on both the master and slave
+ clusters to high loads.
</para>
</message>
@@ -51475,7 +51492,7 @@
<logentry entrytype="feature">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<highlight type="incompatiblechange"/>
<manual type="cluster"/>
<manual type="AbortOption"/>
@@ -51490,9 +51507,9 @@
<message>
<para>
- (Cluster APIs) / The <literal>AbortOption</literal> type is now
- a member of the <literal>NdbOperation</literal> class; its
- values and behavior have also changed.
+ The <literal>AbortOption</literal> type is now a member of the
+ <literal>NdbOperation</literal> class; its values and behavior
+ have also changed.
<literal>NdbTransaction::AbortOption</literal> can no longer be
used, and applications written against the NDB API may need to
be rewritten and recompiled to accomodate these changes. For
@@ -52153,7 +52170,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="diskdata"/>
<manual type="cluster"/>
</tags>
@@ -52168,9 +52185,9 @@
<message>
<para>
- (Disk Data): When in single user mode, it was possible to create
- log file groups and tablespaces from any SQL node connected to
- the cluster.
+ When in single user mode, it was possible to create log file
+ groups and tablespaces from any SQL node connected to the
+ cluster.
</para>
</message>
@@ -52702,7 +52719,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<manual type="cluster"/>
<manual type="ndb_mgm_check_connection"/>
</tags>
@@ -52714,7 +52731,7 @@
<message>
<para>
- (Cluster APIs): You can now use the
+ You can now use the
<literal>ndb_mgm_check_connection()</literal> function to
determine whether a management server is running. See
<xref linkend="ndb-mgm-check-connection"/>.
@@ -54090,10 +54107,9 @@
<message>
<para>
- Queries on <literal>NDB</literal> tables that are executed using
- <literal>index_merge</literal>/union or
- <literal>index_merge</literal>/intersection could produce
- incorrect results.
+ Queries on <literal>NDB</literal> tables that were executed
+ using <literal>index_merge</literal> could produce incorrect
+ results.
</para>
</message>
@@ -56096,6 +56112,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="replication"/>
<manual type="WHERE"/>
<manual type="statement-based logging"/>
@@ -57637,7 +57654,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterreplication"/>
<manual type="cluster"/>
<manual type="replication"/>
<manual type="partitioning"/>
@@ -58794,6 +58811,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -58809,9 +58827,9 @@
<message>
<para>
- NDB Cluster returned incorrect <literal>Can't find
- file</literal> error for OS error 24, changed to <literal>Too
- many open files</literal>.
+ <literal>NDB</literal> returned an incorrect <errortext>Can't
+ find file error</errortext> for OS error 24; this has been
+ changed to <errortext>Too many open files</errortext>.
</para>
</message>
@@ -59110,6 +59128,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="mysql-test-run.pl"/>
</tags>
@@ -59127,7 +59146,7 @@
<para>
<command>mysql-test-run.pl</command> started
- <literal>NDB</literal> even for test cases that didn't need it.
+ <literal>NDB</literal> even for test cases that did not need it.
</para>
</message>
@@ -59844,6 +59863,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -59858,8 +59878,9 @@
<message>
<para>
- NDB Cluster leaked disk space when performing INSERTS/DELETES in
- a loop.
+ <literal>NDB</literal> leaked disk space when performing
+ repeated <literal>INSERT</literal> or <literal>DELETE</literal>
+ statements.
</para>
</message>
@@ -60089,6 +60110,7 @@
<tags>
<highlight type="cluster"/>
+ <highlight type="importantchange"/>
<manual type="KEY"/>
<manual type="cluster"/>
<manual type="partitioning"/>
@@ -61691,7 +61713,7 @@
<para>
Trying to import too many dumped tables requiring resources
- beyond those allocated in the cluster configuration would cause
+ beyond those allocated in the cluster configuration file caused
the server to crash instead of reporting an insufficient
resources error.
</para>
@@ -62178,7 +62200,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="diskdata"/>
<manual type="cluster"/>
</tags>
@@ -62193,7 +62215,7 @@
<message>
<para>
- (Disk Data): <literal>CREATE TABLE ... LIKE
+ <literal>CREATE TABLE ... LIKE
<replaceable>disk_data_table</replaceable> </literal> created an
in-memory <literal>NDB</literal> table.
</para>
@@ -62866,6 +62888,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="diskdata"/>
<manual type="cluster"/>
</tags>
@@ -62880,8 +62903,8 @@
<message>
<para>
- NDB Cluster returned wrong error when tablespace on disk was
- full.
+ <literal>NDB</literal> returned the wrong error when the
+ tablespace on disk was full.
</para>
</message>
@@ -63221,8 +63244,9 @@
<message>
<para>
- A table insert or update of more than 128 bytes of data in a
- 4-replica Cluster could cause a node to crash.
+ An <literal>INSERT</literal> or <literal>UPDATE</literal> of
+ more than 128 bytes of data in a 4-replica cluster could cause
+ data nodes to crash.
</para>
</message>
@@ -63457,7 +63481,7 @@
<para>
The failure of a data node when preparing to commit a
- transaction (that is, while the node's status was
+ transaction (that is, while the node's status was
<literal>CS_PREPARE_TO_COMMIT</literal>) could cause the failure
of other cluster data nodes.
</para>
@@ -63564,8 +63588,8 @@
<message>
<para>
- Multiple <command>ndb_mgmd</command> processes in a cluster
- would not know each other's IP addresses.
+ Multiple <command>ndb_mgmd</command> processes in a cluster did
+ not know each other's IP addresses.
</para>
</message>
@@ -64416,8 +64440,8 @@
<message>
<para>
- On 64-bit Solaris 9, the cluster would time out and crash after
- the first query was made.
+ On 64-bit Solaris 9, the cluster timed out and crashed after the
+ first query was made.
</para>
</message>
@@ -64579,6 +64603,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="SHOW TABLES"/>
<manual type="INFORMATION_SCHEMA"/>
@@ -64847,6 +64872,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -66522,6 +66548,7 @@
<tags>
<highlight type="cluster"/>
+ <highlight type="incompatiblechange"/>
<manual type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -67386,7 +67413,6 @@
<highlight type="cluster"/>
<manual type="cluster"/>
<manual type="SHOW TABLES"/>
- <manual type="cluster"/>
</tags>
<bugs>
@@ -67394,9 +67420,8 @@
</bugs>
<versions>
- <version ver="5.0.33"/>
+ <version ver="4.1.22"/>
<version ver="5.0.30"/>
- <version ver="4.1.22"/>
</versions>
<message>
@@ -67435,8 +67460,8 @@
<para>
Data nodes added while the cluster was running in single user
mode were all assigned node ID 0, which could later cause
- multiple node failures. Adding of nodes in single user mode is
- no longer possible.
+ multiple node failures. Adding nodes while in single user mode
+ is no longer possible.
</para>
</message>
@@ -67858,6 +67883,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -67987,8 +68013,9 @@
<para>
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.
+ <literal>DROP TABLE</literal> operation were not actually made
+ available again until after the cluster had performed a local
+ checkpoint.
</para>
</message>
@@ -68551,7 +68578,8 @@
<message>
<para>
- Fixed aggregate function in prepared statements.
+ Aggregate functions could lead to server crashes when used in
+ prepared statements.
</para>
</message>
@@ -68586,6 +68614,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="BLOB"/>
<manual type="TEXT"/>
<manual type="cluster"/>
@@ -68695,7 +68724,7 @@
An attempt to perform a <literal>SELECT ... FROM
INFORMATION_SCHEMA.TABLES</literal> whose result included
information about <literal>NDB</literal> tables for which the
- user had no privileges could crash the MySQL Server on which the
+ user had no privileges crashed the MySQL Server on which the
query was performed.
</para>
@@ -68706,7 +68735,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="diskdata"/>
<manual type="cluster"/>
</tags>
@@ -68721,8 +68750,8 @@
<message>
<para>
- (Disk Data): Creating multiple Disk Data tables using different
- tablespaces could sometimes cause the cluster to fail.
+ Creating multiple Disk Data tables using different tablespaces
+ could sometimes cause the cluster to fail.
</para>
</message>
@@ -68793,6 +68822,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="InnoDB"/>
<manual type="cluster"/>
<manual type="triggers"/>
@@ -69105,8 +69135,11 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
+ <highlight type="importantchange"/>
<manual type="LOAD DATA INFILE"/>
<manual type="cluster"/>
+ <manual type="commit"/>
</tags>
<bugs>
@@ -69290,6 +69323,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="perror"/>
</tags>
@@ -69934,8 +69968,8 @@
<message>
<para>
- A vague error message was returned when reading of both schema
- files occurred during a restart of the cluster.
+ A vague error message was returned when reading both schema
+ files during a restart of the cluster.
</para>
</message>
@@ -70365,7 +70399,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterreplication"/>
<manual type="replication"/>
<manual type="cluster"/>
<manual type="binary log"/>
@@ -70383,8 +70417,8 @@
<message>
<para>
- (Replication): Setting <literal>SQL_LOG_BIN</literal> to zero
- did not disable binary logging.
+ Setting <literal>SQL_LOG_BIN</literal> to zero did not disable
+ binary logging.
</para>
<para>
@@ -70431,6 +70465,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="clusterreplication"/>
<manual type="TimeBetweenEpochsTimeout"/>
<manual type="cluster"/>
</tags>
@@ -70979,9 +71014,8 @@
<logentry entrytype="feature">
<tags>
- <manual type="cluster"/>
+ <highlight type="cluster"/>
<manual type="CREATE TABLE"/>
- <manual type="cluster"/>
</tags>
<bugs>
@@ -70995,7 +71029,7 @@
<message>
<para>
- The <literal>NDBCluster</literal> storage engine now supports
+ The <literal>NDB</literal> storage engine now supports
<literal>CREATE TABLE</literal> statements of arbitrary length.
(Previously, <literal>CREATE TABLE</literal> statements for
MySQL Cluster tables could contain a maximum of 4096 characters
@@ -72268,6 +72302,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="transactions"/>
<manual type="DUMP"/>
@@ -72282,14 +72317,9 @@
<para>
New cluster management client <literal>DUMP</literal> commands
were added to aid in tracking transactions, scan operations, and
- locks. See <xref linkend="ndb-internals-dump-command-2350"/>
- <remark role="TODO">
- [js] Uncomment when DUMP 2352 is documented.
- </remark>
-<!--,
- <xref linkend="ndb-internals-dump-command-2352"/>,
--->
- and <xref linkend="ndb-internals-dump-command-2550"/>.
+ locks. See <xref linkend="ndb-internals-dump-command-2350"/>,
+ <xref linkend="ndb-internals-dump-command-2352"/>, and
+ <xref linkend="ndb-internals-dump-command-2550"/>.
</para>
</message>
@@ -72966,7 +72996,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterreplication"/>
<manual type="cluster"/>
</tags>
@@ -73617,7 +73647,8 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
+ <highlight type="clusterreplication"/>
<manual type="cluster"/>
<manual type="VARCHAR"/>
</tags>
@@ -73633,12 +73664,11 @@
<message>
<para>
- (Cluster APIs / Disk Data): 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 <literal>VARCHAR</literal> type and was
- stored on disk.
+ A delete and a read peformed as part of 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
+ <literal>VARCHAR</literal> type and was stored on disk.
</para>
</message>
@@ -74000,11 +74030,11 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="transactions"/>
<manual type="NoOfTransactions"/>
<manual type="ndb_restore"/>
- <highlight type="cluster"/>
</tags>
<bugs>
@@ -74203,6 +74233,14 @@
table would cause the server to crash.
</para>
+ <note>
+ <para>
+ Beginning with MySQL 5.1.12, user-defined partitioning types
+ other than <literal>KEY</literal> or <literal>LINEAR
+ KEY</literal> were disabled for <literal>NDB</literal> tables.
+ </para>
+ </note>
+
</message>
</logentry>
@@ -75235,6 +75273,7 @@
<logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
<manual type="ndb-cluster-connection-pool"/>
<manual type="cluster"/>
<manual type="mysqld"/>
@@ -75762,7 +75801,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterapi"/>
<manual type="cluster"/>
</tags>
@@ -75777,10 +75816,10 @@
<message>
<para>
- (<literal>NDB</literal> API): When multiple processes or threads
- in parallel performed the same ordered scan with exclusive lock
- and updating the retrieved records, the scan could skip some
- records, which were not updated as the result.
+ When multiple processes or threads in parallel performed the
+ same ordered scan with exclusive lock and updated the retrieved
+ records, the scan could skip some records, which as a result
+ were not updated.
</para>
</message>
@@ -76450,9 +76489,9 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
<manual type="ndb_restore"/>
- <highlight type="cluster"/>
</tags>
<bugs>
@@ -76467,7 +76506,7 @@
<para>
Insert records were incorrectly applied by
- <command>ndb_restore</command>, thus making restoration from
+ <command>ndb_restore</command>, thus making restoring from
backup inconsistent if the binlog contained inserts.
</para>
@@ -77005,6 +77044,7 @@
<highlight type="cluster"/>
<manual type="cluster"/>
<manual type="ndb_restore"/>
+ <manual type="upgrades"/>
</tags>
<bugs>
@@ -77202,6 +77242,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="BLOB"/>
<manual type="cluster"/>
<manual type="DATETIME"/>
@@ -77410,6 +77451,7 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -77950,7 +77992,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="diskdata"/>
<manual type="cluster"/>
</tags>
@@ -77965,9 +78007,9 @@
<message>
<para>
- (Disk Data): Following 3 or more missed local checkpoints by a
- cluster node, a restart of the node caused incorrect undo
- information to be used for Disk Data tables.
+ Following 3 or more missed local checkpoints by a cluster node,
+ a restart of the node caused incorrect undo information to be
+ used for Disk Data tables.
</para>
</message>
@@ -78089,8 +78131,8 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
<manual type="cluster"/>
- <manual type="cluster"/>
</tags>
<bugs>
@@ -79790,7 +79832,7 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="clusterreplication"/>
<manual type="replication"/>
<manual type="cluster"/>
</tags>
@@ -79815,6 +79857,8 @@
</logentry>
+<!-- END CLUSTER FIXUPS -->
+
<logentry entrytype="bug">
<tags>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8553 - trunk/dynamic-docs/changelog | jon | 6 Nov |
