List:Commits« Previous MessageNext Message »
From:jon Date:February 2 2006 11:56pm
Subject:svn commit - mysqldoc@docsrva: r1196 - trunk/refman-5.1
View as plain text  
Author: jstephens
Date: 2006-02-03 00:56:49 +0100 (Fri, 03 Feb 2006)
New Revision: 1196

Log:

Make Cluster Replication section public; reformat.



Modified:
   trunk/refman-5.1/ndbcluster.xml

Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml	2006-02-02 22:16:42 UTC (rev 1195)
+++ trunk/refman-5.1/ndbcluster.xml	2006-02-02 23:56:49 UTC (rev 1196)
@@ -3014,7 +3014,7 @@
               available for storing database records. The entire amount
               specified by this value is allocated in memory, so it is
               extremely important that the machine has sufficient
-              physical memory to accommodate it. 
+              physical memory to accommodate it.
             </para>
 
             <remark role="todo">
@@ -4602,8 +4602,8 @@
             </para>
 
             <para>
-              All update activities also need to be logged. The REDO
-              log makes it possible to replay these updates whenever the
+              All update activities also need to be logged. The REDO log
+              makes it possible to replay these updates whenever the
               system is restarted. The NDB recovery algorithm uses a
               <quote>fuzzy</quote> checkpoint of the data together with
               the UNDO log, and then applies the REDO log to play back
@@ -5070,8 +5070,8 @@
               To identify a connection between two nodes it is necessary
               to provide their node IDs in the <literal>[TCP]</literal>
               section of the configuration file. These are the same
-              unique <literal>Id</literal> values for each of these nodes
-              as described in 
+              unique <literal>Id</literal> values for each of these
+              nodes as described in
               <xref linkend="mysql-cluster-api-definition"/>.
             </para>
           </listitem>
@@ -5343,7 +5343,7 @@
           The <replaceable>path</replaceable> should point to a
           directory that contains at a minimum <filename>lib</filename>
           and <filename>include</filename> directories containing SISCI
-          libraries and header files. (See 
+          libraries and header files. (See
           <xref linkend="mysql-cluster-interconnects"/> for more
           information about SCI.)
         </para>
@@ -5517,35 +5517,35 @@
       cluster, how to use them, and what startup options are available
       for each of them:
     </para>
-    
+
     <itemizedlist>
-      
+
       <listitem>
         <para>
           <xref linkend="mysqld-process"/>
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <xref linkend="ndbd-process"/>
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <xref linkend="ndb-mgmd-process"/>
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <xref linkend="ndb-mgm-process"/>
         </para>
       </listitem>
+
     </itemizedlist>
-    
-    
+
     <section id="mysqld-process">
 
       <title>&title-mysqld-process;</title>
@@ -5895,9 +5895,9 @@
         The following files are created or used by
         <command>ndb_mgmd</command> in its starting directory, and are
         placed in the <literal>DataDir</literal> as specified in the
-        <filename>config.ini</filename> configuration file. In the list that follows,
-        <replaceable>node_id</replaceable> is the unique node
-        identifier.
+        <filename>config.ini</filename> configuration file. In the list
+        that follows, <replaceable>node_id</replaceable> is the unique
+        node identifier.
       </para>
 
       <itemizedlist>
@@ -6115,8 +6115,9 @@
             Cluster processes verifies that the versions of the binaries
             being used can co-exist in the same cluster. This is also
             important when performing an online software upgrade of
-            MySQL Cluster. 
-            <!-- (See <literal>Software Upgrade of MySQL
+            MySQL Cluster.
+
+<!-- (See <literal>Software Upgrade of MySQL
             Cluster</literal>). -->
           </para>
         </listitem>
@@ -8331,14 +8332,6 @@
 
   </section>
 
-<!-- 
-  
-    CLUSTER REPLICATION SECTION COMMENTED OUT TFN  //JS
-  
-  -->
-
-<!--  
-
   <section id="mysql-cluster-replication">
 
     <title>&title-mysql-cluster-replication;</title>
@@ -9985,8 +9978,6 @@
 
   </section>
 
--->
-
   <section id="mysql-cluster-interconnects">
 
     <title>&title-mysql-cluster-interconnects;</title>
@@ -11670,11 +11661,11 @@
         </para>
 
         <para>
-          MySQL Cluster is officially
-          supported on Linux, Mac OS X, and Solaris. We are working to
-          add Cluster support for other platforms, including Windows,
-          and our goal is eventually to offer MySQL Cluster on all
-          platforms for which MySQL itself is supported.
+          MySQL Cluster is officially supported on Linux, Mac OS X, and
+          Solaris. We are working to add Cluster support for other
+          platforms, including Windows, and our goal is eventually to
+          offer MySQL Cluster on all platforms for which MySQL itself is
+          supported.
         </para>
 
         <para>

Thread
svn commit - mysqldoc@docsrva: r1196 - trunk/refman-5.1jon3 Feb