Author: jstephens
Date: 2010-10-18 15:11:54 +0200 (Mon, 18 Oct 2010)
New Revision: 23180
Log:
De-gunking and general revisions
Modified:
trunk/refman-5.1/mysql-cluster-multi-computer.xml
Modified: trunk/refman-5.1/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-multi-computer.xml 2010-10-18 13:11:14 UTC (rev 23179)
+++ trunk/refman-5.1/mysql-cluster-multi-computer.xml 2010-10-18 13:11:54 UTC (rev 23180)
Changed blocks: 5, Lines Added: 97, Lines Deleted: 113; 10056 bytes
@@ -2958,144 +2958,126 @@
<para>
There are a number of reasons why a rolling restart might be
- desirable:
+ desirable. These are described in the next few paragraphs.
</para>
- <itemizedlist>
+ <formalpara>
- <listitem>
- <formalpara>
+ <title>Cluster configuration change</title>
- <title>Cluster configuration change</title>
+ <indexterm>
+ <primary>MySQL Cluster</primary>
+ <secondary>configuration changes</secondary>
+ </indexterm>
- <indexterm>
- <primary>MySQL Cluster</primary>
- <secondary>configuration changes</secondary>
- </indexterm>
+ <para>
+ To make a change in the cluster's configuration, such as
+ adding an SQL node to the cluster, or setting a configuration
+ parameter to a new value.
+ </para>
- <para>
- To make a change in the cluster's configuration, such
- as adding an SQL node to the cluster, or setting a
- configuration parameter to a new value.
- </para>
+ </formalpara>
- </formalpara>
- </listitem>
+ <formalpara>
- <listitem>
- <formalpara>
+ <title>Cluster software upgrade/downgrade</title>
- <title>Cluster software upgrade/downgrade</title>
+ <para>
+ To upgrade the cluster to a newer version of the MySQL Cluster
+ software (or to downgrade it to an older version). This is
+ usually referred to as a <quote>rolling upgrade</quote> (or
+ <quote>rolling downgrade</quote>, when reverting to an older
+ version of MySQL Cluster).
+ </para>
- <para>
- To upgrade the cluster to a newer version of the MySQL
- Cluster software (or to downgrade it to an older version).
- This is usually referred to as a <quote>rolling
- upgrade</quote> (or <quote>rolling downgrade</quote>, when
- reverting to an older version of MySQL Cluster).
- </para>
+ </formalpara>
- </formalpara>
- </listitem>
+ <formalpara>
- <listitem>
- <formalpara>
+ <title>Change on node host</title>
- <title>Change on node host</title>
+ <para>
+ To make changes in the hardware or operating system on which
+ one or more cluster nodes are running.
+ </para>
- <para>
- To make changes in the hardware or operating system on
- which one or more cluster nodes are running.
- </para>
+ </formalpara>
- </formalpara>
- </listitem>
+ <formalpara>
- <listitem>
- <formalpara>
+ <title>Cluster reset</title>
- <title>Cluster reset</title>
+ <indexterm>
+ <primary>MySQL Cluster</primary>
+ <secondary>resetting</secondary>
+ </indexterm>
- <indexterm>
- <primary>MySQL Cluster</primary>
- <secondary>resetting</secondary>
- </indexterm>
+ <para>
+ To reset the cluster because it has reached an undesirable
+ state. In such cases it is often desirable to reload the data
+ and metadata of one or more data nodes. This can be done 1 of
+ 3 ways:
+ </para>
- <para>
- To reset the cluster because it has reached an undesirable
- state. In such cases it is often desirable to reload the
- data and metadata of one or more data nodes. This can be
- done 1 of 3 ways:
+ </formalpara>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- Start each data node process
- (<command>ndbd</command>, or possibly
- <command>ndbmtd</command> in MySQL Cluster NDB 7.0
- and later) with the
- <option role="ndbd">--initial</option> option, which
- forces the data node to clear its filesystem and
- reload data and metadata from the other data nodes.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Start each data node process (<command>ndbd</command>, or
+ possibly <command>ndbmtd</command> in MySQL Cluster NDB 7.0
+ and later) with the <option role="ndbd">--initial</option>
+ option, which forces the data node to clear its filesystem
+ and reload data and metadata from the other data nodes.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Create a backup using the <command>ndb_mgm</command>
- client <literal>BACKUP</literal> command prior to
- performing the restart. Following the upgrade,
- restore the node or nodes using
- <command>ndb_restore</command>.
- </para>
+ <listitem>
+ <para>
+ Create a backup using the <command>ndb_mgm</command> client
+ <literal>BACKUP</literal> command prior to performing the
+ restart. Following the upgrade, restore the node or nodes
+ using <command>ndb_restore</command>.
+ </para>
- <para>
- See <xref linkend="mysql-cluster-backup"/>, and
- <xref linkend="mysql-cluster-programs-ndb-restore"/>,
- for more information.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Use <command>mysqldump</command> (see
- <xref linkend="mysqldump"/>) to create a backup
- prior to the upgrade; afterward, restore the dump
- using
- <literal role="stmt" condition="load-data">LOAD DATA
- INFILE</literal>.
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
-
- </formalpara>
+ <para>
+ See <xref linkend="mysql-cluster-backup"/>, and
+ <xref linkend="mysql-cluster-programs-ndb-restore"/>, for
+ more information.
+ </para>
</listitem>
<listitem>
- <formalpara>
+ <para>
+ Use <command>mysqldump</command> (see
+ <xref linkend="mysqldump"/>) to create a backup prior to the
+ upgrade; afterward, restore the dump using
+ <literal role="stmt" condition="load-data">LOAD DATA
+ INFILE</literal>.
+ </para>
+ </listitem>
- <title>Freeing of resources</title>
+ </itemizedlist>
- <indexterm>
- <primary>MySQL Cluster</primary>
- <secondary>memory usage and recovery</secondary>
- </indexterm>
+ <formalpara>
- <para>
- To permit memory allocated to a table by successive
- <literal role="stmt">INSERT</literal> and
- <literal role="stmt">DELETE</literal> operations to be
- freed for re-use by other MySQL Cluster tables.
- </para>
+ <title>Freeing of resources</title>
- </formalpara>
- </listitem>
+ <indexterm>
+ <primary>MySQL Cluster</primary>
+ <secondary>memory usage and recovery</secondary>
+ </indexterm>
- </itemizedlist>
+ <para>
+ To permit memory allocated to a table by successive
+ <literal role="stmt">INSERT</literal> and
+ <literal role="stmt">DELETE</literal> operations to be freed
+ for re-use by other MySQL Cluster tables.
+ </para>
+ </formalpara>
+
<para>
The process for performing a rolling restart may be generalized
as follows:
@@ -3494,7 +3476,8 @@
perform an online upgrade from MySQL Cluster NDB 7.0.9b and
earlier MySQL Cluster NDB 7.0 releases to MySQL Cluster NDB
7.0.10. Instead, you should upgrade your MySQL Cluster NDB
- 7.0 cluster directly to MySQL Cluster NDB 7.0.11 or later.
+ 7.0 installation directly to MySQL Cluster NDB 7.0.11 or
+ later.
</para>
<para>
@@ -3510,7 +3493,7 @@
It was not possible to perform an online upgrade from a
MySQL Cluster NDB 6.3 or 7.0 release to MySQL Cluster NDB
7.1.0 or 7.1.1. This issue was fixed in MySQL Cluster NDB
- 7.1.2. (Bug#51429)
+ 7.1.2 (see Bug#51429).
</para>
</listitem>
@@ -3597,8 +3580,8 @@
<para>
MySQL Cluster NDB 6.1 is no longer in production; if you are
still using a MySQL Cluster NDB 6.1 release, you should
- upgrade to the most recent MySQL Cluster NDB 6.3 or 7.0
- release as soon as possible.
+ upgrade to the most recent MySQL Cluster NDB 7.0 or MySQL
+ Cluster NDB 7.1 release as soon as possible.
</para>
</listitem>
@@ -3816,9 +3799,10 @@
<listitem>
<para>
- You cannot downgrade a MySQL 5.1.6 or later Cluster using
- Disk Data tables to MySQL 5.1.5 or earlier unless you
- convert all such tables to in-memory Cluster tables first.
+ You cannot downgrade a MySQL Cluster based on MySQL 5.1.6 or
+ later and using Disk Data tables to MySQL 5.1.5 or earlier
+ unless you convert all such tables to in-memory
+ <literal role="se">NDB</literal> tables first.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r23180 - trunk/refman-5.1 | jon.stephens | 18 Oct |
