Author: jstephens
Date: 2009-09-23 11:06:08 +0200 (Wed, 23 Sep 2009)
New Revision: 16765
Log:
Fix LCP directory description in NDB Internals docs (Thanks, MMontgomery!)
Fix para ID
Fix wording/markup
Modified:
trunk/ndbapi/ndb-internals.xml
trunk/refman-5.1/mysql-cluster-configuration-core.xml
trunk/refman-5.1/mysql-cluster-programs-core.xml
Modified: trunk/ndbapi/ndb-internals.xml
===================================================================
--- trunk/ndbapi/ndb-internals.xml 2009-09-23 08:07:00 UTC (rev 16764)
+++ trunk/ndbapi/ndb-internals.xml 2009-09-23 09:06:08 UTC (rev 16765)
Changed blocks: 2, Lines Added: 41, Lines Deleted: 4; 3642 bytes
@@ -168,7 +168,7 @@
<filename>LCP</filename>: This directory holds 3
subdirectories, named <filename>0</filename>,
<filename>1</filename>, and <filename>2</filename>,
- which contain local checkpoint datafiles (one per
+ which contain local checkpoint data files (one per
checkpoint — see
<xref linkend="mysql-cluster-config-lcp-params"/>).
</para>
@@ -178,10 +178,47 @@
whose names follow the pattern
<filename>T<replaceable>N</replaceable>F<replaceable>M</replaceable>.Data</filename>,
where <replaceable>N</replaceable> is a table ID and
- and M is a fragment number. For each table, there are
- <link linkend="ndbparam-ndbd-nooffragmentlogfiles"><literal>NoOfFragmentLogFiles</literal></link>
- fragments, and thus that many files.
+ and M is a fragment number. Each data node typically
+ has one primary fragment and one backup fragment. This
+ means that, for a MySQL Cluster having 2 data nodes,
+ and with
+ <link linkend="ndbparam-ndbd-noofreplicas"><literal>NoOfReplicas
+ = 2</literal></link>, <replaceable>M</replaceable> is
+ either 0 to 1. For a 4-node cluster with
+ <link linkend="ndbparam-ndbd-noofreplicas"><literal>NoOfReplicas
+ = 2</literal></link>, <replaceable>M</replaceable> is
+ either 0 or 2 on node group 1, and either 1 or 3 on
+ node group 2.
</para>
+
+ <para>
+ In MySQL Cluster NDB 7.0 and later, when using
+ <command>ndbmtd</command> there may be more than one
+ primary fragment per node. In this case,
+ <replaceable>M</replaceable> is a number in the range
+ of 0 to the number of LQH worker threads in the entire
+ cluster, less 1. The number of fragments on each data
+ node is equal to the number of LQH on that node times
+ <link linkend="ndbparam-ndbd-noofreplicas"><literal>NoOfReplicas</literal></link>.
+ </para>
+
+ <note>
+ <para>
+ Increasing
+ <link linkend="ndbparam-ndbmtd-maxnoofexecutionthreads"><literal>MaxNoOfExecutionThreads</literal></link>
+ does not change the number of fragments used by
+ existing tables; only newly-created tables
+ automatically use the new fragment count. To force
+ the new fragment count to be used by an existing
+ table after increasing
+ <link linkend="ndbparam-ndbmtd-maxnoofexecutionthreads"><literal>MaxNoOfExecutionThreads</literal></link>,
+ you must perform an
+ <literal role="stmt" condition="alter-table">ALTER
+ TABLE ... REORGANIZE PARTITION</literal> statement
+ (just as when adding new node groups in MySQL
+ Cluster NDB 7.0 and later).
+ </para>
+ </note>
</listitem>
<listitem>
Modified: trunk/refman-5.1/mysql-cluster-configuration-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-configuration-core.xml 2009-09-23 08:07:00 UTC (rev 16764)
+++ trunk/refman-5.1/mysql-cluster-configuration-core.xml 2009-09-23 09:06:08 UTC (rev 16765)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 797 bytes
@@ -2073,8 +2073,8 @@
configuration parameter
<literal>MaxNoOfExecutionThreads</literal> applies to
<command>ndbmtd</command> only, and has no effect when used with
- <command>ndbd</command>. For a description of this parameter and
- its use, see <xref linkend="mysql-cluster-programs-ndbmtd"/>.
+ <command>ndbd</command>. For more information, see
+ <xref linkend="mysql-cluster-programs-ndbmtd"/>.
</para>
<formalpara>
Modified: trunk/refman-5.1/mysql-cluster-programs-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-programs-core.xml 2009-09-23 08:07:00 UTC (rev 16764)
+++ trunk/refman-5.1/mysql-cluster-programs-core.xml 2009-09-23 09:06:08 UTC (rev 16765)
Changed blocks: 3, Lines Added: 13, Lines Deleted: 3; 1583 bytes
@@ -1143,6 +1143,15 @@
</para>
<indexterm>
+ <primary>execution threads (MySQL Cluster)</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>MySQL Cluster</primary>
+ <secondary>execution threads</secondary>
+ </indexterm>
+
+ <indexterm>
<primary>ndbmtd</primary>
<secondary>MaxNoOfExecutionThreads</secondary>
</indexterm>
@@ -1166,7 +1175,7 @@
<title>Number of execution threads</title>
- <para id="mysql-cluster-param-ndbmtd-maxnoofexecutionthreads">
+ <para id="ndbparam-ndbmtd-maxnoofexecutionthreads">
The <literal>MaxNoOfExecutionThreads</literal> configuration
parameter is used to determine the number of local query
handler (LQH) threads spawned by <command>ndbmtd</command>.
@@ -1181,8 +1190,9 @@
<para>
This parameter takes an integer value from 2 to 8 inclusive.
- Generally, you should set this to the number of CPU cores on
- the data node host, as shown in the following table:
+ Generally, you should set this parameter equal to the number
+ of CPU cores on the data node host, as shown in the following
+ table:
</para>
<informaltable>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r16765 - in trunk: ndbapi refman-5.1 | jon.stephens | 23 Sep |
