Author: jstephens
Date: 2007-03-04 07:38:49 +0100 (Sun, 04 Mar 2007)
New Revision: 5163
Log:
Reformat.
Modified:
trunk/refman-5.1/mysql-cluster.xml
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-03-04 06:37:41 UTC (rev 5162)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-03-04 06:38:49 UTC (rev 5163)
Changed blocks: 9, Lines Added: 42, Lines Deleted: 41; 7893 bytes
@@ -4537,16 +4537,16 @@
in the SQL nodes.
</para>
</listitem>
-
+
<listitem>
<indexterm>
<primary><literal>LongMessageBuffer</literal></primary>
</indexterm>
-
+
<para id="mysql-cluster-param-ndbd-definition-longmessagebuffer">
<literal>LongMessageBuffer</literal>
</para>
-
+
<para>
This is an internal buffer used for passing messages
within individual nodes and between nodes. Although it is
@@ -4554,7 +4554,7 @@
configurable. By default, it is set to 1MB.
</para>
</listitem>
-
+
</itemizedlist>
<para id="mysql-cluster-logging-and-checkpointing">
@@ -4633,53 +4633,52 @@
do so via a rolling node restart.
</para>
</listitem>
-
+
<listitem>
<indexterm>
<primary><literal>MaxNoOfOpenFiles</literal></primary>
</indexterm>
-
+
<remark role="todo">
If this doesn't ever need to be changed, then why is it
even mentioned? [js]
</remark>
-
+
<para id="mysql-cluster-param-ndbd-definition-maxnoofopenfiles">
<literal>MaxNoOfOpenFiles</literal>
</para>
-
+
<para>
This parameter sets a ceiling on how many internal threads
to allocate for open files. <emphasis>Any situation
- requiring a change in this parameter should be reported as
- a bug</emphasis>.
+ requiring a change in this parameter should be reported as
+ a bug</emphasis>.
</para>
-
+
<para>
The default value is 40.
</para>
</listitem>
-
-
+
<listitem>
<indexterm>
<primary><literal>InitialNoOfOpenFiles</literal></primary>
</indexterm>
-
+
<para id="mysql-cluster-param-ndbd-definition-initialnoofopenfiles">
<literal>InitialNoOfOpenFiles</literal>
</para>
-
+
<para>
This parameter sets the initial number of internal threads
to allocate for open files.
</para>
-
+
<para>
The default value is 27.
</para>
</listitem>
-
+
<listitem>
<indexterm>
<primary><literal>MaxNoOfSavedMessages</literal></primary>
@@ -4699,31 +4698,30 @@
The default is 25 trace files.
</para>
</listitem>
-
-
+
<listitem>
<indexterm>
<primary><literal>MemReportFrequency</literal></primary>
</indexterm>
-
+
<para id="mysql-cluster-param-ndbd-definition-memreportfrequency">
<literal>MemReportFrequency</literal>
</para>
-
+
<para>
By default, warnings are written to the cluster only when
- high levels of data node
- memory usage are reached. Beginning with MySQL 5.1.16, it
- is possible — by setting this configuration
- parameter to a non-zero value <replaceable>N</replaceable>
- — to cause a memory usage report to be written to the
- cluster each <replaceable>N</replaceable> seconds instead.
+ high levels of data node memory usage are reached.
+ Beginning with MySQL 5.1.16, it is possible — by
+ setting this configuration parameter to a non-zero value
+ <replaceable>N</replaceable> — to cause a memory
+ usage report to be written to the cluster each
+ <replaceable>N</replaceable> seconds instead.
</para>
-
+
<para>
The default value is 0, in which case memory warnings are
logged only when the thresholds of 80%, 85%, 90%, 95%, and
- 100% of data node memory usage are reached.
+ 100% of data node memory usage are reached.
</para>
</listitem>
@@ -5924,43 +5922,43 @@
The default level is 0.
</para>
</listitem>
-
+
<listitem>
<indexterm>
<primary><literal>LogLevelError</literal></primary>
</indexterm>
-
+
<para id="mysql-cluster-param-ndbd-definition-loglevelerror">
<literal>LogLevelError</literal>
</para>
-
+
<para>
The reporting level for events generated by errors and
warnings by the cluster as a whole. These errors do not
cause any node failure but are still considered worth
reporting.
</para>
-
+
<para>
The default level is 0.
</para>
</listitem>
-
+
<listitem>
<indexterm>
<primary><literal>LogLevelCongestion</literal></primary>
</indexterm>
-
+
<para id="mysql-cluster-param-ndbd-definition-loglevelcongestion">
<literal>LogLevelCongestion</literal>
</para>
-
+
<para>
The reporting level for events generated by congestion.
These errors do not cause node failure but are still
considered worth reporting.
</para>
-
+
<para>
The default level is 0.
</para>
@@ -7749,7 +7747,8 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-stringmemory">StringMemory</link></literal></entry>
- <entry>integer or percentage (see <link
+ <entry>integer or percentage (see
+ <link
linkend="mysql-cluster-param-ndbd-definition-stringmemory">description</link>
for details)</entry>
<entry>0</entry>
@@ -7815,7 +7814,8 @@
<entry>N</entry>
</row>
<row>
- <entry><literal><link linkend="mysql-cluster-param-ndbd-definition-undodatabuffer">UndoDataBuffer</link></literal> (<emphasis>OBSOLETE</emphasis>)</entry>
+ <entry><literal><link linkend="mysql-cluster-param-ndbd-definition-undodatabuffer">UndoDataBuffer</link></literal>
+ (<emphasis>OBSOLETE</emphasis>)</entry>
<entry>bytes</entry>
<entry>2M</entry>
<entry>1M</entry>
@@ -7823,7 +7823,8 @@
<entry>N</entry>
</row>
<row>
- <entry><literal><link linkend="mysql-cluster-param-ndbd-definition-undodatabuffer">UndoDataBuffer</link></literal> (<emphasis>OBSOLETE</emphasis>)</entry>
+ <entry><literal><link linkend="mysql-cluster-param-ndbd-definition-undodatabuffer">UndoDataBuffer</link></literal>
+ (<emphasis>OBSOLETE</emphasis>)</entry>
<entry>bytes</entry>
<entry>2M</entry>
<entry>1M</entry>
@@ -18518,7 +18519,7 @@
<filename>config.ini</filename> configuration file, and is
measured in bytes.
</para>
-
+
<para>
The default value is 20M.
</para>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-03-04 06:37:41 UTC (rev 5162)
+++ trunk/refman-5.1/news-5.1.xml 2007-03-04 06:38:49 UTC (rev 5163)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 846 bytes
@@ -171,7 +171,7 @@
information.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A new configuration parameter
@@ -179,7 +179,7 @@
control of data node memory usage. Previously, only warnings
at predetermined percentages of memory allocation were given;
setting this parameter allows for that behavior to be
- overridden. For more information, see
+ overridden. For more information, see
<xref linkend="mysql-cluster-ndbd-definition"/>.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5163 - trunk/refman-5.1 | jon | 4 Mar |
