svn commit - mysqldoc@docsrva: r3671 - in trunk: refman-4.1 refman-5.0 refman-5.1

[jon]

Author: jstephens
Date: 2006-10-18 12:58:36 +0200 (Wed, 18 Oct 2006)
New Revision: 3671

Log:

Reworded description of NoOfFragmentLogFiles, as suggested by Roland.



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-10-18 10:31:58 UTC (rev 3670)
+++ trunk/refman-4.1/mysql-cluster.xml	2006-10-18 10:58:36 UTC (rev 3671)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 8; 1539 bytes

@@ -4401,14 +4401,16 @@
             </para>
 
             <para>
-              This parameter sets the size of the node's REDO log files.
-              REDO log files are organized in a ring. It is extremely
-              important that the first and last log files (sometimes
-              referred to as the <quote>head</quote> and
-              <quote>tail</quote> log files, respectively) do not meet.
-              When these approach one another too closely, the node
-              begins aborting all transactions encompassing updates due
-              to a lack of room for new log records.
+              This parameter sets the number of REDO log files for the
+              node, and thus the amount of space allocated to REDO
+              logging. Because the REDO log files are organized in a
+              ring, it is extremely important that the first and last
+              log files in the set (sometimes referred to as the
+              <quote>head</quote> and <quote>tail</quote> log
files,
+              respectively) do not meet. When these approach one another
+              too closely, the node begins aborting all transactions
+              encompassing updates due to a lack of room for new log
+              records.
             </para>
 
             <para>


Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml	2006-10-18 10:31:58 UTC (rev 3670)
+++ trunk/refman-5.0/mysql-cluster.xml	2006-10-18 10:58:36 UTC (rev 3671)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 8; 1539 bytes

@@ -4379,14 +4379,16 @@
             </para>
 
             <para>
-              This parameter sets the size of the node's REDO log files.
-              REDO log files are organized in a ring. It is extremely
-              important that the first and last log files (sometimes
-              referred to as the <quote>head</quote> and
-              <quote>tail</quote> log files, respectively) do not meet.
-              When these approach one another too closely, the node
-              begins aborting all transactions encompassing updates due
-              to a lack of room for new log records.
+              This parameter sets the number of REDO log files for the
+              node, and thus the amount of space allocated to REDO
+              logging. Because the REDO log files are organized in a
+              ring, it is extremely important that the first and last
+              log files in the set (sometimes referred to as the
+              <quote>head</quote> and <quote>tail</quote> log
files,
+              respectively) do not meet. When these approach one another
+              too closely, the node begins aborting all transactions
+              encompassing updates due to a lack of room for new log
+              records.
             </para>
 
             <para>


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2006-10-18 10:31:58 UTC (rev 3670)
+++ trunk/refman-5.1/mysql-cluster.xml	2006-10-18 10:58:36 UTC (rev 3671)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 8; 1539 bytes

@@ -4380,14 +4380,16 @@
             </para>
 
             <para>
-              This parameter sets the size of the node's REDO log files.
-              REDO log files are organized in a ring. It is extremely
-              important that the first and last log files (sometimes
-              referred to as the <quote>head</quote> and
-              <quote>tail</quote> log files, respectively) do not meet.
-              When these approach one another too closely, the node
-              begins aborting all transactions encompassing updates due
-              to a lack of room for new log records.
+              This parameter sets the number of REDO log files for the
+              node, and thus the amount of space allocated to REDO
+              logging. Because the REDO log files are organized in a
+              ring, it is extremely important that the first and last
+              log files in the set (sometimes referred to as the
+              <quote>head</quote> and <quote>tail</quote> log
files,
+              respectively) do not meet. When these approach one another
+              too closely, the node begins aborting all transactions
+              encompassing updates due to a lack of room for new log
+              records.
             </para>
 
             <para>