Author: jstephens
Date: 2007-07-12 17:30:02 +0200 (Thu, 12 Jul 2007)
New Revision: 7099
Log:
Documented behaviour change for TransactionDeadlockDetectionTimeout
config parameter (see WL#2610) (Tomas)
Modified:
trunk/refman-4.1/mysql-cluster.xml
trunk/refman-5.0/mysql-cluster.xml
trunk/refman-5.1/mysql-cluster.xml
trunk/refman-5.2/mysql-cluster.xml
Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml 2007-07-12 15:14:35 UTC (rev 7098)
+++ trunk/refman-4.1/mysql-cluster.xml 2007-07-12 15:30:02 UTC (rev 7099)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 3; 1229 bytes
@@ -5434,9 +5434,14 @@
This timeout parameter states how long the transaction
coordinator waits for query execution by another node
before aborting the transaction, and is important for both
- node failure handling and deadlock detection. Setting it
- too high can cause a undesirable behavior in situations
- involving deadlocks and node failure.
+ node failure handling and deadlock detection. In MySQL
+ 4.1.18 and earlier versions, setting it too high could
+ cause undesirable behavior in situations involving
+ deadlocks and node failure. Beginning with MySQL 4.1.19,
+ active transactions occurring during node failures are
+ actively aborted by the Cluster Transaction Coordinator,
+ and so high settings are no longer an issue with this
+ parameter.
</para>
<para>
Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml 2007-07-12 15:14:35 UTC (rev 7098)
+++ trunk/refman-5.0/mysql-cluster.xml 2007-07-12 15:30:02 UTC (rev 7099)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 3; 1229 bytes
@@ -5383,9 +5383,14 @@
This timeout parameter states how long the transaction
coordinator waits for query execution by another node
before aborting the transaction, and is important for both
- node failure handling and deadlock detection. Setting it
- too high can cause a undesirable behavior in situations
- involving deadlocks and node failure.
+ node failure handling and deadlock detection. In MySQL
+ 5.1.20 and earlier versions, setting it too high could
+ cause undesirable behavior in situations involving
+ deadlocks and node failure. Beginning with MySQL 5.0.21,
+ active transactions occurring during node failures are
+ actively aborted by the Cluster Transaction Coordinator,
+ and so high settings are no longer an issue with this
+ parameter.
</para>
<para>
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-07-12 15:14:35 UTC (rev 7098)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-07-12 15:30:02 UTC (rev 7099)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 3; 1229 bytes
@@ -6320,9 +6320,14 @@
This timeout parameter states how long the transaction
coordinator waits for query execution by another node
before aborting the transaction, and is important for both
- node failure handling and deadlock detection. Setting it
- too high can cause a undesirable behavior in situations
- involving deadlocks and node failure.
+ node failure handling and deadlock detection. In MySQL
+ 5.1.10 and earlier versions, setting it too high could
+ cause undesirable behavior in situations involving
+ deadlocks and node failure. Beginning with MySQL 5.1.11,
+ active transactions occurring during node failures are
+ actively aborted by the Cluster Transaction Coordinator,
+ and so high settings are no longer an issue with this
+ parameter.
</para>
<para>
Modified: trunk/refman-5.2/mysql-cluster.xml
===================================================================
--- trunk/refman-5.2/mysql-cluster.xml 2007-07-12 15:14:35 UTC (rev 7098)
+++ trunk/refman-5.2/mysql-cluster.xml 2007-07-12 15:30:02 UTC (rev 7099)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 3; 781 bytes
@@ -5762,9 +5762,7 @@
This timeout parameter states how long the transaction
coordinator waits for query execution by another node
before aborting the transaction, and is important for both
- node failure handling and deadlock detection. Setting it
- too high can cause a undesirable behavior in situations
- involving deadlocks and node failure.
+ node failure handling and deadlock detection.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7099 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-5.2 | jon | 12 Jul |
