Author: jstephens
Date: 2007-01-17 14:31:03 +0100 (Wed, 17 Jan 2007)
New Revision: 4545
Log:
Reformat.
Modified:
branches/telcos/refman-5.1/mysql-cluster.xml
trunk/refman-4.1/mysql-cluster.xml
trunk/refman-5.0/mysql-cluster.xml
trunk/refman-5.1/mysql-cluster.xml
Modified: branches/telcos/refman-5.1/mysql-cluster.xml
===================================================================
--- branches/telcos/refman-5.1/mysql-cluster.xml 2007-01-17 13:29:28 UTC (rev 4544)
+++ branches/telcos/refman-5.1/mysql-cluster.xml 2007-01-17 13:31:03 UTC (rev 4545)
Changed blocks: 6, Lines Added: 13, Lines Deleted: 14; 4133 bytes
@@ -39,7 +39,6 @@
Hartmut Holzgraefe, Carsten Pedersen, and Roland Bouman. Rewrite
editor: Jon Stephens; Supervising editor: Stefan Hinz.
</remark>
-
<para>
MySQL Cluster is a high-availability, high-redundancy version of
@@ -4877,8 +4876,8 @@
<para>
The default value is 30000 milliseconds (30 seconds). 0
- disables the timeout, in which case the cluster may
- start only if all nodes are available.
+ disables the timeout, in which case the cluster may start
+ only if all nodes are available.
</para>
</listitem>
@@ -5707,23 +5706,23 @@
reports are recorded in the cluster log; it is an integer
value representing the number of seconds between reports.
</para>
-
+
<para>
Each data node's data memory and index memory usage is
logged as both a percentage and a number of 32 KB pages of
the <literal>DataMemory</literal> and
- <literal>IndexMemory</literal>, respectively, set in the
+ <literal>IndexMemory</literal>, respectively, set in the
<filename>config.ini</filename> file. For example, if
<literal>DataMemory</literal> is equal to 100 MB, and a
given data node is using 50 MB for data memory storage,
the corresponding line in the cluster log might look like
- this:
+ this:
</para>
<programlisting>
2006-12-24 01:18:16 [MgmSrvr] INFO -- Node 2: Data usage is 50%(1280 32K pages of total 2560)
</programlisting>
-
+
<para>
<literal>MemReportFrequency</literal> is not a required
parameter. If used, it can be set for all cluster data
@@ -5735,10 +5734,10 @@
value — is 0, in which case memory reports are
logged only when memory usage reaches certain percentages
(80%, 90%, and 100%), as mentioned in the discussion of
- statistics events in
+ statistics events in
<xref linkend="mysql-cluster-log-events"/>.
</para>
-
+
<para>
This parameter was added in MySQL Cluster
5.1.14/NDB-6.1.0-beta.
@@ -15253,13 +15252,13 @@
beginning with MySQL 5.1.14, all MySQL Cluster replication
tables reside in the <literal>mysql</literal> system database.
</para>
-
+
<para>
Information about how this change affects upgrades from MySQL
Cluster 5.1.13 and earlier to 5.1.14 and later versions can be
found in <xref linkend="news-5-1-14"/>.
</para>
-
+
<para>
The following figure shows the relationship of the MySQL Cluster
replication master server, its binlog injector thread, and the
@@ -19097,15 +19096,15 @@
<literal>NDB</literal> tables based on
<literal>KEY</literal>, <literal>HASH</literal>,
<literal>LINEAR KEY</literal>, and <literal>LINEAR
- HASH</literal> schemes. This feature is also available for
+ HASH</literal> schemes. This feature is also available for
most other MySQL storage engines, which support additional
partitioning types that are not available to <literal>NDB
- Cluster</literal> tables.
+ Cluster</literal> tables.
</para>
<para>
For additional general information about user-defined
- partitioning in MySQL ¤t-series;, see
+ partitioning in MySQL ¤t-series;, see
<xref linkend="partitioning"/>. Specifics of partitioning
types are discussed in <xref linkend="partitioning-types"/>.
</para>
Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml 2007-01-17 13:29:28 UTC (rev 4544)
+++ trunk/refman-4.1/mysql-cluster.xml 2007-01-17 13:31:03 UTC (rev 4545)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 649 bytes
@@ -4891,8 +4891,8 @@
<para>
The default value is 30000 milliseconds (30 seconds). 0
- disables the timeout, in which case the cluster may
- start only if all nodes are available.
+ disables the timeout, in which case the cluster may start
+ only if all nodes are available.
</para>
</listitem>
Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml 2007-01-17 13:29:28 UTC (rev 4544)
+++ trunk/refman-5.0/mysql-cluster.xml 2007-01-17 13:31:03 UTC (rev 4545)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 649 bytes
@@ -4868,8 +4868,8 @@
<para>
The default value is 30000 milliseconds (30 seconds). 0
- disables the timeout, in which case the cluster may
- start only if all nodes are available.
+ disables the timeout, in which case the cluster may start
+ only if all nodes are available.
</para>
</listitem>
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-01-17 13:29:28 UTC (rev 4544)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-01-17 13:31:03 UTC (rev 4545)
Changed blocks: 3, Lines Added: 7, Lines Deleted: 7; 2155 bytes
@@ -4877,8 +4877,8 @@
<para>
The default value is 30000 milliseconds (30 seconds). 0
- disables the timeout, in which case the cluster may
- start only if all nodes are available.
+ disables the timeout, in which case the cluster may start
+ only if all nodes are available.
</para>
</listitem>
@@ -15193,13 +15193,13 @@
beginning with MySQL 5.1.14, all MySQL Cluster replication
tables reside in the <literal>mysql</literal> system database.
</para>
-
+
<para>
Information about how this change affects upgrades from MySQL
Cluster 5.1.13 and earlier to 5.1.14 and later versions can be
found in <xref linkend="news-5-1-14"/>.
</para>
-
+
<para>
The following figure shows the relationship of the MySQL Cluster
replication master server, its binlog injector thread, and the
@@ -19037,15 +19037,15 @@
<literal>NDB</literal> tables based on
<literal>KEY</literal>, <literal>HASH</literal>,
<literal>LINEAR KEY</literal>, and <literal>LINEAR
- HASH</literal> schemes. This feature is also available for
+ HASH</literal> schemes. This feature is also available for
most other MySQL storage engines, which support additional
partitioning types that are not available to <literal>NDB
- Cluster</literal> tables.
+ Cluster</literal> tables.
</para>
<para>
For additional general information about user-defined
- partitioning in MySQL ¤t-series;, see
+ partitioning in MySQL ¤t-series;, see
<xref linkend="partitioning"/>. Specifics of partitioning
types are discussed in <xref linkend="partitioning-types"/>.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4545 - branches/telcos/refman-5.1 trunk/refman-4.1 trunk/refman-5.0 trunk/refman-5.1 | jon | 17 Jan |
