From: jon
Date: June 21 2006 4:27am
Subject: svn commit - mysqldoc@docsrva: r2450 - in trunk: refman-4.1 refman-5.0 refman-5.1
List-Archive: http://lists.mysql.com/commits/7981
Message-Id: <200606210427.k5L4Rh9R031747@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2006-06-21 06:27:40 +0200 (Wed, 21 Jun 2006)
New Revision: 2450

Log:
Reformat.

Modified:
   trunk/refman-4.1/ndbcluster.xml
   trunk/refman-5.0/ndbcluster.xml
   trunk/refman-5.1/ndbcluster.xml

Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml	2006-06-21 04:26:19 UTC (rev 2449)
+++ trunk/refman-4.1/ndbcluster.xml	2006-06-21 04:27:40 UTC (rev 2450)
@@ -3553,15 +3553,16 @@
               there are the same number of fragments as are set in
               <literal>NoOfReplicas</literal>.
             </para>
-            
-            <para>Once a page has been
-              allocated, it is currently not possible to return it to
-              the pool of free pages, except by deleting the table.
-              (This also means that <literal>DataMemory</literal> pages,
-              once allocated to a given table, cannot be used by other
-              tables.) Performing a node recovery also compresses the
-              partition because all records are inserted into empty
-              partitions from other live nodes.
+
+            <para>
+              Once a page has been allocated, it is currently not
+              possible to return it to the pool of free pages, except by
+              deleting the table. (This also means that
+              <literal>DataMemory</literal> pages, once allocated to a
+              given table, cannot be used by other tables.) Performing a
+              node recovery also compresses the partition because all
+              records are inserted into empty partitions from other live
+              nodes.
             </para>
 
             <para>
@@ -6415,7 +6416,7 @@
 
     </section>
 
-    <!--<section id="mysql-cluster-config-params-overview">
+<!--<section id="mysql-cluster-config-params-overview">
 
       <title>&title-mysql-cluster-config-params-overview;</title>
 
@@ -9267,7 +9268,7 @@
         </listitem>
 
       </orderedlist>
-      
+
       <para>
         When a data node or SQL node first connects to the management
         node, it reserves a cluster node ID. To make sure that no other
@@ -9277,7 +9278,7 @@
         This retention of the node ID is guarded by the connection
         between the node in question and <command>ndb_mgmd</command>.
       </para>
-      
+
       <para>
         Normally, in the event of a problem with the node, the node
         disconnects from the management server, the socket used for the
@@ -9289,16 +9290,16 @@
         the node ID continues to be reserved and not released until a
         TCP timeout occurs 10 or so minutes later.
       </para>
-      
+
       <indexterm>
         <primary><literal>PURGE STALE SESSIONS</literal></primary>
       </indexterm>
-      
+
       <para>
         To take care of this problem, you can use <literal>PURGE STALE
-          SESSIONS</literal>. Running this statement forces all reserved
-        node IDs to be checked; any that are not being used by
-        nodes actually connected to the cluster are then freed.
+        SESSIONS</literal>. Running this statement forces all reserved
+        node IDs to be checked; any that are not being used by nodes
+        actually connected to the cluster are then freed.
       </para>
 
       <para>
@@ -12842,18 +12843,20 @@
                   (<literal>DataMemory</literal> and
                   <literal>IndexMemory</literal>, respectively).
                 </para>
-                
+
                 <para>
                   <literal>DataMemory</literal> is allocated as 32KB
                   pages. As each <literal>DataMemory</literal> page is
                   used, it is assigned to a specific table; once
                   allocated, this memory cannot be freed except by
-                  deleting the table. 
+                  deleting the table.
                 </para>
-                
+
                 <para>
                   See <xref linkend="mysql-cluster-db-definition"/>, for
-                  further information about <literal>DataMemory</literal> and <literal>IndexMemory</literal>.
+                  further information about
+                  <literal>DataMemory</literal> and
+                  <literal>IndexMemory</literal>.
                 </para>
               </listitem>
 

Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml	2006-06-21 04:26:19 UTC (rev 2449)
+++ trunk/refman-5.0/ndbcluster.xml	2006-06-21 04:27:40 UTC (rev 2450)
@@ -3540,15 +3540,16 @@
               there are the same number of fragments as are set in
               <literal>NoOfReplicas</literal>.
             </para>
