Author: jstephens
Date: 2008-02-19 16:06:16 +0100 (Tue, 19 Feb 2008)
New Revision: 9917
Log:
Fixed description of ndb_cache_check_time system variable
(Thanks, MTaylor and Pekka!)
Modified:
trunk/dynamic-docs/command-optvars/mysqld.xml
trunk/refman-4.1/dba-core.xml
trunk/refman-5.0/dba-core.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-6.0/dba-core.xml
Modified: trunk/dynamic-docs/command-optvars/mysqld.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqld.xml 2008-02-19 14:15:55 UTC (rev 9916)
+++ trunk/dynamic-docs/command-optvars/mysqld.xml 2008-02-19 15:06:16 UTC (rev 9917)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 610 bytes
@@ -13353,8 +13353,8 @@
<name>ndb_cache_check_time</name>
<shortdescription lang="en">
- The number of milliseconds to wait before checking the NDB query
- cache
+ The number of milliseconds between checks of cluster SQL nodes
+ made by the MySQL query cache
</shortdescription>
<types>
Modified: trunk/refman-4.1/dba-core.xml
===================================================================
--- trunk/refman-4.1/dba-core.xml 2008-02-19 14:15:55 UTC (rev 9916)
+++ trunk/refman-4.1/dba-core.xml 2008-02-19 15:06:16 UTC (rev 9917)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 12; 1812 bytes
@@ -5038,21 +5038,19 @@
</para>
<para>
- The number of milliseconds to wait before checking the
- <literal>NDB</literal> query cache. Setting this to
- <literal>0</literal> (the default and minimum value) means
- that the <literal>NDB</literal> query cache will be checked
- for validation on every query.
+ The number of milliseconds that elapse between checks of
+ MySQL Cluster SQL nodes by the MySQL query cache. Setting
+ this to 0 (the default and minimum value) means that the
+ query cache checks for validation on every query.
</para>
<para>
- The recommended maximum value for this variable is
- <literal>1000</literal>, which means that the query cache is
- checked once per second. A larger value means the
- <literal>NDB</literal> query cache is less often checked and
- invalidated due to updates on a different
- <command>mysqld</command>. It is generally not desirable to
- set this to a value greater than <literal>2000</literal>.
+ The recommended maximum value for this variable is 1000,
+ which means that the check is performed once per second. A
+ larger value means that the check is performed and possibly
+ invalidated due to updates on different SQL nodes less
+ often. It is generally not desirable to set this to a value
+ greater than 2000.
</para>
</listitem>
Modified: trunk/refman-5.0/dba-core.xml
===================================================================
--- trunk/refman-5.0/dba-core.xml 2008-02-19 14:15:55 UTC (rev 9916)
+++ trunk/refman-5.0/dba-core.xml 2008-02-19 15:06:16 UTC (rev 9917)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 12; 1883 bytes
@@ -6014,21 +6014,19 @@
<para condition="dynamic:optvar:item" role="5.0:mysqld:ndb_cache_check_time"/>
<para>
- The number of milliseconds to wait before checking the
- <literal>NDB</literal> query cache. Setting this to
- <literal>0</literal> (the default and minimum value) means
- that the <literal>NDB</literal> query cache will be checked
- for validation on every query.
+ The number of milliseconds that elapse between checks of
+ MySQL Cluster SQL nodes by the MySQL query cache. Setting
+ this to 0 (the default and minimum value) means that the
+ query cache checks for validation on every query.
</para>
<para>
- The recommended maximum value for this variable is
- <literal>1000</literal>, which means that the query cache is
- checked once per second. A larger value means the
- <literal>NDB</literal> query cache is less often checked and
- invalidated due to updates on a different
- <command>mysqld</command>. It is generally not desirable to
- set this to a value greater than <literal>2000</literal>.
+ The recommended maximum value for this variable is 1000,
+ which means that the check is performed once per second. A
+ larger value means that the check is performed and possibly
+ invalidated due to updates on different SQL nodes less
+ often. It is generally not desirable to set this to a value
+ greater than 2000.
</para>
</listitem>
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-02-19 14:15:55 UTC (rev 9916)
+++ trunk/refman-5.1/dba-core.xml 2008-02-19 15:06:16 UTC (rev 9917)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 12; 1883 bytes
@@ -6213,21 +6213,19 @@
<para condition="dynamic:optvar:item" role="5.1:mysqld:ndb_cache_check_time"/>
<para>
- The number of milliseconds to wait before checking the
- <literal>NDB</literal> query cache. Setting this to
- <literal>0</literal> (the default and minimum value) means
- that the <literal>NDB</literal> query cache will be checked
- for validation on every query.
+ The number of milliseconds that elapse between checks of
+ MySQL Cluster SQL nodes by the MySQL query cache. Setting
+ this to 0 (the default and minimum value) means that the
+ query cache checks for validation on every query.
</para>
<para>
- The recommended maximum value for this variable is
- <literal>1000</literal>, which means that the query cache is
- checked once per second. A larger value means the
- <literal>NDB</literal> query cache is less often checked and
- invalidated due to updates on a different
- <command>mysqld</command>. It is generally not desirable to
- set this to a value greater than <literal>2000</literal>.
+ The recommended maximum value for this variable is 1000,
+ which means that the check is performed once per second. A
+ larger value means that the check is performed and possibly
+ invalidated due to updates on different SQL nodes less
+ often. It is generally not desirable to set this to a value
+ greater than 2000.
</para>
</listitem>
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-02-19 14:15:55 UTC (rev 9916)
+++ trunk/refman-6.0/dba-core.xml 2008-02-19 15:06:16 UTC (rev 9917)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 12; 1883 bytes
@@ -6082,21 +6082,19 @@
<para condition="dynamic:optvar:item" role="6.0:mysqld:ndb_cache_check_time"/>
<para>
- The number of milliseconds to wait before checking the
- <literal>NDB</literal> query cache. Setting this to
- <literal>0</literal> (the default and minimum value) means
- that the <literal>NDB</literal> query cache will be checked
- for validation on every query.
+ The number of milliseconds that elapse between checks of
+ MySQL Cluster SQL nodes by the MySQL query cache. Setting
+ this to 0 (the default and minimum value) means that the
+ query cache checks for validation on every query.
</para>
<para>
- The recommended maximum value for this variable is
- <literal>1000</literal>, which means that the query cache is
- checked once per second. A larger value means the
- <literal>NDB</literal> query cache is less often checked and
- invalidated due to updates on a different
- <command>mysqld</command>. It is generally not desirable to
- set this to a value greater than <literal>2000</literal>.
+ The recommended maximum value for this variable is 1000,
+ which means that the check is performed once per second. A
+ larger value means that the check is performed and possibly
+ invalidated due to updates on different SQL nodes less
+ often. It is generally not desirable to set this to a value
+ greater than 2000.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r9917 - in trunk: dynamic-docs/command-optvars refman-4.1 refman-5.0 refman-5.1 refman-6.0 | jon | 19 Feb |
