Author: jstephens
Date: 2010-07-08 16:26:38 +0200 (Thu, 08 Jul 2010)
New Revision: 21622
Log:
Documented fix for Cluster BUG#54521
Fixed typo; added NDB-6.3.35/7.0.16/7.1.5 release dates (Thanks, AndrewH!)
Modified:
trunk/dynamic-docs/changelog/mysqld-2.xml
trunk/dynamic-docs/changelog/mysqld-versions.xml
trunk/refman-5.1/mysql-cluster-overview.xml
Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml 2010-07-08 14:18:06 UTC (rev 21621)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml 2010-07-08 14:26:38 UTC (rev 21622)
Changed blocks: 2, Lines Added: 30, Lines Deleted: 1; 1408 bytes
@@ -6,6 +6,35 @@
]>
<changelog>
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ <manual type="BuildIndexThreads"/>
+ <manual type="ndbmtd"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="54521"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.47-ndb-7.0.16"/>
+ <version ver="5.1.47-ndb-7.1.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The setting for <literal>BuildIndexThreads</literal> was ignored
+ by <command>ndbmtd</command>, which made it impossible to use
+ more than 4 cores for rebuilding indexes.
+ </para>
+
+ </message>
+
+ </logentry>
+
<logentry entrytype="feature">
<tags>
@@ -162,7 +191,7 @@
<para>
Introduced the
- <link linkend="ndbparam-ndbd-heartbeatorder"><literal>HeartbestOrder</literal></link>
+ <link linkend="ndbparam-ndbd-heartbeatorder"><literal>HeartbeatOrder</literal></link>
data node configuration parameter, which can be used to set the
order in which hearts are transmitted between data nodes. This
parameter can be useful in situations where multiple data nodes
Modified: trunk/dynamic-docs/changelog/mysqld-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-versions.xml 2010-07-08 14:18:06 UTC (rev 21621)
+++ trunk/dynamic-docs/changelog/mysqld-versions.xml 2010-07-08 14:26:38 UTC (rev 21622)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 1330 bytes
@@ -124,11 +124,11 @@
<versionentry ver="5.1.49" reldate="Not yet released"/>
<versionentry ver="5.1.48" reldate="02 June 2010"/>
<versionentry ver="5.1.47" subver="ndb-7.1.6" reldate="Not yet released"/>
- <versionentry ver="5.1.47" subver="ndb-7.1.5" reldate="Not yet released"/>
+ <versionentry ver="5.1.47" subver="ndb-7.1.5" reldate="25 June 2010"/>
<versionentry ver="5.1.47" subver="ndb-7.0.17" reldate="Not yet released"/>
- <versionentry ver="5.1.47" subver="ndb-7.0.16" reldate="Not yet released"/>
+ <versionentry ver="5.1.47" subver="ndb-7.0.16" reldate="25 June 2010"/>
<versionentry ver="5.1.47" subver="ndb-6.3.36" reldate="Not yet released"/>
- <versionentry ver="5.1.47" subver="ndb-6.3.35" reldate="Not yet released"/>
+ <versionentry ver="5.1.47" subver="ndb-6.3.35" reldate="25 June 2010"/>
<versionentry ver="5.1.47" subver="ndb-6.2.20" reldate="Not yet released"/>
<versionentry ver="5.1.47" subver="ndb-6.2.19" reldate="Not yet released"/>
<versionentry ver="5.1.47" reldate="06 May 2010"/>
Modified: trunk/refman-5.1/mysql-cluster-overview.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-overview.xml 2010-07-08 14:18:06 UTC (rev 21621)
+++ trunk/refman-5.1/mysql-cluster-overview.xml 2010-07-08 14:26:38 UTC (rev 21622)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 2134 bytes
@@ -1601,7 +1601,7 @@
Beginning with MySQL Cluster NDB 7.1.5, it is possible to
set a specific order for transmission of heartbeats
between datat nodes, using the
- <link linkend="ndbparam-ndbd-heartbeatorder"><literal>HeartbestOrder</literal></link>
+ <link linkend="ndbparam-ndbd-heartbeatorder"><literal>HeartbeatOrder</literal></link>
data node configuration parameter introduced in this
version. This parameter can be useful in situations where
multiple data nodes are running on the same host and a
@@ -2390,7 +2390,7 @@
Beginning with MySQL Cluster NDB 7.0.16, it is possible to
set a specific order for transmission of heartbeats
between datat nodes, using the
- <link linkend="ndbparam-ndbd-heartbeatorder"><literal>HeartbestOrder</literal></link>
+ <link linkend="ndbparam-ndbd-heartbeatorder"><literal>HeartbeatOrder</literal></link>
data node configuration parameter introduced in this
version. This parameter can be useful in situations where
multiple data nodes are running on the same host and a
@@ -3239,7 +3239,7 @@
Beginning with MySQL Cluster NDB 6.3.35, it is possible
to set a specific order for transmission of heartbeats
between datat nodes, using the
- <link linkend="ndbparam-ndbd-heartbeatorder"><literal>HeartbestOrder</literal></link>
+ <link linkend="ndbparam-ndbd-heartbeatorder"><literal>HeartbeatOrder</literal></link>
data node configuration parameter introduced in this
version. This parameter can be useful in situations
where multiple data nodes are running on the same host
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r21622 - in trunk: dynamic-docs/changelog refman-5.1 | jon.stephens | 8 Jul |