-            
-            <para>Once a page has been
-              allocated, it is currently not possible to return it to
-              the pool of free pages, except by deleting the table.
-              (This also means that <literal>DataMemory</literal> pages,
-              once allocated to a given table, cannot be used by other
-              tables.) Performing a node recovery also compresses the
-              partition because all records are inserted into empty
-              partitions from other live nodes.
+
+            <para>
+              Once a page has been allocated, it is currently not
+              possible to return it to the pool of free pages, except by
+              deleting the table. (This also means that
+              <literal>DataMemory</literal> pages, once allocated to a
+              given table, cannot be used by other tables.) Performing a
+              node recovery also compresses the partition because all
+              records are inserted into empty partitions from other live
+              nodes.
             </para>
 
             <para>
@@ -6410,7 +6411,7 @@
 
     </section>
 
-    <!--<section id="mysql-cluster-config-params-overview">
+<!--<section id="mysql-cluster-config-params-overview">
 
       <title>&title-mysql-cluster-config-params-overview;</title>
 
@@ -8927,70 +8928,69 @@
               already been created by the affected node.
             </para>
           </listitem>
-          
+
           <listitem>
             <para>
               <option>--initial-start</option>
             </para>
-            
+
             <para>
               This option is used when performing a partial initial
               start of the cluster. Each node should be started with
               this option, as well as <option>--no-wait-nodes</option>.
             </para>
-            
+
             <para>
               For example, suppose you have a 4-node cluster whose data
               nodes have the IDs 2, 3, 4, and 5, and you wish to perform
               a partial initial start using only nodes 2, 4, and 5
               &mdash; that is, omitting node 3:
             </para>
-            
+
 <programlisting>
 ndbd --ndbd-nodeid=2 --no-wait-nodes=3 --initial-start
 ndbd --ndbd-nodeid=4 --no-wait-nodes=3 --initial-start
 ndbd --ndbd-nodeid=5 --no-wait-nodes=3 --initial-start
 </programlisting>
-            
+
             <para>
               This option was added in MySQL 5.0.21.
             </para>
           </listitem>
-          
+
           <listitem>
             <para>
               <option>--nowait-nodes=<replaceable>node_id_1</replaceable>[,
-                <replaceable>node_id_2</replaceable>[, ...]]</option>
+              <replaceable>node_id_2</replaceable>[, ...]]</option>
             </para>
-            
+
             <para>
               This option takes a list of data nodes which for which the
               cluster will not wait for before starting.
             </para>
-            
+
             <para>
-              This can be used to start the cluster in a
-              partitioned state. For example, to start the cluster with
-              only half of the data nodes (nodes 2, 3, 4, and 5) running
-              in a 4-node cluster, you can start each
-              <command>ndbd</command> process with
-              <option>--nowait-nodes=3,5</option>. In this case, the
-              cluster starts as soon as nodes 2 and 4 connect, and does
-              <emphasis>not</emphasis> wait
+              This can be used to start the cluster in a partitioned
+              state. For example, to start the cluster with only half of
+              the data nodes (nodes 2, 3, 4, and 5) running in a 4-node
+              cluster, you can start each <command>ndbd</command>
+              process with <option>--nowait-nodes=3,5</option>. In this
+              case, the cluster starts as soon as nodes 2 and 4 connect,
+              and does <emphasis>not</emphasis> wait
               <literal>StartPartitionedTimeout</literal> milliseconds
               for nodes 3 and 5 to connect as it would otherwise.
             </para>
-            
+
             <para>
               If you wanted to start up the same cluster as in the
               previous example without one <command>ndbd</command>
-              &mdash; say, for example, that the host machine for node
-              3 has suffered a hardware failure &mdash; then start
-              nodes 2, 4, and 5 with <option>--no-wait-nodes=3</option>.
-              Then the cluster will start as soon as nodes 2, 4, and 5
+              &mdash; say, for example, that the host machine for node 3
+              has suffered a hardware failure &mdash; then start nodes
+              2, 4, and 5 with <option>--no-wait-nodes=3</option>. Then
+              the cluster will start as soon as nodes 2, 4, and 5
               connect and will not wait for node 3 to start.
             </para>
-            
+
             <para>
               This option was added in MySQL 5.0.21.
             </para>
@@ -9297,7 +9297,7 @@
         </listitem>
 
       </orderedlist>
