Author: jstephens
Date: 2007-09-05 07:42:41 +0200 (Wed, 05 Sep 2007)
New Revision: 7670
Log:
Reformat. (Sorry, forgot to do this prior to my previous commit.)
Modified:
trunk/refman-5.2/mysql-cluster.xml
Modified: trunk/refman-5.2/mysql-cluster.xml
===================================================================
--- trunk/refman-5.2/mysql-cluster.xml 2007-09-05 05:37:59 UTC (rev 7669)
+++ trunk/refman-5.2/mysql-cluster.xml 2007-09-05 05:42:41 UTC (rev 7670)
Changed blocks: 50, Lines Added: 159, Lines Deleted: 95; 20625 bytes
@@ -42,6 +42,7 @@
in MySQL ¤t-series; binary releases and in RPMs compatible
with most modern Linux distributions.
</para>
+
<!--
<note>
<para>
@@ -1903,9 +1904,9 @@
require a custom binary, see
<xref linkend="installing-source-tree"/>.)
</para>
-
- <!--&mccge-warning-unsupported-begin;-->
+<!--&mccge-warning-unsupported-begin;-->
+
<para>
RPMs are also available for both 32-bit and 64-bit Linux
platforms. For a MySQL Cluster, three RPMs are required:
@@ -1984,9 +1985,9 @@
cluster as discussed in
<xref linkend="mysql-cluster-multi-config"/>.
</para>
-
- <!--&mccge-warning-end-cluster;-->
+<!--&mccge-warning-end-cluster;-->
+
<note>
<para>
After completing the installation, do not yet start any of the
@@ -2120,9 +2121,9 @@
Remember that the preceding steps must be performed separately
on each machine where a data node or SQL node is to reside.
</para>
-
- <!--&mccge-warning-unsupported-begin;-->
+<!--&mccge-warning-unsupported-begin;-->
+
<formalpara>
<title>SQL node installation — RPM files</title>
@@ -2154,9 +2155,9 @@
creating the <literal>mysql</literal> user and group, if needed)
automatically.
</para>
-
- <!--&mccge-warning-unsupported-begin;-->
+<!--&mccge-warning-unsupported-begin;-->
+
<para>
<emphasis role="bold">Data Node Installation — RPM
Files</emphasis>
@@ -2180,9 +2181,9 @@
(<command>ndbd</command>) in the <filename>/usr/sbin</filename>
directory.
</para>
-
- <!--&mccge-warning-end-cluster;-->
+<!--&mccge-warning-end-cluster;-->
+
<para>
<emphasis role="bold">Management Node Installation —
<filename>.tar.gz</filename> Binary</emphasis>
@@ -2244,9 +2245,9 @@
</listitem>
</orderedlist>
-
- <!--&mccge-warning-unsupported-begin;-->
+<!--&mccge-warning-unsupported-begin;-->
+
<para>
<emphasis role="bold">Management Node Installation — RPM
File</emphasis>
@@ -2570,8 +2571,8 @@
</listitem>
<listitem>
- <!--&mccge-warning-unsupported-begin;-->
-
+<!--&mccge-warning-unsupported-begin;-->
+
<para>
If you used RPM files to install MySQL on the cluster host
where the SQL node is to reside, you can (and should) use
@@ -2581,9 +2582,9 @@
</listitem>
</orderedlist>
-
- <!--&mccge-warning-end-cluster;-->
+<!--&mccge-warning-end-cluster;-->
+
<indexterm>
<primary>MySQL Cluster</primary>
<secondary><command>ndb_mgm</command></secondary>
@@ -3176,7 +3177,7 @@
<xref linkend="installing-source-tree"/>.
</para>
- <!--&mccge-warning-begin;
+<!--&mccge-warning-begin;
<warning>
<para>
@@ -4317,11 +4318,15 @@
</para>
<para>
- Beginning with MySQL 5.1.16<!--
+ Beginning with MySQL 5.1.16
+
+<!--
(<emphasis>&mccge-series;</emphasis>: MySQL
- 5.1.15-ndb-6.1.3)-->, it is possible to disable arbitration
- completely by setting <literal>ArbitrationRank</literal>
- to 0 on all management and SQL nodes.
+ 5.1.15-ndb-6.1.3)-->
+
+ , it is possible to disable arbitration completely by
+ setting <literal>ArbitrationRank</literal> to 0 on all
+ management and SQL nodes.
</para>
</listitem>
@@ -4523,9 +4528,8 @@
</listitem>
<listitem>
+<!--&mccge-warning-begin;-->
- <!--&mccge-warning-begin;-->
-
<para id="mysql-cluster-param-ndbd-definition-tcpbind-inaddr-any">
<literal>TcpBind_INADDR_ANY</literal>
</para>
@@ -4537,13 +4541,13 @@
autogenerated connections). The default is
<literal>FALSE</literal> (<literal>0</literal>).
</para>
+
<!--
<para>
This parameter was added in MySQL 5.1.16-ndb-6.2.0.
</para>
&mccge-warning-end-cluster;-->
-
</listitem>
<listitem>
@@ -5562,9 +5566,9 @@
<indexterm>
<primary><literal>FragmentLogFileSize</literal></primary>
</indexterm>
-
- <!--&mccge-warning-begin;-->
-
+
+<!--&mccge-warning-begin;-->
+
<para id="mysql-cluster-param-ndbd-definition-fragmentlogfilesize">
<literal>FragmentLogFileSize</literal>
</para>
@@ -5574,9 +5578,8 @@
size of redo log files. The default is
<literal>16M</literal>.
</para>
-
- <!--&mccge-warning-end-cluster;-->
-
+
+<!--&mccge-warning-end-cluster;-->
</listitem>
<listitem>
@@ -5881,9 +5884,13 @@
</para>
<para>
- Beginning with MySQL 5.1.15<!-- (&mccge-series;: MySQL
- 5.1.15-ndb-6.1.1)-->, this parameter takes one of the integer
- values <literal>0</literal>, <literal>1</literal>, or
+ Beginning with MySQL 5.1.15
+
+<!-- (&mccge-series;: MySQL
+ 5.1.15-ndb-6.1.1)-->
+
+ , this parameter takes one of the integer values
+ <literal>0</literal>, <literal>1</literal>, or
<literal>2</literal>, which act as follows:
</para>
@@ -6008,9 +6015,12 @@
<warning>
<para>
- When using MySQL Cluster<!-- or &mccge-series;--> on Linux,
- <literal>ODirect</literal> should be enabled for 2.6 or
- newer kernels.
+ When using MySQL Cluster
+
+<!-- or &mccge-series;-->
+
+ on Linux, <literal>ODirect</literal> should be enabled
+ for 2.6 or newer kernels.
</para>
</warning>
@@ -7167,8 +7177,12 @@
</para>
<para>
- This parameter was added in MySQL Cluster 5.1.16<!--.
- (&mccge-series;: MySQL Cluster 5.1.14-ndb-6.1.0)-->.
+ This parameter was added in MySQL Cluster 5.1.16
+
+<!--.
+ (&mccge-series;: MySQL Cluster 5.1.14-ndb-6.1.0)-->
+
+ .
</para>
</listitem>
@@ -7294,8 +7308,8 @@
<primary>BackupReportFrequency</primary>
</indexterm>
- <!--&mccge-warning-begin;-->
-
+<!--&mccge-warning-begin;-->
+
<para id="mysql-cluster-param-ndbd-definition-backupreportfrequency">
This parameter controls how often backup status reports
are issued in the management client during a backup, as
@@ -7310,13 +7324,13 @@
<para>
The default value is 0.
</para>
+
<!--
<para>
This parameter was added in MySQL 5.1.19-ndb-6.2.3.
</para>
&mccge-warning-end-cluster;-->
-
</listitem>
<listitem>
@@ -7508,11 +7522,15 @@
</para>
<para>
- Beginning with MySQL 5.1.16<!--
+ Beginning with MySQL 5.1.16
+
+<!--
(<emphasis>&mccge-series;</emphasis>: MySQL
- 5.1.15-ndb-6.1.3)-->, it is possible to disable arbitration
- completely by setting <literal>ArbitrationRank</literal>
- to 0 on all management and SQL nodes.
+ 5.1.15-ndb-6.1.3)-->
+
+ , it is possible to disable arbitration completely by
+ setting <literal>ArbitrationRank</literal> to 0 on all
+ management and SQL nodes.
</para>
</listitem>
@@ -8671,10 +8689,13 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory">LockPagesInMainMemory</link></literal></entry>
- <entry><emphasis>As of MySQL 5.1.15<!-- (&mccge-series;: MySQL
- 5.1.15-ndb-6.1.1)--></emphasis>: integer;
- <emphasis>previously</emphasis>: true|false
- (<literal>1</literal>|<literal>0</literal>)</entry>
+ <entry><emphasis>As of MySQL 5.1.15
+
+<!-- (&mccge-series;: MySQL
+ 5.1.15-ndb-6.1.1)-->
+
+ </emphasis>: integer; <emphasis>previously</emphasis>:
+ true|false (<literal>1</literal>|<literal>0</literal>)</entry>
<entry>0</entry>
<entry>0</entry>
<entry>1</entry>
@@ -8896,8 +8917,12 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-memreportfrequency">MemReportFrequency</link></literal>
- (added in MySQL 5.1.16<!--; &mccge-series;: added in MySQL
- 5.1.14-ndb-6.1.0-->)</entry>
+ (added in MySQL 5.1.16
+
+<!--; &mccge-series;: added in MySQL
+ 5.1.14-ndb-6.1.0-->
+
+ )</entry>
<entry>integer</entry>
<entry>0</entry>
<entry>0</entry>
@@ -9042,7 +9067,8 @@
</row>
<row>
<entry><literal><link linkend="mysql-cluster-param-ndbd-definition-tcpbind-inaddr-any">TcpBind_INADDR_ANY</link></literal>
- <!--(<emphasis>&mccge-series; only</emphasis>: added in
+
+<!--(<emphasis>&mccge-series; only</emphasis>: added in
MySQL 5.1.16-ndb-6.2.0)--></entry>
<entry>true|false (<literal>1</literal>|<literal>0</literal>)</entry>
<entry>1</entry>
@@ -9742,7 +9768,7 @@
downgrade. See <xref linkend="mysql-cluster-configuration"/>.
</para>
- <!--<para>
+<!--<para>
For information about upgrading or downgrading between
&mccge-series; releases, or between &mccge-series; releases and
mainline MySQL releases, see the changelogs relating to
@@ -10273,7 +10299,7 @@
5.1.17 or earlier to MySQL 5.1.18 or later.
</para>
- <!--<para>
+<!--<para>
For users of &mccge-series; the relevant versions are as
follows:
@@ -12577,7 +12603,7 @@
<primary><literal>REPORT</literal> command (MySQL Cluster)</primary>
</indexterm>
- <!--&mccge-warning-begin;-->
+<!--&mccge-warning-begin;-->
<para>
<literal><replaceable>node_id</replaceable> REPORT
@@ -12601,9 +12627,8 @@
<para>
The REPORT command was introduced in MySQL 5.1.8-ndb-6.2.3.
</para>
-
- <!--&mccge-warning-end-cluster;-->
-
+
+<!--&mccge-warning-end-cluster;-->
</listitem>
<listitem>
@@ -15108,7 +15133,7 @@
present in the data node's <literal>DataDir</literal>.)
</para>
- <!--&mccge-warning-unsupported-begin;-->
+<!--&mccge-warning-unsupported-begin;-->
<para>
It is possible to restore data without restoring table
@@ -15133,7 +15158,7 @@
notice</emphasis>. (Bug #24363)
</para>
- <!--&mccge-warning-end-cluster;-->
+<!--&mccge-warning-end-cluster;-->
<para>
The <option>-b</option> option is used to specify the ID or
@@ -15392,7 +15417,9 @@
<row>
<entry><option>--skip-table-check</option></entry>
<entry><option>-s</option></entry>
- <entry>Do not check table schemas (Added in MySQL 5.1.17<!--; <emphasis>not
+ <entry>Do not check table schemas (Added in MySQL 5.1.17
+
+<!--; <emphasis>not
supported in &mccge-series;</emphasis>)--></entry>
<entry><literal>FALSE</literal></entry>
</row>
@@ -15406,7 +15433,7 @@
</tgroup>
</informaltable>
- <!--&mccge-warning-unsupported-begin;-->
+<!--&mccge-warning-unsupported-begin;-->
<para>
Beginning with MySQL 5.1.18, several additional options are
@@ -15524,7 +15551,7 @@
</itemizedlist>
</para>
- <!--&mccge-warning-end-cluster;-->
+<!--&mccge-warning-end-cluster;-->
<indexterm>
<primary><command>ndb_restore</command></primary>
@@ -15963,6 +15990,7 @@
management client command <literal>ALL STATUS</literal>.
</para>
</listitem>
+
<!--
<listitem>
&mccge-warning-begin;
@@ -16018,7 +16046,8 @@
<listitem>
<para>
<command>ndbd_redo_log_reader</command>
- <!--(<emphasis>&mccge-series; only</emphasis>)-->
+
+<!--(<emphasis>&mccge-series; only</emphasis>)-->
</para>
</listitem>
@@ -17471,7 +17500,7 @@
<manvolnum>1</manvolnum>
<refmiscinfo class="manual">MySQL Database System</refmiscinfo>
<refmiscinfo class="source">MySQL</refmiscinfo>
- <!--<refmiscinfo class="version">&mccge-series;</refmiscinfo>-->
+<!--<refmiscinfo class="version">&mccge-series;</refmiscinfo>-->
<refmiscinfo class="refman">Check and Print Content of Cluster Redo Log</refmiscinfo>
</refmeta>
@@ -17490,9 +17519,11 @@
<refsection id="ndb-redo-log-reader">
<title>Description</title>
+
<!--
&mccge-warning-section;
-->
+
<para>
Reads a redo log file, checking it for errors, printing its
contents in a human-readable format, or both.
@@ -17502,12 +17533,15 @@
</para>
<para>
- This utility<!-- was made available as part of the default
+ This utility
+
+<!-- was made available as part of the default
builds of &mccge-series; beginning with MySQL
- 5.1.15-ndb-6.1.3. It--> remains under development, and its
- syntax and behavior are subject to change in future
- releases. For this reason, it should be considered
- experimental at this time.
+ 5.1.15-ndb-6.1.3. It-->
+
+ remains under development, and its syntax and behavior are
+ subject to change in future releases. For this reason, it
+ should be considered experimental at this time.
</para>
<para>
@@ -19262,6 +19296,7 @@
</para>
</formalpara>
+
<!--
&mccge-warning-unsupported-begin;
<para>
@@ -20094,9 +20129,11 @@
are covered in
<xref linkend="mysql-cluster-replication-two-channels"/>.
</para>
+
<!--
&mccge-warning-begin;
-->
+
<indexterm>
<primary>batched updates (MySQL Cluster Replication)</primary>
</indexterm>
@@ -20168,11 +20205,11 @@
6 rows in set (0.00 sec)
</programlisting>
</para>
+
<!--
&mccge-warning-end-cluster;
-->
-
</section>
<section id="mysql-cluster-replication-two-channels">
@@ -21015,9 +21052,11 @@
<primary>conflict resolution</primary>
<secondary>in MySQL Cluster Replication</secondary>
</indexterm>
+
<!--
&mccge-warning-section;
-->
+
<para>
When using a replication setup involving multiple masters, it is
possible that different masters may try to update the same row
@@ -23095,17 +23134,25 @@
<para>
In the sections that follow, we discuss known limitations in MySQL
- ¤t-series; Cluster<!-- and &mccge-series;--> releases as compared
- with the features available when using the
+ ¤t-series; Cluster
+
+<!-- and &mccge-series;-->
+
+ releases as compared with the features available when using the
<literal>MyISAM</literal> and <literal>InnoDB</literal> storage
engines. Currently, there are no plans to address these in coming
- releases of MySQL ¤t-series;<!-- or &mccge-series;-->; however, we
- will attempt to supply fixes for these issues in subsequent
- release series. If you check the <quote>Cluster</quote> category
- in the MySQL bugs database at
+ releases of MySQL ¤t-series;
+
+<!-- or &mccge-series;-->
+
+ ; however, we will attempt to supply fixes for these issues in
+ subsequent release series. If you check the <quote>Cluster</quote>
+ category in the MySQL bugs database at
<ulink url="http://bugs.mysql.com"/>, you can find known bugs
which (if marked <quote>¤t-series;</quote>) we intend to
- correct in upcoming releases of MySQL ¤t-series;.<!-- Some of
+ correct in upcoming releases of MySQL ¤t-series;.
+
+<!-- Some of
these issues may be addressed in &mccge-series; and the fixes
included in a future mainline MySQL Cluster version.-->
</para>
@@ -23591,15 +23638,18 @@
<listitem>
<para>
The maximum number of metadata objects in
- MySQL ¤t-series; Cluster<!-- and
- &mccge-series;--> is 20320. This limit is
- hard-coded.
+ MySQL ¤t-series; Cluster
+
+<!-- and
+ &mccge-series;-->
+
+ is 20320. This limit is hard-coded.
</para>
</listitem>
</itemizedlist>
- <!--<note>
+<!--<note>
<para role="mccge-warning">
&mccge-series; users should see
<xref linkend="mysql-cluster-limitations-resolved"/>,
@@ -24484,17 +24534,23 @@
concurrently on a single host, it is not always advisable to
do so for reasons of performance and high availability, as
well as other considerations. In particular, in MySQL
- ¤t-series;<!-- or &mccge-series;-->, we do not support for
- production use any MySQL Cluster deployment in which more than
- one <command>ndbd</command> process is run on a single
- physical machine.
+ ¤t-series;
+<!-- or &mccge-series;-->
+
+ , we do not support for production use any MySQL Cluster
+ deployment in which more than one <command>ndbd</command>
+ process is run on a single physical machine.
+
<note>
<para>
We may support multiple data nodes per host in a future
MySQL release, following additional testing. However, in
- MySQL ¤t-series;<!-- and &mccge-series;-->, such
- configurations can be considered experimental only.
+ MySQL ¤t-series;
+
+<!-- and &mccge-series;-->
+
+ , such configurations can be considered experimental only.
</para>
</note>
</para>
@@ -24543,8 +24599,12 @@
<para>
A number of limitations and related issues existing in earlier
versions of MySQL Cluster have been resolved over the course of
- development of MySQL ¤t-series;<!-- or &mccge-series;-->:
+ development of MySQL ¤t-series;
+<!-- or &mccge-series;-->
+
+ :
+
<itemizedlist>
<listitem>
@@ -24800,10 +24860,10 @@
</listitem>
<listitem>
-
- <!--&mccge-warning-begin;-->
- <formalpara>
+<!--&mccge-warning-begin;-->
+ <formalpara>
+
<title>Maximum number of cluster nodes</title>
<para>
@@ -24823,6 +24883,7 @@
nodes and management nodes beginning with this version is
63, of which up to 48 can be data nodes.
</para>
+
<!--
<para>
The limitation that a data node cannot have a node ID
@@ -24830,7 +24891,7 @@
</para>
&mccge-warning-end-cluster;-->
- </listitem>
+ </listitem>
</itemizedlist>
</para>
@@ -24878,9 +24939,12 @@
<para>
In this section, we discuss changes in the implementation of MySQL
- Cluster in MySQL ¤t-series; <!--and &mccge-series;--> as compared
- to MySQL &previous-series;.
+ Cluster in MySQL ¤t-series;
+<!--and &mccge-series;-->
+
+ as compared to MySQL &previous-series;.
+
<!--
We also discuss our roadmap for further improvements to MySQL Cluster
as currently planned for MySQL &next-series;.
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7670 - trunk/refman-5.2 | jon | 5 Sep |
