List:Commits« Previous MessageNext Message »
From:mysqldoc Date:February 22 2011 4:04pm
Subject:svn commit - mysqldoc@oter02: r25137 - trunk/mysql-monitor-2.3
View as plain text  
Author: mysqldoc
Date: 2011-02-22 17:04:40 +0100 (Tue, 22 Feb 2011)
New Revision: 25137

Log:
Automatic update from ET

Modified:
   trunk/mysql-monitor-2.3/mem-reference-advgraph-core.xml


Modified: trunk/mysql-monitor-2.3/mem-reference-advgraph-core.xml
===================================================================
--- trunk/mysql-monitor-2.3/mem-reference-advgraph-core.xml	2011-02-22 15:46:17 UTC (rev 25136)
+++ trunk/mysql-monitor-2.3/mem-reference-advgraph-core.xml	2011-02-22 16:04:40 UTC (rev 25137)
Changed blocks: 3, Lines Added: 13, Lines Deleted: 13; 2912 bytes

@@ -3353,20 +3353,20 @@
           dump diagnostics information. As this SHOW statement can
           output a lot of data when running in a system with very many
           concurrent sessions, the output is limited to 64 kilobytes in
-          versions less than 5.5.7, and 1 megabyte on versions greater
-          than 5.5.7. You are running a version where the truncation
-          limit should be 1 megabyte, however truncation is still
-          occuring in your system, and the MEM Agent relies on this
-          output to pass back a number of key InnoDB statistics.
+          versions < 5.5.7, and 1 megabyte on versions greater than
+          5.5.7. You are running a version where the truncation limit
+          should be 1 megabyte, however truncation is still occuring in
+          your system, and the MEM Agent relies on this output to pass
+          back a number of key InnoDB statistics.
         </para>
 
         <para>
           However, InnoDB provides a startup option called
           innodb_status_file, which dumps the same output as SHOW ENGINE
-          INNODB STATUS to a file called innodb_status.mysql pid in the
-          datadir. The MEM Agent (in versions > 2.3.0) will read this
-          file automatically if it exists before executing the SHOW
-          statement.
+          INNODB STATUS to a file called innodb_status.&lt;mysql pid&gt;
+          in the datadir. The MEM Agent (in versions &gt; 2.3.0) will
+          read this file automatically if it exists before executing the
+          SHOW statement.
         </para>
 
         <para>

@@ -8407,6 +8407,10 @@
             <entry><emphasis role="bold">Data Item</emphasis></entry>
           </row>
           <row>
+            <entry><emphasis role="bold">hits</emphasis></entry>
+            <entry><literal>mysql</literal>:<literal>status</literal>:<literal>Qcache_hits</literal></entry>
+          </row>
+          <row>
             <entry><emphasis role="bold">inserts</emphasis></entry>
             <entry><literal>mysql</literal>:<literal>status</literal>:<literal>Qcache_inserts</literal></entry>
           </row>

@@ -8414,10 +8418,6 @@
             <entry><emphasis role="bold">not_cached</emphasis></entry>
             <entry><literal>mysql</literal>:<literal>status</literal>:<literal>Qcache_not_cached</literal></entry>
           </row>
-          <row>
-            <entry><emphasis role="bold">hits</emphasis></entry>
-            <entry><literal>mysql</literal>:<literal>status</literal>:<literal>Qcache_hits</literal></entry>
-          </row>
         </tbody>
       </tgroup>
     </informaltable>


Thread
svn commit - mysqldoc@oter02: r25137 - trunk/mysql-monitor-2.3mysqldoc22 Feb