-      
+
       <para>
         When a data node or SQL node first connects to the management
         node, it reserves a cluster node ID. To make sure that no other
@@ -9307,7 +9307,7 @@
         This retention of the node ID is guarded by the connection
         between the node in question and <command>ndb_mgmd</command>.
       </para>
-      
+
       <para>
         Normally, in the event of a problem with the node, the node
         disconnects from the management server, the socket used for the
@@ -9319,18 +9319,18 @@
         the node ID continues to be reserved and not released until a
         TCP timeout occurs 10 or so minutes later.
       </para>
-      
+
       <indexterm>
         <primary><literal>PURGE STALE SESSIONS</literal></primary>
       </indexterm>
-      
+
       <para>
         To take care of this problem, you can use <literal>PURGE STALE
-          SESSIONS</literal>. Running this statement forces all reserved
-        node IDs to be checked; any that are not being used by
-        nodes actually connected to the cluster are then freed.
+        SESSIONS</literal>. Running this statement forces all reserved
+        node IDs to be checked; any that are not being used by nodes
+        actually connected to the cluster are then freed.
       </para>
-      
+
       <para>
         Beginning with MySQL 5.0.22, timeout handling of node ID
         assignments is implemented. This performs the ID usage checks
@@ -12894,18 +12894,20 @@
                   (<literal>DataMemory</literal> and
                   <literal>IndexMemory</literal>, respectively).
                 </para>
-                
+
                 <para>
                   <literal>DataMemory</literal> is allocated as 32KB
                   pages. As each <literal>DataMemory</literal> page is
                   used, it is assigned to a specific table; once
                   allocated, this memory cannot be freed except by
-                  deleting the table. 
+                  deleting the table.
                 </para>
-                
+
                 <para>
                   See <xref linkend="mysql-cluster-db-definition"/>, for
-                  further information about <literal>DataMemory</literal> and <literal>IndexMemory</literal>.
+                  further information about
+                  <literal>DataMemory</literal> and
+                  <literal>IndexMemory</literal>.
                 </para>
               </listitem>
 

Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml	2006-06-21 04:26:19 UTC (rev 2449)
+++ trunk/refman-5.1/ndbcluster.xml	2006-06-21 04:27:40 UTC (rev 2450)
@@ -3540,15 +3540,16 @@
               there are the same number of fragments as are set in
               <literal>NoOfReplicas</literal>.
             </para>
-            
-            <para>Once a page has been
-              allocated, it is currently not possible to return it to
-              the pool of free pages, except by deleting the table.
-              (This also means that <literal>DataMemory</literal> pages,
-              once allocated to a given table, cannot be used by other
-              tables.) Performing a node recovery also compresses the
-              partition because all records are inserted into empty
-              partitions from other live nodes.
+
+            <para>
+              Once a page has been allocated, it is currently not
+              possible to return it to the pool of free pages, except by
+              deleting the table. (This also means that
+              <literal>DataMemory</literal> pages, once allocated to a
+              given table, cannot be used by other tables.) Performing a
+              node recovery also compresses the partition because all
+              records are inserted into empty partitions from other live
+              nodes.
             </para>
 
             <para>
@@ -6415,7 +6416,7 @@
 
     </section>
 
-    <!--<section id="mysql-cluster-config-params-overview">
+<!--<section id="mysql-cluster-config-params-overview">
 
       <title>&title-mysql-cluster-config-params-overview;</title>
 
@@ -8927,70 +8928,69 @@
               already been created by the affected node.
             </para>
           </listitem>
-          
+
           <listitem>
             <para>
               <option>--initial-start</option>
             </para>
-            
+
             <para>
               This option is used when performing a partial initial
               start of the cluster. Each node should be started with
               this option, as well as <option>--no-wait-nodes</option>.
             </para>
-            
+
             <para>
               For example, suppose you have a 4-node cluster whose data
               nodes have the IDs 2, 3, 4, and 5, and you wish to perform
               a partial initial start using only nodes 2, 4, and 5
               &mdash; that is, omitting node 3:
             </para>
-            
+
 <programlisting>
 ndbd --ndbd-nodeid=2 --no-wait-nodes=3 --initial-start
 ndbd --ndbd-nodeid=4 --no-wait-nodes=3 --initial-start
 ndbd --ndbd-nodeid=5 --no-wait-nodes=3 --initial-start
 </programlisting>
