List:Commits« Previous MessageNext Message »
From:jon.stephens Date:April 28 2011 11:00am
Subject:svn commit - mysqldoc@oter02: r26055 - in trunk: dynamic-docs/changelog ndbapi refman-5.1
View as plain text  
Author: js221926
Date: 2011-04-28 13:00:30 +0200 (Thu, 28 Apr 2011)
New Revision: 26055

Log:

Improved ndbinfo auto-link markup, removed redundant xrefs.



Modified:
   trunk/dynamic-docs/changelog/mysqld-2.xml
   trunk/ndbapi/ndb-internals.xml
   trunk/refman-5.1/mysql-cluster-management.xml
   trunk/refman-5.1/mysql-cluster-overview.xml


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2011-04-28 08:59:47 UTC (rev 26054)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2011-04-28 11:00:30 UTC (rev 26055)
Changed blocks: 9, Lines Added: 38, Lines Deleted: 37; 6197 bytes

@@ -173,13 +173,13 @@
 
       <para>
         A <literal>config_generation</literal> column has been added to
-        the <literal role="ndbinfo">ndbinfo.nodes</literal> table. By
-        checking this column, it is now possible to determine which
-        version or versions of the MySQL Cluster configuration file are
-        in effect on the data nodes. This information can be especially
-        useful when performing a rolling restart of the cluster in order
-        to update its configuration. For more information, see
-        <xref linkend="mysql-cluster-ndbinfo-nodes"/>.
+        the <literal role="ndbinfo">nodes</literal> table of the
+        <literal role="ndbinfo">ndbinfo</literal> database. By checking
+        this column, it is now possible to determine which version or
+        versions of the MySQL Cluster configuration file are in effect
+        on the data nodes. This information can be especially useful
+        when performing a rolling restart of the cluster in order to
+        update its configuration.
       </para>
 
     </message>

@@ -232,10 +232,10 @@
         given join is pushed down using
         <literal role="stmt">EXPLAIN</literal>. In addition, several new
         counters relating to push-down join performance have been added
-        to the <literal role="ndbinfo">ndbinfo.counters</literal> table.
-        For more information, see the descriptions of these status
-        variables, as well as
-        <xref linkend="mysql-cluster-ndbinfo-counters"/>.
+        to the <literal role="ndbinfo">counters</literal> table in the
+        <literal role="ndbinfo">ndbinfo</literal> database. For more
+        information, see the descriptions of the status variables
+        previously mentioned.
       </para>
 
     </message>

@@ -2367,10 +2367,10 @@
 
       <para>
         Successive queries on the
-        <literal role="ndbinfo">ndbinfo.counters</literal> table from
-        the same SQL node returned unchanging results. To fix this
-        issue, and to prevent similar issues from occurring in the
-        future, <literal role="ndbinfo">ndbinfo</literal> tables are now
+        <literal role="ndbinfo">counters</literal> table from the same
+        SQL node returned unchanging results. To fix this issue, and to
+        prevent similar issues from occurring in the future,
+        <literal role="ndbinfo">ndbinfo</literal> tables are now
         excluded from the query cache.
       </para>
 

@@ -5171,15 +5171,14 @@
     <message>
 
       <para>
-        A new <literal>diskpagebuffer</literal> table, providing
-        statistics on disk page buffer usage by Disk Data tables, is
-        added to the <literal role="ndbinfo">ndbinfo</literal>
-        information database. These statistics can be used to monitor
-        performance of reads and writes on Disk Data tables, and to
-        assist in the tuning of related parameters such as
+        A new <literal role="ndbinfo">diskpagebuffer</literal> table,
+        providing statistics on disk page buffer usage by Disk Data
+        tables, is added to the
+        <literal role="ndbinfo">ndbinfo</literal> information database.
+        These statistics can be used to monitor performance of reads and
+        writes on Disk Data tables, and to assist in the tuning of
+        related parameters such as
         <literal role="ndbparam:ndbd">DiskPageBufferMemory</literal>.
-        For more information, see
-        <xref linkend="mysql-cluster-ndbinfo-diskpagebuffer"/>.
       </para>
 
     </message>

@@ -13360,9 +13359,10 @@
     <message>
 
       <para>
