Author: js221926
Date: 2011-05-25 09:18:14 +0200 (Wed, 25 May 2011)
New Revision: 26330
Log:
Fixed errors in data node parameter descriptions (Thanks, MMontgomery!)
Modified:
trunk/refman-5.0/mysql-cluster-configuration-core.xml
trunk/refman-5.1/mysql-cluster-configuration-core.xml
Modified: trunk/refman-5.0/mysql-cluster-configuration-core.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster-configuration-core.xml 2011-05-24 17:13:41 UTC (rev 26329)
+++ trunk/refman-5.0/mysql-cluster-configuration-core.xml 2011-05-25 07:18:14 UTC (rev 26330)
Changed blocks: 3, Lines Added: 11, Lines Deleted: 10; 1868 bytes
@@ -2410,8 +2410,8 @@
<para>
The default value is 64; this value has a strong connection
- to the <literal>ScanBatchSize</literal> defined in the SQL
- nodes.
+ to the <literal role="ndbparam:api">BatchSize</literal>
+ defined in the SQL nodes.
</para>
</listitem>
@@ -3305,11 +3305,11 @@
</listitem>
<listitem>
- <indexterm>
- <primary>TransactionInactiveTimeout (MySQL Cluster configuration parameter)</primary>
- </indexterm>
+ <para id="ndbparam-ndbd-transactioninactivetimeout">
+ <indexterm>
+ <primary>TransactionInactiveTimeout</primary>
+ </indexterm>
- <para id="ndbparam-ndbd-transactioninactivetimeout">
<literal>TransactionInactiveTimeout</literal>
</para>
@@ -3322,10 +3322,11 @@
</para>
<para>
- The default for this parameter is zero (no timeout). For a
- real-time database that needs to ensure that no transaction
- keeps locks for too long, this parameter should be set to a
- relatively small value. The unit is milliseconds.
+ The default for this parameter is <literal>4G</literal>
+ (also the maximum). For a real-time database that needs to
+ ensure that no transaction keeps locks for too long, this
+ parameter should be set to a relatively small value. The
+ unit is milliseconds.
</para>
</listitem>
Modified: trunk/refman-5.1/mysql-cluster-configuration-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-configuration-core.xml 2011-05-24 17:13:41 UTC (rev 26329)
+++ trunk/refman-5.1/mysql-cluster-configuration-core.xml 2011-05-25 07:18:14 UTC (rev 26330)
Changed blocks: 3, Lines Added: 8, Lines Deleted: 7; 1751 bytes
@@ -1943,7 +1943,7 @@
<para>
When setting this parameter, you must specify a policy. This
- is one of <literal>FIFO</literal> (first in, first in) or
+ is one of <literal>FIFO</literal> (first in, first out) or
<literal>RR</literal> (round robin). The policy value is
followed optionally by the priority (an integer).
</para>
@@ -3312,8 +3312,8 @@
<para>
The default value is 64; this value has a strong connection
- to the <literal>ScanBatchSize</literal> defined in the SQL
- nodes.
+ to the <literal role="ndbparam:api">BatchSize</literal>
+ defined in the SQL nodes.
</para>
</listitem>
@@ -5091,10 +5091,11 @@
</para>
<para>
- The default for this parameter is zero (no timeout). For a
- real-time database that needs to ensure that no transaction
- keeps locks for too long, this parameter should be set to a
- relatively small value. The unit is milliseconds.
+ The default for this parameter is <literal>4G</literal>
+ (also the maximum). For a real-time database that needs to
+ ensure that no transaction keeps locks for too long, this
+ parameter should be set to a relatively small value. The
+ unit is milliseconds.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@oter02: r26330 - in trunk: refman-5.0 refman-5.1 | jon.stephens | 25 May |