-            
+
             <para>
               This option was added in MySQL 5.1.9.
             </para>
           </listitem>
-          
+
           <listitem>
             <para>
               <option>--nowait-nodes=<replaceable>node_id_1</replaceable>[,
-                <replaceable>node_id_2</replaceable>[, ...]]</option>
+              <replaceable>node_id_2</replaceable>[, ...]]</option>
             </para>
-            
+
             <para>
               This option takes a list of data nodes which for which the
               cluster will not wait for before starting.
             </para>
-            
+
             <para>
-              This can be used to start the cluster in a
-              partitioned state. For example, to start the cluster with
-              only half of the data nodes (nodes 2, 3, 4, and 5) running
-              in a 4-node cluster, you can start each
-              <command>ndbd</command> process with
-              <option>--nowait-nodes=3,5</option>. In this case, the
-              cluster starts as soon as nodes 2 and 4 connect, and does
-              <emphasis>not</emphasis> wait
+              This can be used to start the cluster in a partitioned
+              state. For example, to start the cluster with only half of
+              the data nodes (nodes 2, 3, 4, and 5) running in a 4-node
+              cluster, you can start each <command>ndbd</command>
+              process with <option>--nowait-nodes=3,5</option>. In this
+              case, the cluster starts as soon as nodes 2 and 4 connect,
+              and does <emphasis>not</emphasis> wait
               <literal>StartPartitionedTimeout</literal> milliseconds
               for nodes 3 and 5 to connect as it would otherwise.
             </para>
-            
+
             <para>
               If you wanted to start up the same cluster as in the
               previous example without one <command>ndbd</command>
-              &mdash; say, for example, that the host machine for node
-              3 has suffered a hardware failure &mdash; then start
-              nodes 2, 4, and 5 with <option>--no-wait-nodes=3</option>.
-              Then the cluster will start as soon as nodes 2, 4, and 5
+              &mdash; say, for example, that the host machine for node 3
+              has suffered a hardware failure &mdash; then start nodes
+              2, 4, and 5 with <option>--no-wait-nodes=3</option>. Then
+              the cluster will start as soon as nodes 2, 4, and 5
               connect and will not wait for node 3 to start.
             </para>
-            
+
             <para>
               This option was added in MySQL 5.1.9.
             </para>
@@ -9297,7 +9297,7 @@
         </listitem>
 
       </orderedlist>
-      
+
       <para>
         When a data node or SQL node first connects to the management
         node, it reserves a cluster node ID. To make sure that no other
@@ -9307,7 +9307,7 @@
         This retention of the node ID is guarded by the connection
         between the node in question and <command>ndb_mgmd</command>.
       </para>
-      
+
       <para>
         Normally, in the event of a problem with the node, the node
         disconnects from the management server, the socket used for the
@@ -9319,18 +9319,18 @@
         the node ID continues to be reserved and not released until a
         TCP timeout occurs 10 or so minutes later.
       </para>
-      
+
       <para>
         To take care of this problem, you can use <literal>PURGE STALE
-          SESSIONS</literal>. Running this statement forces all reserved
-        node IDs to be checked; any that are not being used by
-        nodes actually connected to the cluster are then freed.
+        SESSIONS</literal>. Running this statement forces all reserved
+        node IDs to be checked; any that are not being used by nodes
+        actually connected to the cluster are then freed.
       </para>
-      
+
       <indexterm>
         <primary><literal>PURGE STALE SESSIONS</literal></primary>
       </indexterm>
-      
+
       <para>
         Beginning with MySQL 5.1.11, timeout handling of node ID
         assignments is implemented. This performs the ID usage checks
@@ -15310,18 +15310,20 @@
                   (<literal>DataMemory</literal> and
                   <literal>IndexMemory</literal>, respectively).
                 </para>
-                
+
                 <para>
                   <literal>DataMemory</literal> is allocated as 32KB
                   pages. As each <literal>DataMemory</literal> page is
                   used, it is assigned to a specific table; once
                   allocated, this memory cannot be freed except by
-                  deleting the table. 
+                  deleting the table.
                 </para>
-                
+
                 <para>
                   See <xref linkend="mysql-cluster-db-definition"/>, for
-                  further information about <literal>DataMemory</literal> and <literal>IndexMemory</literal>.
+                  further information about
+                  <literal>DataMemory</literal> and
+                  <literal>IndexMemory</literal>.
                 </para>
               </listitem>