-        The schema for the <literal>memoryusage</literal> table of the
-        <literal role="ndbinfo">ndbinfo</literal> information database
-        has changed, as detailed in the following list:
+        The schema for the <literal role="ndbinfo">memoryusage</literal>
+        table of the <literal role="ndbinfo">ndbinfo</literal>
+        information database has changed, as detailed in the following
+        list:
       </para>
 
       <itemizedlist>

@@ -15065,11 +15065,12 @@
     <message>
 
       <para>
-        The experimental <literal role="ndbinfo">ndbinfo.pools</literal>
-        table has been removed. Information useful to MySQL Cluster
-        administration that was contained in this table should be
-        available from other <literal role="ndbinfo">ndbinfo</literal>
-        tables.
+        The experimental <literal role="ndbinfo">pools</literal> table
+        has been removed from the
+        <literal role="ndbinfo">ndbinfo</literal> database. Information
+        useful to MySQL Cluster administration that was contained in
+        this table should be available from other
+        <literal role="ndbinfo">ndbinfo</literal> tables.
       </para>
 
     </message>

@@ -15902,8 +15903,8 @@
 
       <para>
         Some values shown in the
-        <literal role="ndbinfo">ndbinfo.memoryusage</literal> table did
-        not match corresponding values shown by the
+        <literal role="ndbinfo">memoryusage</literal> table did not
+        match corresponding values shown by the
         <command>ndb_mgm</command> client <literal>ALL REPORT
         MEMORYUSAGE</literal> command.
       </para>

@@ -17726,8 +17727,8 @@
 
       <para>
         The <literal>DATA_MEMORY</literal> column of the
-        <literal role="ndbinfo">ndbinfo.memoryusage</literal> table was
-        renamed to <literal>memory_type</literal>.
+        <literal role="ndbinfo">memoryusage</literal> table was renamed
+        to <literal>memory_type</literal>.
       </para>
 
     </message>

@@ -17754,8 +17755,8 @@
     <message>
 
       <para>
-        The <literal role="ndbinfo">ndbinfo.transporters</literal> table
-        showed the status of a disconnected node as
+        The <literal role="ndbinfo">transporters</literal> table showed
+        the status of a disconnected node as
         <literal>DISCONNECTING</literal> rather than
         <literal>DISCONNECTED</literal>.
       </para>


Modified: trunk/ndbapi/ndb-internals.xml
===================================================================
--- trunk/ndbapi/ndb-internals.xml	2011-04-28 08:59:47 UTC (rev 26054)
+++ trunk/ndbapi/ndb-internals.xml	2011-04-28 11:00:30 UTC (rev 26055)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 2; 759 bytes

@@ -2258,8 +2258,9 @@
             information (see
             <xref linkend="mysql-cluster-mgm-client-commands"/>).
             Beginning with MySQL Cluster NDB 7.1.0, you can also query
-            the <literal role="ndbinfo">ndbinfo.memoryusage</literal>
-            table for this information.
+            the <literal role="ndbinfo">memoryusage</literal> table (in
+            the <literal role="ndbinfo">ndbinfo</literal> database) for
+            this information.
           </para>
 
         </formalpara>


Modified: trunk/refman-5.1/mysql-cluster-management.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-management.xml	2011-04-28 08:59:47 UTC (rev 26054)
+++ trunk/refman-5.1/mysql-cluster-management.xml	2011-04-28 11:00:30 UTC (rev 26055)
Changed blocks: 3, Lines Added: 17, Lines Deleted: 9; 1977 bytes

@@ -8521,18 +8521,15 @@
 </programlisting>
 
     <para>
-      The <literal>diskpagebuffer</literal> table was added in MySQL
-      Cluster NDB 7.1.9. See
-      <xref linkend="mysql-cluster-ndbinfo-diskpagebuffer"/>, for more
-      information.
+      The <literal role="ndbinfo">diskpagebuffer</literal> table was added in MySQL
+      Cluster NDB 7.1.9.
     </para>
 
     <para>
       In early versions of MySQL Cluster NDB 7.1, there was an
-      additional <literal>pools</literal> table in the
+      additional <literal role="ndbinfo">pools</literal> table in the
       <literal>ndbinfo</literal> database; however, this table was
