List:Commits« Previous MessageNext Message »
From:jon.stephens Date:February 10 2011 1:31pm
Subject:svn commit - mysqldoc@docsrva: r25053 - trunk/refman-5.1
View as plain text  
Author: jstephens
Date: 2011-02-10 14:31:20 +0100 (Thu, 10 Feb 2011)
New Revision: 25053

Log:

Wording; misc. corrections



Modified:
   trunk/refman-5.1/mysql-cluster-configuration-core.xml
   trunk/refman-5.1/mysql-cluster-overview.xml


Modified: trunk/refman-5.1/mysql-cluster-configuration-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-configuration-core.xml	2011-02-10 12:13:07 UTC (rev 25052)
+++ trunk/refman-5.1/mysql-cluster-configuration-core.xml	2011-02-10 13:31:20 UTC (rev 25053)
Changed blocks: 2, Lines Added: 10, Lines Deleted: 13; 2471 bytes

@@ -7284,15 +7284,13 @@
           <literal role="ndbparam:ndbd">RedoOverCommitCounter</literal>
           times, causing any pending transactions to be aborted. When
           this happens, the API node that sent the transaction can
-          handle the operations that should have committed as part of
-          the aborted transactions, either by queuing the operations and
-          re-trying them, or by aborting them, as determined by the
-          value of its
-          <literal role="ndbparam:api">DefaultOperationRedoProblemAction</literal>
-          configuration parameter. The data node configuration
-          parameters for setting the timeout and number of times it may
-          be exceeeded before the API node take this action are
-          described in the following list:
+          handle the operations that should have been committed either
+          by queuing the operations and re-trying them, or by aborting
+          them, as determined by
+          <literal role="ndbparam:api">DefaultOperationRedoProblemAction</literal>.
+          The data node configuration parameters for setting the timeout
+          and number of times it may be exceeded before the API node
+          takes this action are described in the following list:
         </para>
 
       </formalpara>

@@ -7316,10 +7314,9 @@
             <literal role="ndbparam:ndbd">RedoOverCommitLimit</literal>
             is exceeded when trying to write a given redo log to disk
             this many times or more, any transactions that were not
-            committed as a result of the flush timeout are aborted, and
-            an API node where any of these transactions originated
-            handles the operations making up those transactions
-            according to its value for
+            committed as a result are aborted, and an API node where any
+            of these transactions originated handles the operations
+            making up those transactions according to its value for
             <literal role="ndbparam:api">DefaultOperationRedoProblemAction</literal>
             (by either queuing the operations to be re-tried, or
             aborting them).


Modified: trunk/refman-5.1/mysql-cluster-overview.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-overview.xml	2011-02-10 12:13:07 UTC (rev 25052)
+++ trunk/refman-5.1/mysql-cluster-overview.xml	2011-02-10 13:31:20 UTC (rev 25053)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 3; 901 bytes

@@ -1983,9 +1983,8 @@
             seconds, and this occurs
             <literal role="ndbparam:ndbd">RedoOverCommitLimit</literal>
             times or more, the transactions contained within the redo
-            log are aborted, and any operations left uncommitted as a
-            result of this are either aborted or re-tried, according to
-            the value of
+            log are aborted. Any operations left uncommitted as a result
+            are either aborted or re-tried, according to the value of
             <literal role="ndbparam:api">DefaultOperationRedoProblemAction</literal>.
           </para>
 


Thread
svn commit - mysqldoc@docsrva: r25053 - trunk/refman-5.1jon.stephens10 Feb