List:Commits« Previous MessageNext Message »
From:jon Date:August 9 2006 2:51pm
Subject:svn commit - mysqldoc@docsrva: r2982 - in trunk: refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: jstephens
Date: 2006-08-09 16:51:44 +0200 (Wed, 09 Aug 2006)
New Revision: 2982

Log:
Reformat.

Modified:
   trunk/refman-4.1/mysql-cluster.xml
   trunk/refman-5.0/mysql-cluster.xml
   trunk/refman-5.1/mysql-cluster.xml


Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml	2006-08-09 14:43:05 UTC (rev 2981)
+++ trunk/refman-4.1/mysql-cluster.xml	2006-08-09 14:51:44 UTC (rev 2982)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1252 bytes

@@ -5281,7 +5281,7 @@
               engine issues internal error code 677 (<literal>Index UNDO
               buffers overloaded</literal>).
             </para>
-            
+
             <para>
               <emphasis role="bold">Important</emphasis>: It is not safe
               to decrease the value of this parameter during a rolling

@@ -5333,7 +5333,7 @@
               storage engine issues internal error code 891
               (<errortext>Data UNDO buffers overloaded</errortext>).
             </para>
-            
+
             <para>
               <emphasis role="bold">Important</emphasis>: It is not safe
               to decrease the value of this parameter during a rolling

@@ -5370,7 +5370,7 @@
               error code 1221 (<literal>REDO log buffers
               overloaded</literal>).
             </para>
-            
+
             <para>
               <emphasis role="bold">Important</emphasis>: It is not safe
               to decrease the value of this parameter during a rolling


Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml	2006-08-09 14:43:05 UTC (rev 2981)
+++ trunk/refman-5.0/mysql-cluster.xml	2006-08-09 14:51:44 UTC (rev 2982)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1252 bytes

@@ -5264,7 +5264,7 @@
               engine issues internal error code 677 (<literal>Index UNDO
               buffers overloaded</literal>).
             </para>
-            
+
             <para>
               <emphasis role="bold">Important</emphasis>: It is not safe
               to decrease the value of this parameter during a rolling

@@ -5316,7 +5316,7 @@
               storage engine issues internal error code 891
               (<errortext>Data UNDO buffers overloaded</errortext>).
             </para>
-            
+
             <para>
               <emphasis role="bold">Important</emphasis>: It is not safe
               to decrease the value of this parameter during a rolling

@@ -5353,7 +5353,7 @@
               error code 1221 (<literal>REDO log buffers
               overloaded</literal>).
             </para>
-            
+
             <para>
               <emphasis role="bold">Important</emphasis>: It is not safe
               to decrease the value of this parameter during a rolling


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2006-08-09 14:43:05 UTC (rev 2981)
+++ trunk/refman-5.1/mysql-cluster.xml	2006-08-09 14:51:44 UTC (rev 2982)
Changed blocks: 2, Lines Added: 44, Lines Deleted: 44; 4773 bytes

@@ -5207,60 +5207,60 @@
           <emphasis role="bold">Buffering and Logging</emphasis>
         </para>
 
-          
-            <indexterm>
-              <primary><literal>RedoBuffer</literal></primary>
-            </indexterm>
+        <indexterm>
+          <primary><literal>RedoBuffer</literal></primary>
+        </indexterm>
 
-            <para id="mysql-cluster-param-ndbd-definition-redobuffer">
-              <literal>RedoBuffer</literal>
-            </para>
+        <para id="mysql-cluster-param-ndbd-definition-redobuffer">
+          <literal>RedoBuffer</literal>
+        </para>
 
-            <para>
-              All update activities 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
-              all changes up to the restoration point.
-            </para>
+        <para>
+          All update activities 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 all
+          changes up to the restoration point.
+        </para>
 
-            <para>
-              <literal>RedoBuffer</literal> sets the size of the buffer
-              inwhich the REDO log is written, and is 8MB by default.
-          This buffer is used as a front end to the file system when
-              writing REDO log records to disk. If this buffer is too
-              small, the <literal>NDB</literal> storage engine issues 
-              error code 1221 (<literal>REDO log buffers
-              overloaded</literal>).
-            </para>
         <para>
-              The minimum value is 1MB. If the node is running in
-          diskless mode, these parameters can be set to their minimum
-          values without penalty due to the fact that disk writes are
+          <literal>RedoBuffer</literal> sets the size of the buffer
+          inwhich the REDO log is written, and is 8MB by default. This
+          buffer is used as a front end to the file system when writing
+          REDO log records to disk. If this buffer is too small, the
+          <literal>NDB</literal> storage engine issues error code 1221
+          (<literal>REDO log buffers overloaded</literal>).
+        </para>
+
+        <para>
+          The minimum value is 1MB. If the node is running in diskless
+          mode, these parameters can be set to their minimum values
+          without penalty due to the fact that disk writes are
           <quote>faked</quote> by the <literal>NDB</literal> storage
           engine's filesystem abstraction layer.
-            </para>
-            
-            <para>
-              <emphasis role="bold">Important</emphasis>: It is not safe
-              to decrease the value of this parameter during a rolling
-              restart.
-            </para>
-            <indexterm>
-              <primary><literal>UndoDataBuffer</literal></primary>
-            </indexterm>
-            <indexterm>
-              <primary><literal>UndoIndexBuffer</literal></primary>
-            </indexterm>
-        
+        </para>
+
         <para>
+          <emphasis role="bold">Important</emphasis>: It is not safe to
+          decrease the value of this parameter during a rolling restart.
+        </para>
+
+        <indexterm>
+          <primary><literal>UndoDataBuffer</literal></primary>
+        </indexterm>
+
+        <indexterm>
+          <primary><literal>UndoIndexBuffer</literal></primary>
+        </indexterm>
+
+        <para>
           <emphasis role="bold">Note</emphasis>: The
           <literal>UndoIndexBuffer</literal> and
           <literal>UndoDataBuffer</literal> parameters which appeared in
           earlier versions of MySQL Cluster are no longer necessary (or
-          even present) in MySQL 5.1. 
-        </para>        
+          even present) in MySQL 5.1.
+        </para>
 
         <para id="mysql-cluster-controlling-log-messages">
           <emphasis role="bold">Controlling Log Messages</emphasis>

@@ -12463,7 +12463,7 @@
             which they are issued.
           </para>
         </listitem>
-        
+
         <listitem>
           <para>
             In MySQL 5.1.6, only those <literal>NDB</literal> tables


Thread
svn commit - mysqldoc@docsrva: r2982 - in trunk: refman-4.1 refman-5.0 refman-5.1jon9 Aug