Author: jstephens
Date: 2007-01-27 04:19:21 +0100 (Sat, 27 Jan 2007)
New Revision: 4670
Log:
Added note about CLUSTERLOG STATISTICS=15 filling up logs.
Modified:
branches/telcos/refman-5.1/mysql-cluster.xml
trunk/refman-4.1/mysql-cluster.xml
trunk/refman-5.0/mysql-cluster.xml
trunk/refman-5.1/mysql-cluster.xml
Modified: branches/telcos/refman-5.1/mysql-cluster.xml
===================================================================
--- branches/telcos/refman-5.1/mysql-cluster.xml 2007-01-27 02:49:02 UTC (rev 4669)
+++ branches/telcos/refman-5.1/mysql-cluster.xml 2007-01-27 03:19:21 UTC (rev 4670)
Changed blocks: 3, Lines Added: 19, Lines Deleted: 6; 2080 bytes
@@ -10991,9 +10991,7 @@
to appear in the log are connections and disconnections
between different nodes in the cluster, and when checkpoints
occur. In some cases, the description may contain status
- information, such as that generated when the
- <literal>CLUSTERLOG STATISTICS</literal> command is issued
- in the management client.
+ information.
</para>
</listitem>
</itemizedlist>
@@ -11168,6 +11166,13 @@
</tbody>
</tgroup>
</informaltable>
+
+ <para>
+ The <literal>STATISTICS</literal> category can provide a great
+ deal of useful data. See
+ <xref linkend="mysql-cluster-log-statistics"/>, for more
+ information.
+ </para>
<para>
Thresholds are used to filter events within each category. For
@@ -12154,14 +12159,22 @@
</para>
<para>
- To generate a report of all cluster log statistics, you can
- use the following command in the <literal>NDB</literal>
- management client:
+ To cause all cluster log statistics to be logged, you can use
+ the following command in the <literal>NDB</literal> management
+ client:
</para>
<programlisting>
ndb_mgm> <userinput>ALL CLUSTERLOG STATISTICS=15</userinput>
</programlisting>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: Setting the threshold
+ for <literal>STATISTICS</literal> to 15 causes the cluster log
+ to become very verbose, and to gow quite rapidly in size, in
+ direct proportion to the number of cluster nodes and the
+ amount of activity on the cluster.
+ </para>
</section>
Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml 2007-01-27 02:49:02 UTC (rev 4669)
+++ trunk/refman-4.1/mysql-cluster.xml 2007-01-27 03:19:21 UTC (rev 4670)
Changed blocks: 3, Lines Added: 22, Lines Deleted: 9; 2202 bytes
@@ -10769,9 +10769,7 @@
to appear in the log are connections and disconnections
between different nodes in the cluster, and when checkpoints
occur. In some cases, the description may contain status
- information, such as that generated when the
- <literal>CLUSTERLOG STATISTICS</literal> command is issued
- in the management client.
+ information.
</para>
</listitem>
</itemizedlist>
@@ -10879,6 +10877,13 @@
</listitem>
</itemizedlist>
+
+ <para>
+ The <literal>STATISTICS</literal> category can provide a great
+ deal of useful data. See
+ <xref linkend="mysql-cluster-log-statistics"/>, for more
+ information.
+ </para>
<para>
The following table describes the default setting (for all
@@ -11929,16 +11934,24 @@
These values are given in bytes. Higher values mean a lower
cost per byte sent or received; the maximum is 64k.
</para>
-
+
<para>
- To generate a report of all cluster log statistics, you can
- use the following command in the <literal>NDB</literal>
- management client:
+ To cause all cluster log statistics to be logged, you can use
+ the following command in the <literal>NDB</literal> management
+ client:
</para>
-
-<programlisting>
+
+ <programlisting>
ndb_mgm> <userinput>ALL CLUSTERLOG STATISTICS=15</userinput>
</programlisting>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: Setting the threshold
+ for <literal>STATISTICS</literal> to 15 causes the cluster log
+ to become very verbose, and to gow quite rapidly in size, in
+ direct proportion to the number of cluster nodes and the
+ amount of activity on the cluster.
+ </para>
</section>
Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml 2007-01-27 02:49:02 UTC (rev 4669)
+++ trunk/refman-5.0/mysql-cluster.xml 2007-01-27 03:19:21 UTC (rev 4670)
Changed blocks: 3, Lines Added: 22, Lines Deleted: 9; 2225 bytes
@@ -10882,9 +10882,7 @@
to appear in the log are connections and disconnections
between different nodes in the cluster, and when checkpoints
occur. In some cases, the description may contain status
- information, such as that generated when the
- <literal>CLUSTERLOG STATISTICS</literal> command is issued
- in the management client.
+ information.
</para>
</listitem>
</itemizedlist>
@@ -11058,6 +11056,13 @@
</tbody>
</tgroup>
</informaltable>
+
+ <para>
+ The <literal>STATISTICS</literal> category can provide a great
+ deal of useful data. See
+ <xref linkend="mysql-cluster-log-statistics"/>, for more
+ information.
+ </para>
<para>
Thresholds are used to filter events within each category. For
@@ -12042,16 +12047,24 @@
These values are given in bytes. Higher values mean a lower
cost per byte sent or received; the maximum is 64k.
</para>
-
+
<para>
- To generate a report of all cluster log statistics, you can
- use the following command in the <literal>NDB</literal>
- management client:
+ To cause all cluster log statistics to be logged, you can use
+ the following command in the <literal>NDB</literal> management
+ client:
</para>
-
-<programlisting>
+
+ <programlisting>
ndb_mgm> <userinput>ALL CLUSTERLOG STATISTICS=15</userinput>
</programlisting>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: Setting the threshold
+ for <literal>STATISTICS</literal> to 15 causes the cluster log
+ to become very verbose, and to gow quite rapidly in size, in
+ direct proportion to the number of cluster nodes and the
+ amount of activity on the cluster.
+ </para>
</section>
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-01-27 02:49:02 UTC (rev 4669)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-01-27 03:19:21 UTC (rev 4670)
Changed blocks: 3, Lines Added: 22, Lines Deleted: 9; 2225 bytes
@@ -10935,9 +10935,7 @@
to appear in the log are connections and disconnections
between different nodes in the cluster, and when checkpoints
occur. In some cases, the description may contain status
- information, such as that generated when the
- <literal>CLUSTERLOG STATISTICS</literal> command is issued
- in the management client.
+ information.
</para>
</listitem>
</itemizedlist>
@@ -11111,6 +11109,13 @@
</tbody>
</tgroup>
</informaltable>
+
+ <para>
+ The <literal>STATISTICS</literal> category can provide a great
+ deal of useful data. See
+ <xref linkend="mysql-cluster-log-statistics"/>, for more
+ information.
+ </para>
<para>
Thresholds are used to filter events within each category. For
@@ -12095,16 +12100,24 @@
These values are given in bytes. Higher values mean a lower
cost per byte sent or received; the maximum is 64k.
</para>
-
+
<para>
- To generate a report of all cluster log statistics, you can
- use the following command in the <literal>NDB</literal>
- management client:
+ To cause all cluster log statistics to be logged, you can use
+ the following command in the <literal>NDB</literal> management
+ client:
</para>
-
-<programlisting>
+
+ <programlisting>
ndb_mgm> <userinput>ALL CLUSTERLOG STATISTICS=15</userinput>
</programlisting>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: Setting the threshold
+ for <literal>STATISTICS</literal> to 15 causes the cluster log
+ to become very verbose, and to gow quite rapidly in size, in
+ direct proportion to the number of cluster nodes and the
+ amount of activity on the cluster.
+ </para>
</section>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4670 - branches/telcos/refman-5.1 trunk/refman-4.1 trunk/refman-5.0 trunk/refman-5.1 | jon | 27 Jan |