-      removed in MySQL Cluster NDB 7.1.3. See
-      <xref linkend="mysql-cluster-ndbinfo-pools"/>.
+      removed in MySQL Cluster NDB 7.1.3.
     </para>
 
     <indexterm>

@@ -8559,7 +8556,8 @@
 </programlisting>
 
     <para>
-      More complex queries are possible, as shown here:
+      More complex queries, such as the two following <literal role="stmt">SELECT</literal> statements using
+      the <literal role="ndbinfo">memoryusage</literal> table, are possible:
     </para>
 
 <programlisting>

@@ -12042,7 +12040,17 @@
           restart of the cluster.
         </para>
       </important>
-
+      
+      
+      <para>
+        Performance of Disk Data tables can be improved by minimizing the number
+        of disk seeks by making sure that 
+        <literal role="ndbparam:ndbd">DiskPageBufferMemory</literal> is of
+        sufficient size. You can query the 
+        <literal role="ndbinfo">diskpagebuffer</literal> table to help determine
+        whether the value for this parameter needs to be increased.
+      </para>
+      
     </section>
 
   </section>


Modified: trunk/refman-5.1/mysql-cluster-overview.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-overview.xml	2011-04-28 08:59:47 UTC (rev 26054)
+++ trunk/refman-5.1/mysql-cluster-overview.xml	2011-04-28 11:00:30 UTC (rev 26055)
Changed blocks: 7, Lines Added: 43, Lines Deleted: 39; 7787 bytes

@@ -1398,9 +1398,10 @@
             <literal role="statvar">Ndb_pushed_queries_dropped</literal>,
             <literal role="statvar">Ndb_pushed_queries_executed</literal>,
             and <literal role="statvar">Ndb_pushed_reads</literal>) and
-            additions to the <literal role="ndbinfo">ndbinfo.counters</literal> table
-            can also be helpful in determining when and how well joins
-            are being pushed down.
+            additions to the <literal role="ndbinfo">counters</literal>
+            table (in the <literal role="ndbinfo">ndbinfo</literal>
+            information database) can also be helpful in determining
+            when and how well joins are being pushed down.
           </para>
 
           <para>

@@ -1499,18 +1500,19 @@
         <listitem>
           <formalpara>
 
-            <title>MySQL Cluster information database (<literal role="ndbinfo">ndbinfo</literal>)</title>
+            <title>MySQL Cluster information database
+              (<literal role="ndbinfo">ndbinfo</literal>)</title>
 
             <para>
-              The <literal role="ndbinfo">ndbinfo</literal> information database makes
-              it possible to obtain real-time characteristics of a MySQL
-              Cluster by issuing queries from the
-              <command>mysql</command> client or other MySQL client
-              applications. <literal role="ndbinfo">ndbinfo</literal> provides metadata
-              specific to MySQL Cluster similarly to how the
-              <literal>INFORMATION_SCHEMA</literal> database provides
-              metadata for the standard MySQL Server. This eliminates
-              much of the need to read log files, issue
+              The <literal role="ndbinfo">ndbinfo</literal> information
+              database makes it possible to obtain real-time
+              characteristics of a MySQL Cluster by issuing queries from
+              the <command>mysql</command> client or other MySQL client
+              applications. <literal role="ndbinfo">ndbinfo</literal>
+              provides metadata specific to MySQL Cluster similarly to
+              how the <literal>INFORMATION_SCHEMA</literal> database
+              provides metadata for the standard MySQL Server. This
+              eliminates much of the need to read log files, issue
               <literal>REPORT</literal> or <literal>DUMP</literal>
               commands in the <command>ndb_mgm</command> client, or
               parse the output of <command>ndb_config</command> in order

@@ -1793,12 +1795,12 @@
             <title>Change in <literal role="ndbinfo">ndbinfo</literal> database</title>
 
             <para>
