svn commit - mysqldoc@docsrva: r1722 - trunk/refman-5.1

[jon]

Author: jstephens
Date: 2006-04-05 13:10:34 +0200 (Wed, 05 Apr 2006)
New Revision: 1722

Log:

Updated Disk Data with corrected info about DiskPageBufferMemory, added 
SharedBlogalMemory config param.

Clarified info about 4096-character query limit (was a bug in 5.1.6-8 only).

"Share-nothing" -> "shared-nothing" following discussion with Tomas et al.

Other misc. fixes from 2006-04-05 cluster docs discussion.



Modified:
   trunk/refman-5.1/ndbcluster.xml

Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml	2006-04-05 04:48:16 UTC (rev 1721)
+++ trunk/refman-5.1/ndbcluster.xml	2006-04-05 11:10:34 UTC (rev 1722)
@@ -93,8 +93,8 @@
 
     <para>
       <firstterm>MySQL Cluster</firstterm> is a technology that enables
-      clustering of in-memory databases in a share-nothing system. The
-      share-nothing architecture allows the system to work with very
+      clustering of in-memory databases in a shared-nothing system. The
+      shared-nothing architecture allows the system to work with very
       inexpensive hardware, and without any specific requirements on
       hardware or software. It also does not have any single point of
       failure because each component has its own memory and disk.
@@ -10327,13 +10327,47 @@
     </para>
 
     <para>
-      Configuration parameters affecting Disk Data behaviour include
-      <literal>DiskPageBufferMemory</literal>, which determines the
-      amount of space used for caching pages on disk. This is set in the
-      <literal>[NDB DEFAULT]</literal> section of the
-      <filename>my.cnf</filename> file, and is measured in bytes. Each
-      page takes up 32k.
+      Configuration parameters affecting Disk Data behaviour include the
+      following:
     </para>
+    
+    <itemizedlist>
+      <listitem>
+        <para>
+          <literal>DiskPageBufferMemory</literal>
+        </para>
+        
+        <para>
+          This determines the amount of space used for caching pages on
+          disk, and is set in the <literal>[NDBD]</literal> or
+          <literal>[NDBD DEFAULT]</literal> section of the
+          <filename>config.ini</filename> file. It is measured in bytes.
+          Each page takes up 32k. This means that Cluster Disk Data
+          storage always uses <replaceable>N</replaceable> * 32k memory
+          where <replaceable>N</replaceable> is some non-negative
+          integer. 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>SharedGlobalMemory</literal>
+        </para>
+        
+        <para>
+          This determines the amount of memory that is used for log
+          buffers, disk operations (such as page requests and wait
+          queues), and metadata for tablespaces, logfile groups,
+          <literal>UNDO</literal> files, and datafiles. It can be set in
+          the <literal>[NDBD]</literal> or <literal>[NDBD
+            DEFAULT]</literal> section of the
+          <filename>config.ini</filename> configuration file, and is
+          measured in bytes.
+        </para>
+      </listitem>
+    </itemizedlist>
+    
+    
 
   </section>
 
@@ -11124,8 +11158,9 @@
           <listitem>
             <para>
               <literal>CREATE TABLE</literal> statements may be no more than
-              4096 characters in length. This limitation is lifted in MySQL
-              5.1.9. (Bug #17813)
+              4096 characters in length. <emphasis>This limitation
+                affects MySQL 5.1.6, 5.1.7, and 5.1.8 only</emphasis>.
+              (See Bug #17813)
             </para>
           </listitem>
           
@@ -12940,7 +12975,7 @@
         <para>
           This refers to a group of computers working together using the
           <literal>NDB</literal> storage engine to support a distributed
-          MySQL database in a <emphasis>share-nothing
+          MySQL database in a <emphasis>shared-nothing
           architecture</emphasis> using <emphasis>in-memory
           storage</emphasis>.
         </para>
@@ -13329,12 +13364,12 @@
 
       <listitem>
         <para>
-          <emphasis role="bold">Share-nothing architecture</emphasis>:
+          <emphasis role="bold">shared-nothing architecture</emphasis>:
         </para>
 
         <para>
           The ideal architecture for a MySQL Cluster. In a true
-          share-nothing setup, each node runs on a separate host. The
+          shared-nothing setup, each node runs on a separate host. The
           advantage such an arrangement is that there no single host or
           node can act as single point of failure or as a performance
           bottle neck for the system as a whole.