Author: lgrimmer
Date: 2006-11-01 16:35:07 +0100 (Wed, 01 Nov 2006)
New Revision: 3818
Log:
- Fixed two typos in the Cluster FAQ: "cuase"->"cause", "hearbeats"->"heartbeats"
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-11-01 12:17:27 UTC (rev 3817)
+++ trunk/refman-4.1/mysql-cluster.xml 2006-11-01 15:35:07 UTC (rev 3818)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 994 bytes
@@ -16917,8 +16917,8 @@
RAM, then the system will attempt to use swap space up to the
limit set for <literal>DataMemory</literal>. However, this
will at best result in severely degraded performance, and may
- cuase the node to be dropped due to slow response time (missed
- hearbeats). We do not recommend on relying on disk swapping in
+ cause the node to be dropped due to slow response time (missed
+ heartbeats). We do not recommend on relying on disk swapping in
a production environment for this reason. In any case, once
the <literal>DataMemory</literal> limit is reached, any
operations requiring additional memory (such as inserts) will
Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml 2006-11-01 12:17:27 UTC (rev 3817)
+++ trunk/refman-5.0/mysql-cluster.xml 2006-11-01 15:35:07 UTC (rev 3818)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 994 bytes
@@ -17277,8 +17277,8 @@
RAM, then the system will attempt to use swap space up to the
limit set for <literal>DataMemory</literal>. However, this
will at best result in severely degraded performance, and may
- cuase the node to be dropped due to slow response time (missed
- hearbeats). We do not recommend on relying on disk swapping in
+ cause the node to be dropped due to slow response time (missed
+ heartbeats). We do not recommend on relying on disk swapping in
a production environment for this reason. In any case, once
the <literal>DataMemory</literal> limit is reached, any
operations requiring additional memory (such as inserts) will
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2006-11-01 12:17:27 UTC (rev 3817)
+++ trunk/refman-5.1/mysql-cluster.xml 2006-11-01 15:35:07 UTC (rev 3818)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 994 bytes
@@ -19796,8 +19796,8 @@
RAM, then the system will attempt to use swap space up to the
limit set for <literal>DataMemory</literal>. However, this
will at best result in severely degraded performance, and may
- cuase the node to be dropped due to slow response time (missed
- hearbeats). We do not recommend on relying on disk swapping in
+ cause the node to be dropped due to slow response time (missed
+ heartbeats). We do not recommend on relying on disk swapping in
a production environment for this reason. In any case, once
the <literal>DataMemory</literal> limit is reached, any
operations requiring additional memory (such as inserts) will
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3818 - in trunk: refman-4.1 refman-5.0 refman-5.1 | lgrimmer | 1 Nov |