-              The experimental <literal role="ndbinfo">ndbinfo.pools</literal> table
-              was removed from <literal role="ndbinfo">ndbinfo</literal> in MySQL
-              Cluster NDB 7.1.3. Applications which used this table can
-              and should be rewritten to use other
-              <literal role="ndbinfo">ndbinfo</literal> tables. For more information,
-              see <xref linkend="mysql-cluster-ndbinfo-pools"/>.
+              The experimental <literal role="ndbinfo">pools</literal>
+              table was removed from
+              <literal role="ndbinfo">ndbinfo</literal> in MySQL Cluster
+              NDB 7.1.3. Applications which used this table can and
+              should be rewritten to use other
+              <literal role="ndbinfo">ndbinfo</literal> tables.
             </para>
 
           </formalpara>

@@ -2023,15 +2025,14 @@
 
             <para>
               MySQL Cluster 7.1.9 introduces a new table in the
-              <literal role="ndbinfo">ndbinfo</literal> information database. The
-              <literal>diskpagebuffer</literal> table provides real-time
-              data on disk page buffer usage. These statistics can be
-              used to monitor performance of MySQL Cluster Disk Data
-              read and write operations, and can prove useful in the
-              tuning of Disk Data parameters such as
+              <literal role="ndbinfo">ndbinfo</literal> information
+              database. The
+              <literal role="ndbinfo">diskpagebuffer</literal> table
+              provides real-time data on disk page buffer usage. These
+              statistics can be used to monitor performance of MySQL
+              Cluster Disk Data read and write operations, and can prove
+              useful in the tuning of Disk Data parameters such as
               <literal role="ndbparam:ndbd">DiskPageBufferMemory</literal>.
-              For more information, see
-              <xref linkend="mysql-cluster-ndbinfo-diskpagebuffer"/>.
             </para>
 
           </formalpara>

@@ -2275,15 +2276,16 @@
         <listitem>
           <formalpara>
 
-            <title>Configuration version information in <literal role="ndbinfo">ndbinfo.nodes</literal></title>
+            <title>Configuration version information in
+              <literal role="ndbinfo">ndbinfo.nodes</literal></title>
 
             <para>
               You can see which version or versions of the MySQL Cluster
               configuration file are in effect on the data nodes by
               checking the <literal>config_generation</literal> column
-              which is added to the <literal role="ndbinfo">ndbinfo.nodes</literal>
-              table in MySQL Cluster NDB 7.1.13. For more information,
-              see <xref linkend="mysql-cluster-ndbinfo-nodes"/>.
+              which is added to the
+              <literal role="ndbinfo">nodes</literal> table in MySQL
+              Cluster NDB 7.1.13.
             </para>
 
           </formalpara>

@@ -2292,15 +2294,16 @@
         <listitem>
           <formalpara>
 
-            <title>Configuration version information in <literal role="ndbinfo">ndbinfo.nodes</literal></title>
+            <title>Configuration version information in
+              <literal role="ndbinfo">ndbinfo.nodes</literal></title>
 
             <para>
               You can see which version or versions of the MySQL Cluster
               configuration file are in effect on the data nodes by
               checking the <literal>config_generation</literal> column
-              which is added to the <literal role="ndbinfo">ndbinfo.nodes</literal>
-              table in MySQL Cluster NDB 7.1.13. For more information,
-              see <xref linkend="mysql-cluster-ndbinfo-nodes"/>.
+              which is added to the
+              <literal role="ndbinfo">nodes</literal> table in MySQL
+              Cluster NDB 7.1.13.
             </para>
 
           </formalpara>

@@ -3352,15 +3355,16 @@
         <listitem>
           <formalpara>
 
-            <title>Configuration version information in <literal role="ndbinfo">ndbinfo.nodes</literal></title>
+            <title>Configuration version information in
+              <literal role="ndbinfo">ndbinfo.nodes</literal></title>
 
             <para>
               You can see which version or versions of the MySQL Cluster
               configuration file are in effect on the data nodes by
               checking the <literal>config_generation</literal> column
-              which is added to the <literal role="ndbinfo">ndbinfo.nodes</literal>
-              table in MySQL Cluster NDB 7.0.24. For more information,
-              see <xref linkend="mysql-cluster-ndbinfo-nodes"/>.
+              which is added to the
+              <literal role="ndbinfo">nodes</literal> table in MySQL
+              Cluster NDB 7.0.24.
             </para>
 
           </formalpara>


Thread
svn commit - mysqldoc@oter02: r26055 - in trunk: dynamic-docs/changelog ndbapi refman-5.1jon.stephens28 Apr