Author: paul
Date: 2006-01-11 20:49:43 +0100 (Wed, 11 Jan 2006)
New Revision: 766
Log:
r6091@frost: paul | 2006-01-11 13:49:14 -0600
De-cruft.
Modified:
trunk/
trunk/refman-4.1/ndbcluster.xml
trunk/refman-5.0/ndbcluster.xml
trunk/refman-5.1/ndbcluster.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6086
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1994
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6091
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1994
Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml 2006-01-11 18:44:24 UTC (rev 765)
+++ trunk/refman-4.1/ndbcluster.xml 2006-01-11 19:49:43 UTC (rev 766)
@@ -6180,296 +6180,295 @@
<para>
There are several different startup types and modes, as shown
here:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Initial Start</emphasis>: The
- cluster starts with a clean filesystem on all data nodes.
- This occurs either when the cluster started for the very
- first time, or when it is restarted using the
- <option>--initial</option> option.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Initial Start</emphasis>: The cluster
+ starts with a clean filesystem on all data nodes. This
+ occurs either when the cluster started for the very first
+ time, or when it is restarted using the
+ <option>--initial</option> option.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">System Restart</emphasis>: The
- cluster starts and reads data stored in the data nodes.
- This occurs when the cluster has been shut down after
- having been in use, when it is desired for the cluster
- resume operations from the point where it left off.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">System Restart</emphasis>: The cluster
+ starts and reads data stored in the data nodes. This occurs
+ when the cluster has been shut down after having been in
+ use, when it is desired for the cluster resume operations
+ from the point where it left off.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Node Restart</emphasis>: This is the
- online restart of a cluster node while the cluster itself
- is running.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Node Restart</emphasis>: This is the
+ online restart of a cluster node while the cluster itself is
+ running.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Initial Node Restart</emphasis>:
- This is the same as a node restart, except that the node
- is reinitialized and started with a clean filesystem.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Initial Node Restart</emphasis>: This
+ is the same as a node restart, except that the node is
+ reinitialized and started with a clean filesystem.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
+ </itemizedlist>
<para>
Prior to startup, each data node (<literal>ndbd</literal>
process) must be initialized. This consists of the following:
+ </para>
- <orderedlist>
+ <orderedlist>
- <listitem>
- <para>
- Obtain a Node ID.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Obtain a Node ID.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Fetch configuration data.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Fetch configuration data.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Allocate ports to be used for inter-node communications.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Allocate ports to be used for inter-node communications.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Allocate memory according to settings obtained from the
- configuration file.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Allocate memory according to settings obtained from the
+ configuration file.
+ </para>
+ </listitem>
- </orderedlist>
- </para>
+ </orderedlist>
<para>
Once each data node has been initialized, the cluster startup
process can proceed. The stages which the cluster goes through
during this process are listed here:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Stage 0</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 0</emphasis>
+ </para>
- <para>
- Clear the cluster filesystem. This occurs
- <emphasis>only</emphasis> if the cluster was started with
- the <literal>--initial</literal> option.
- </para>
- </listitem>
+ <para>
+ Clear the cluster filesystem. This occurs
+ <emphasis>only</emphasis> if the cluster was started with
+ the <literal>--initial</literal> option.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 1</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 1</emphasis>
+ </para>
- <para>
- Cluster connections are set up; inter-node communications
- are established. Cluster heartbeats are started.
- </para>
- </listitem>
+ <para>
+ Cluster connections are set up; inter-node communications
+ are established. Cluster heartbeats are started.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 2</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 2</emphasis>
+ </para>
- <para>
- The arbitrator node is elected.
- </para>
+ <para>
+ The arbitrator node is elected.
+ </para>
- <para>
- If this is a system restart, then the cluster determines
- the latest restorable global checkpoint.
- </para>
- </listitem>
+ <para>
+ If this is a system restart, then the cluster determines the
+ latest restorable global checkpoint.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 3</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 3</emphasis>
+ </para>
- <para>
- This stage consists of the initialization of a number of
- internal cluster variables.
- </para>
- </listitem>
+ <para>
+ This stage consists of the initialization of a number of
+ internal cluster variables.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 4</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 4</emphasis>
+ </para>
- <para>
- For an initial start or initial node restart, the redo log
- files are created. The number of these files is equal to
- <literal>NoOfFragmentLogFiles</literal>.
- </para>
+ <para>
+ For an initial start or initial node restart, the redo log
+ files are created. The number of these files is equal to
+ <literal>NoOfFragmentLogFiles</literal>.
+ </para>
- <para>
- For a system restart:
+ <para>
+ For a system restart:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- Read schema or schemas.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Read schema or schemas.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Read data from the local checkpoint and undo logs.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Read data from the local checkpoint and undo logs.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Apply all redo information until the latest
- restorable global checkpoint has been reached.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Apply all redo information until the latest restorable
+ global checkpoint has been reached.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
+ </itemizedlist>
- <para>
- For a node restart, find the tail of the redo log.
- </para>
- </listitem>
+ <para>
+ For a node restart, find the tail of the redo log.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 5</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 5</emphasis>
+ </para>
- <para>
- If this is an initial start, create the
- <literal>SYSTAB_0</literal> and
- <literal>NDB$EVENTS</literal> internal system tables.
- </para>
+ <para>
+ If this is an initial start, create the
+ <literal>SYSTAB_0</literal> and
+ <literal>NDB$EVENTS</literal> internal system tables.
+ </para>
- <para>
- For a node restart or an initial node restart:
+ <para>
+ For a node restart or an initial node restart:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- The node is included in transaction handling
- operations.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The node is included in transaction handling operations.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The node's schema is compared with the
- master' and synchronized with it.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The node's schema is compared with the master'
+ and synchronized with it.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Synchronize data received in the form of
- <literal>INSERT</literal> from the other data nodes
- in this node's node group.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Synchronize data received in the form of
+ <literal>INSERT</literal> from the other data nodes in
+ this node's node group.
+ </para>
+ </listitem>
- <listitem>
- <para>
- In all cases, wait for complete local checkpoint as
- determined by the arbitrator.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ In all cases, wait for complete local checkpoint as
+ determined by the arbitrator.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
- </listitem>
+ </itemizedlist>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 6</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 6</emphasis>
+ </para>
- <para>
- Update internal variables.
- </para>
- </listitem>
+ <para>
+ Update internal variables.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 7</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 7</emphasis>
+ </para>
- <para>
- Update internal variables.
- </para>
- </listitem>
+ <para>
+ Update internal variables.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 8</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 8</emphasis>
+ </para>
- <para>
- In a system restart, rebuild all indexes.
- </para>
- </listitem>
+ <para>
+ In a system restart, rebuild all indexes.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 9</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 9</emphasis>
+ </para>
- <para>
- Update internal variables.
- </para>
- </listitem>
+ <para>
+ Update internal variables.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 10</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 10</emphasis>
+ </para>
- <para>
- At this point in a node restart or initial node restart,
- APIs may connect to the node and being to receive events.
- </para>
- </listitem>
+ <para>
+ At this point in a node restart or initial node restart,
+ APIs may connect to the node and being to receive events.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 11</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 11</emphasis>
+ </para>
- <para>
- At this point in a node restart or initial node restart,
- event delivery is handed over to the node joining the
- cluster. The newly-joined node takes over responsibility
- for delivering its primary data to subscribers.
- </para>
- </listitem>
+ <para>
+ At this point in a node restart or initial node restart,
+ event delivery is handed over to the node joining the
+ cluster. The newly-joined node takes over responsibility for
+ delivering its primary data to subscribers.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
+ </itemizedlist>
<para>
Once this process is completed for an initial start or system
Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml 2006-01-11 18:44:24 UTC (rev 765)
+++ trunk/refman-5.0/ndbcluster.xml 2006-01-11 19:49:43 UTC (rev 766)
@@ -52,42 +52,42 @@
<para>
<emphasis role="bold">Additional resources</emphasis>
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- Answers to some commonly asked questions about Cluster may be
- found in the <xref linkend="mysql-cluster-faq"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Answers to some commonly asked questions about Cluster may be
+ found in the <xref linkend="mysql-cluster-faq"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The MySQL Cluster mailing list:
- <ulink url="http://lists.mysql.com/cluster"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The MySQL Cluster mailing list:
+ <ulink url="http://lists.mysql.com/cluster"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The MySQL Cluster forum:
- <ulink url="http://forums.mysql.com/list.php?25"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The MySQL Cluster forum:
+ <ulink url="http://forums.mysql.com/list.php?25"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- If you are new to MySQL Cluster, you may find our Developer
- Zone article
- <ulink url="http://dev.mysql.com/tech-resources/articles/mysql-cluster-for-two-servers.html">
- How to set up a MySQL Cluster for two servers</ulink> to be
- helpful.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ If you are new to MySQL Cluster, you may find our Developer Zone
+ article
+ <ulink url="http://dev.mysql.com/tech-resources/articles/mysql-cluster-for-two-servers.html">
+ How to set up a MySQL Cluster for two servers</ulink> to be
+ helpful.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
+ </itemizedlist>
<section id="mysql-cluster-overview">
@@ -6160,296 +6160,295 @@
<para>
There are several different startup types and modes, as shown
here:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Initial Start</emphasis>: The
- cluster starts with a clean filesystem on all data nodes.
- This occurs either when the cluster started for the very
- first time, or when it is restarted using the
- <option>--initial</option> option.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Initial Start</emphasis>: The cluster
+ starts with a clean filesystem on all data nodes. This
+ occurs either when the cluster started for the very first
+ time, or when it is restarted using the
+ <option>--initial</option> option.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">System Restart</emphasis>: The
- cluster starts and reads data stored in the data nodes.
- This occurs when the cluster has been shut down after
- having been in use, when it is desired for the cluster
- resume operations from the point where it left off.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">System Restart</emphasis>: The cluster
+ starts and reads data stored in the data nodes. This occurs
+ when the cluster has been shut down after having been in
+ use, when it is desired for the cluster resume operations
+ from the point where it left off.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Node Restart</emphasis>: This is the
- online restart of a cluster node while the cluster itself
- is running.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Node Restart</emphasis>: This is the
+ online restart of a cluster node while the cluster itself is
+ running.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Initial Node Restart</emphasis>:
- This is the same as a node restart, except that the node
- is reinitialized and started with a clean filesystem.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Initial Node Restart</emphasis>: This
+ is the same as a node restart, except that the node is
+ reinitialized and started with a clean filesystem.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
+ </itemizedlist>
<para>
Prior to startup, each data node (<literal>ndbd</literal>
process) must be initialized. This consists of the following:
+ </para>
- <orderedlist>
+ <orderedlist>
- <listitem>
- <para>
- Obtain a Node ID.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Obtain a Node ID.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Fetch configuration data.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Fetch configuration data.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Allocate ports to be used for inter-node communications.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Allocate ports to be used for inter-node communications.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Allocate memory according to settings obtained from the
- configuration file.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Allocate memory according to settings obtained from the
+ configuration file.
+ </para>
+ </listitem>
- </orderedlist>
- </para>
+ </orderedlist>
<para>
Once each data node has been initialized, the cluster startup
process can proceed. The stages which the cluster goes through
during this process are listed here:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Stage 0</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 0</emphasis>
+ </para>
- <para>
- Clear the cluster filesystem. This occurs
- <emphasis>only</emphasis> if the cluster was started with
- the <literal>--initial</literal> option.
- </para>
- </listitem>
+ <para>
+ Clear the cluster filesystem. This occurs
+ <emphasis>only</emphasis> if the cluster was started with
+ the <literal>--initial</literal> option.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 1</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 1</emphasis>
+ </para>
- <para>
- Cluster connections are set up; inter-node communications
- are established. Cluster heartbeats are started.
- </para>
- </listitem>
+ <para>
+ Cluster connections are set up; inter-node communications
+ are established. Cluster heartbeats are started.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 2</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 2</emphasis>
+ </para>
- <para>
- The arbitrator node is elected.
- </para>
+ <para>
+ The arbitrator node is elected.
+ </para>
- <para>
- If this is a system restart, then the cluster determines
- the latest restorable global checkpoint.
- </para>
- </listitem>
+ <para>
+ If this is a system restart, then the cluster determines the
+ latest restorable global checkpoint.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 3</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 3</emphasis>
+ </para>
- <para>
- This stage consists of the initialization of a number of
- internal cluster variables.
- </para>
- </listitem>
+ <para>
+ This stage consists of the initialization of a number of
+ internal cluster variables.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 4</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 4</emphasis>
+ </para>
- <para>
- For an initial start or initial node restart, the redo log
- files are created. The number of these files is equal to
- <literal>NoOfFragmentLogFiles</literal>.
- </para>
+ <para>
+ For an initial start or initial node restart, the redo log
+ files are created. The number of these files is equal to
+ <literal>NoOfFragmentLogFiles</literal>.
+ </para>
- <para>
- For a system restart:
+ <para>
+ For a system restart:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- Read schema or schemas.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Read schema or schemas.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Read data from the local checkpoint and undo logs.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Read data from the local checkpoint and undo logs.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Apply all redo information until the latest
- restorable global checkpoint has been reached.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Apply all redo information until the latest restorable
+ global checkpoint has been reached.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
+ </itemizedlist>
- <para>
- For a node restart, find the tail of the redo log.
- </para>
- </listitem>
+ <para>
+ For a node restart, find the tail of the redo log.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 5</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 5</emphasis>
+ </para>
- <para>
- If this is an initial start, create the
- <literal>SYSTAB_0</literal> and
- <literal>NDB$EVENTS</literal> internal system tables.
- </para>
+ <para>
+ If this is an initial start, create the
+ <literal>SYSTAB_0</literal> and
+ <literal>NDB$EVENTS</literal> internal system tables.
+ </para>
- <para>
- For a node restart or an initial node restart:
+ <para>
+ For a node restart or an initial node restart:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- The node is included in transaction handling
- operations.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The node is included in transaction handling operations.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The node's schema is compared with the
- master' and synchronized with it.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The node's schema is compared with the master'
+ and synchronized with it.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Synchronize data received in the form of
- <literal>INSERT</literal> from the other data nodes
- in this node's node group.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Synchronize data received in the form of
+ <literal>INSERT</literal> from the other data nodes in
+ this node's node group.
+ </para>
+ </listitem>
- <listitem>
- <para>
- In all cases, wait for complete local checkpoint as
- determined by the arbitrator.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ In all cases, wait for complete local checkpoint as
+ determined by the arbitrator.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
- </listitem>
+ </itemizedlist>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 6</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 6</emphasis>
+ </para>
- <para>
- Update internal variables.
- </para>
- </listitem>
+ <para>
+ Update internal variables.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 7</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 7</emphasis>
+ </para>
- <para>
- Update internal variables.
- </para>
- </listitem>
+ <para>
+ Update internal variables.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 8</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 8</emphasis>
+ </para>
- <para>
- In a system restart, rebuild all indexes.
- </para>
- </listitem>
+ <para>
+ In a system restart, rebuild all indexes.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 9</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 9</emphasis>
+ </para>
- <para>
- Update internal variables.
- </para>
- </listitem>
+ <para>
+ Update internal variables.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 10</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 10</emphasis>
+ </para>
- <para>
- At this point in a node restart or initial node restart,
- APIs may connect to the node and being to receive events.
- </para>
- </listitem>
+ <para>
+ At this point in a node restart or initial node restart,
+ APIs may connect to the node and being to receive events.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 11</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 11</emphasis>
+ </para>
- <para>
- At this point in a node restart or initial node restart,
- event delivery is handed over to the node joining the
- cluster. The newly-joined node takes over responsibility
- for delivering its primary data to subscribers.
- </para>
- </listitem>
+ <para>
+ At this point in a node restart or initial node restart,
+ event delivery is handed over to the node joining the
+ cluster. The newly-joined node takes over responsibility for
+ delivering its primary data to subscribers.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
+ </itemizedlist>
<para>
Once this process is completed for an initial start or system
Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml 2006-01-11 18:44:24 UTC (rev 765)
+++ trunk/refman-5.1/ndbcluster.xml 2006-01-11 19:49:43 UTC (rev 766)
@@ -52,42 +52,42 @@
<para>
<emphasis role="bold">Additional resources</emphasis>
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- Answers to some commonly asked questions about Cluster may be
- found in the <xref linkend="mysql-cluster-faq"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Answers to some commonly asked questions about Cluster may be
+ found in the <xref linkend="mysql-cluster-faq"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The MySQL Cluster mailing list:
- <ulink url="http://lists.mysql.com/cluster"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The MySQL Cluster mailing list:
+ <ulink url="http://lists.mysql.com/cluster"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The MySQL Cluster forum:
- <ulink url="http://forums.mysql.com/list.php?25"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The MySQL Cluster forum:
+ <ulink url="http://forums.mysql.com/list.php?25"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- If you are new to MySQL Cluster, you may find our Developer
- Zone article
- <ulink url="http://dev.mysql.com/tech-resources/articles/mysql-cluster-for-two-servers.html">
- How to set up a MySQL Cluster for two servers</ulink> to be
- helpful.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ If you are new to MySQL Cluster, you may find our Developer Zone
+ article
+ <ulink url="http://dev.mysql.com/tech-resources/articles/mysql-cluster-for-two-servers.html">
+ How to set up a MySQL Cluster for two servers</ulink> to be
+ helpful.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
+ </itemizedlist>
<section id="mysql-cluster-overview">
@@ -6158,296 +6158,295 @@
<para>
There are several different startup types and modes, as shown
here:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Initial Start</emphasis>: The
- cluster starts with a clean filesystem on all data nodes.
- This occurs either when the cluster started for the very
- first time, or when it is restarted using the
- <option>--initial</option> option.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Initial Start</emphasis>: The cluster
+ starts with a clean filesystem on all data nodes. This
+ occurs either when the cluster started for the very first
+ time, or when it is restarted using the
+ <option>--initial</option> option.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">System Restart</emphasis>: The
- cluster starts and reads data stored in the data nodes.
- This occurs when the cluster has been shut down after
- having been in use, when it is desired for the cluster
- resume operations from the point where it left off.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">System Restart</emphasis>: The cluster
+ starts and reads data stored in the data nodes. This occurs
+ when the cluster has been shut down after having been in
+ use, when it is desired for the cluster resume operations
+ from the point where it left off.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Node Restart</emphasis>: This is the
- online restart of a cluster node while the cluster itself
- is running.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Node Restart</emphasis>: This is the
+ online restart of a cluster node while the cluster itself is
+ running.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Initial Node Restart</emphasis>:
- This is the same as a node restart, except that the node
- is reinitialized and started with a clean filesystem.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Initial Node Restart</emphasis>: This
+ is the same as a node restart, except that the node is
+ reinitialized and started with a clean filesystem.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
+ </itemizedlist>
<para>
Prior to startup, each data node (<literal>ndbd</literal>
process) must be initialized. This consists of the following:
+ </para>
- <orderedlist>
+ <orderedlist>
- <listitem>
- <para>
- Obtain a Node ID.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Obtain a Node ID.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Fetch configuration data.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Fetch configuration data.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Allocate ports to be used for inter-node communications.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Allocate ports to be used for inter-node communications.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Allocate memory according to settings obtained from the
- configuration file.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Allocate memory according to settings obtained from the
+ configuration file.
+ </para>
+ </listitem>
- </orderedlist>
- </para>
+ </orderedlist>
<para>
Once each data node has been initialized, the cluster startup
process can proceed. The stages which the cluster goes through
during this process are listed here:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Stage 0</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 0</emphasis>
+ </para>
- <para>
- Clear the cluster filesystem. This occurs
- <emphasis>only</emphasis> if the cluster was started with
- the <literal>--initial</literal> option.
- </para>
- </listitem>
+ <para>
+ Clear the cluster filesystem. This occurs
+ <emphasis>only</emphasis> if the cluster was started with
+ the <literal>--initial</literal> option.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 1</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 1</emphasis>
+ </para>
- <para>
- Cluster connections are set up; inter-node communications
- are established. Cluster heartbeats are started.
- </para>
- </listitem>
+ <para>
+ Cluster connections are set up; inter-node communications
+ are established. Cluster heartbeats are started.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 2</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 2</emphasis>
+ </para>
- <para>
- The arbitrator node is elected.
- </para>
+ <para>
+ The arbitrator node is elected.
+ </para>
- <para>
- If this is a system restart, then the cluster determines
- the latest restorable global checkpoint.
- </para>
- </listitem>
+ <para>
+ If this is a system restart, then the cluster determines the
+ latest restorable global checkpoint.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 3</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 3</emphasis>
+ </para>
- <para>
- This stage consists of the initialization of a number of
- internal cluster variables.
- </para>
- </listitem>
+ <para>
+ This stage consists of the initialization of a number of
+ internal cluster variables.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 4</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 4</emphasis>
+ </para>
- <para>
- For an initial start or initial node restart, the redo log
- files are created. The number of these files is equal to
- <literal>NoOfFragmentLogFiles</literal>.
- </para>
+ <para>
+ For an initial start or initial node restart, the redo log
+ files are created. The number of these files is equal to
+ <literal>NoOfFragmentLogFiles</literal>.
+ </para>
- <para>
- For a system restart:
+ <para>
+ For a system restart:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- Read schema or schemas.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Read schema or schemas.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Read data from the local checkpoint and undo logs.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Read data from the local checkpoint and undo logs.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Apply all redo information until the latest
- restorable global checkpoint has been reached.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Apply all redo information until the latest restorable
+ global checkpoint has been reached.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
+ </itemizedlist>
- <para>
- For a node restart, find the tail of the redo log.
- </para>
- </listitem>
+ <para>
+ For a node restart, find the tail of the redo log.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 5</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 5</emphasis>
+ </para>
- <para>
- If this is an initial start, create the
- <literal>SYSTAB_0</literal> and
- <literal>NDB$EVENTS</literal> internal system tables.
- </para>
+ <para>
+ If this is an initial start, create the
+ <literal>SYSTAB_0</literal> and
+ <literal>NDB$EVENTS</literal> internal system tables.
+ </para>
- <para>
- For a node restart or an initial node restart:
+ <para>
+ For a node restart or an initial node restart:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- The node is included in transaction handling
- operations.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The node is included in transaction handling operations.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The node's schema is compared with the
- master' and synchronized with it.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The node's schema is compared with the master'
+ and synchronized with it.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Synchronize data received in the form of
- <literal>INSERT</literal> from the other data nodes
- in this node's node group.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Synchronize data received in the form of
+ <literal>INSERT</literal> from the other data nodes in
+ this node's node group.
+ </para>
+ </listitem>
- <listitem>
- <para>
- In all cases, wait for complete local checkpoint as
- determined by the arbitrator.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ In all cases, wait for complete local checkpoint as
+ determined by the arbitrator.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
- </listitem>
+ </itemizedlist>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 6</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 6</emphasis>
+ </para>
- <para>
- Update internal variables.
- </para>
- </listitem>
+ <para>
+ Update internal variables.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 7</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 7</emphasis>
+ </para>
- <para>
- Update internal variables.
- </para>
- </listitem>
+ <para>
+ Update internal variables.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 8</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 8</emphasis>
+ </para>
- <para>
- In a system restart, rebuild all indexes.
- </para>
- </listitem>
+ <para>
+ In a system restart, rebuild all indexes.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 9</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 9</emphasis>
+ </para>
- <para>
- Update internal variables.
- </para>
- </listitem>
+ <para>
+ Update internal variables.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 10</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 10</emphasis>
+ </para>
- <para>
- At this point in a node restart or initial node restart,
- APIs may connect to the node and being to receive events.
- </para>
- </listitem>
+ <para>
+ At this point in a node restart or initial node restart,
+ APIs may connect to the node and being to receive events.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Stage 11</emphasis>
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Stage 11</emphasis>
+ </para>
- <para>
- At this point in a node restart or initial node restart,
- event delivery is handed over to the node joining the
- cluster. The newly-joined node takes over responsibility
- for delivering its primary data to subscribers.
- </para>
- </listitem>
+ <para>
+ At this point in a node restart or initial node restart,
+ event delivery is handed over to the node joining the
+ cluster. The newly-joined node takes over responsibility for
+ delivering its primary data to subscribers.
+ </para>
+ </listitem>
- </itemizedlist>
- </para>
+ </itemizedlist>
<para>
Once this process is completed for an initial start or system
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r766 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 11 Jan |
