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

[jon]

Author: jstephens
Date: 2007-04-30 12:40:54 +0200 (Mon, 30 Apr 2007)
New Revision: 6263

Log:

MCCGE merge: completed first pass on Cluster chapter.



Modified:
   trunk/refman-5.1/mysql-cluster-merged.xml


Modified: trunk/refman-5.1/mysql-cluster-merged.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-merged.xml	2007-04-30 09:56:59 UTC (rev 6262)
+++ trunk/refman-5.1/mysql-cluster-merged.xml	2007-04-30 10:40:54 UTC (rev 6263)
Changed blocks: 23, Lines Added: 75, Lines Deleted: 26; 10873 bytes

@@ -1665,9 +1665,8 @@
       <para>
         <emphasis role="bold">Note</emphasis>: The default port for
         Cluster management nodes is 1186; the default port for data
-        nodes is 2202. Beginning with MySQL 5.0.3, this restriction is
-        lifted, and the cluster automatically allocates ports for data
-        nodes from those that are already free.
+        nodes is 2202. However, the cluster can automatically allocate
+        ports for data nodes from those that are already free.
       </para>
 
     </section>

@@ -2347,6 +2346,8 @@
         <xref linkend="installing-source-tree"/>.
       </para>
 
+      &mccge-warning-begin;
+
       <warning>
         <para>
           <command>BUILD/compile-pentium-max</command> by default builds

@@ -2367,6 +2368,8 @@
         </para>
       </warning>
 
+      &mccge-warning-end-cluster;
+
       <para>
         <command>BUILD/compile-pentium-max</command> also includes
         OpenSSL, so you must either have or obtain OpenSSL to build

@@ -5571,8 +5574,7 @@
               control the write speed, this parameter specifies how many
               pages per 100 milliseconds are to be written. In this
               context, a <quote>page</quote> is defined as 8KB. This
-              parameter is specified in units of 80KB per second, so ,
-              setting
+              parameter is specified in units of 80KB per second, so setting
               <literal>NoOfDiskPagesToDiskAfterRestartTUP</literal> to a
               value of <literal>20</literal> entails writing 1.6MB in
               data pages to disk each second during a local checkpoint.

@@ -5800,7 +5802,7 @@
           <literal>UndoIndexBuffer</literal> and
           <literal>UndoDataBuffer</literal> parameters which appeared in
           earlier versions of MySQL Cluster are not necessary in MySQL
-          5.1, since undo logs are no longer kept on disk for in-memory
+          5.1 (including &mccge-series;), since undo logs are no longer kept on disk
for in-memory
           tables.
         </para>
 

@@ -6779,7 +6781,7 @@
           <emphasis role="bold">Important</emphasis>: <emphasis>SHM
           functionality is considered experimental only</emphasis>. It
           is not officially supported in any MySQL release series up to
-          and including &current-series;. This means that you must
+          and including MySQL &current-series; and &mccge-series;. This means
that you must
           determine for yourself or by using our free resources (forums,
           mailing lists) whether it can be made to work correctly in
           your specific case.

@@ -14419,6 +14421,12 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          <command>ndbd_redo_log_reader</command>
(<em>&mccge-series; only</em>)
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>

@@ -15852,7 +15860,7 @@
       <refentry id="mysql-cluster-utilities-ndbd-redo-log-reader">
 
         <indexterm>
-          <primary></primary>
+          <primary>ndb_redo_log_reader</primary>
         </indexterm>
 
         <refmeta>

@@ -15881,6 +15889,8 @@
 
           <title>Description</title>
 
+          &mccge-warning-section;
+
           <para>
             Reads a redo log file, checking it for errors, printing its
             contents in a human-readable format, or both.

@@ -17529,6 +17539,8 @@
             and <xref linkend="mysql-cluster-replication-failover"/>.)
           </para>
 
+          &mccge-warning-unsupported-begin;
+
           <para>
             Beginning with MySQL 5.1.18, the master issues a
             <quote>gap</quote> event when connecting to the cluster.

@@ -17548,6 +17560,9 @@
             The slave then resumes reading the master binlog from the
             point where the gap was recorded.
           </para>
+
+          &mccge-warning-end-cluster;
+
         </listitem>
 
         <listitem>

@@ -17564,6 +17579,8 @@
             server.
           </para>
 
+          &mccge-warning-unsupported-begin;
+
           <para>
             Beginning with MySQL 5.1.18, this limitation is lifted, as
             discussed in the next few paragraphs, in which we consider

@@ -17647,6 +17664,9 @@
             be noted that it has not yet been thoroughly tested and must
             therefore still be considered experimental.
           </para>
+
+          &mccge-warning-end-cluster;
+
         </listitem>
 
         <listitem>

@@ -17707,17 +17727,17 @@
       </indexterm>
 
       <indexterm>
-        <primary><literal>cluster</literal> database
(obsolete)</primary>
+        <primary><literal>cluster</literal> database
(OBSOLETE)</primary>
 <!--        <seealso>MySQL Cluster replication</seealso> -->
       </indexterm>
 
       <indexterm>
-        <primary><literal>cluster_replication</literal> database
(obsolete)</primary>
+        <primary><literal>cluster_replication</literal> database
(OBSOLETE)</primary>
 <!--        <see>MySQL Cluster replication</see> -->
       </indexterm>
 
       <indexterm>
-        <primary><literal>binlog_index</literal> table
(obsolete)</primary>
+        <primary><literal>binlog_index</literal> table
(OBSOLETE)</primary>
 <!--        <seealso>MySQL Cluster replication</seealso>  -->
       </indexterm>
 

@@ -17727,7 +17747,7 @@
       </indexterm>
 
       <indexterm>
-        <primary><literal>cluster.binlog_index</literal> table
(obsolete)</primary>
+        <primary><literal>cluster.binlog_index</literal> table
(OBSOLETE)</primary>
 <!--        <see>MySQL Cluster replication</see> -->
       </indexterm>
 

@@ -17806,12 +17826,12 @@
       </mediaobject>
 
       <indexterm>
-        <primary><literal>ndb_apply_status</literal> table (MySQL
CLuster replication)</primary>
+        <primary><literal>ndb_apply_status</literal> table (MySQL
Cluster replication)</primary>
 <!--        <seealso>MySQL Cluster replication</seealso> -->
       </indexterm>
 
       <indexterm>
-        <primary><literal>apply_status</literal> table
(obsolete)</primary>
+        <primary><literal>apply_status</literal> table
(OBSOLETE)</primary>
 <!--        <seealso>MySQL Cluster replication</seealso> -->
       </indexterm>
 

@@ -17836,6 +17856,8 @@
 ) ENGINE=NDBCLUSTER   DEFAULT CHARSET=latin1;
 </programlisting>
 
+      &mccge-warning-unsupported-begin;
+
       <para>
         The <literal>log_name</literal>,
<literal>start_pos</literal>,
         and <literal>end_pos</literal> columns were added in MySQL

@@ -17851,6 +17873,8 @@
         </para>
       </important>
 
+      &mccge-warning-end-cluster;
+
       <para>
         The <literal>ndb_binlog_index</literal> and
         <literal>ndb_apply_status</literal> tables are created in the

@@ -19257,11 +19281,12 @@
                 <literal>NDB</literal> and
                 <literal>NDBCLUSTER</literal>.
               </para>
-
+             <important>
               <para>
                 In MySQL 5.1.8 and later, there can exist only one log
                 file group at any given time.
               </para>
+             </important>
             </listitem>
 
             <listitem>

@@ -20677,17 +20702,19 @@
     </indexterm>
 
     <para>
-      In this section, we provide a list of known limitations in MySQL
-      Cluster releases in the &current-series;.x series compared to
+      In this section, we provide a list of known limitations in MySQL
&current-series; 
+      Cluster and &mccge-series; releases as compared with the
       features available when using the <literal>MyISAM</literal> and
       <literal>InnoDB</literal> storage engines. Currently, there are no
       plans to address these in coming releases of MySQL
-      &current-series;; however, we will attempt to supply fixes for
+      &current-series; or &mccge-series;; however, we will attempt to supply
fixes for
       these issues in subsequent release series. If you check the
       <quote>Cluster</quote> category in the MySQL bugs database at
       <ulink url="http://bugs.mysql.com"/>, you can find known bugs
       which (if marked <quote>&current-series;</quote>) we intend to
-      correct in upcoming releases of MySQL &current-series;.
+      correct in upcoming releases of MySQL &current-series;. Some of these issues 
+      may be addressed in &mccge-series; and the fixes included in a future 
+      mainline MySQL Cluster version.
     </para>
 
     <para>

@@ -21589,7 +21616,7 @@
             <para>
               We may support multiple data nodes per host in a future
               MySQL release, following additional testing. However, in
-              MySQL &current-series;, such configurations can be
+              MySQL &current-series; and &mccge-series;, such configurations can
be
               considered experimental only.
             </para>
           </listitem>

@@ -21717,12 +21744,33 @@
               API nodes (applications accessing the cluster other than
               MySQL servers), data nodes, and management servers.
             </para>
+
+            &mccge-warning-begin;
+
+            <para>
+              Prior to MySQL 5.1.15-ndb-6.1.1, the total maximum number
+              of nodes in a MySQL Cluster was 63, including all SQL
+              nodes (MySQL Servers), API nodes (applications accessing
+              the cluster other than MySQL servers), data nodes, and
+              management servers.
+            </para>
+
+            <para>
+              Starting with MySQL 5.1.15-ndb-6.1.1, up to 255 API nodes
+              (including MySQL servers acting as cluster SQL nodes) are
+              supported by a single cluster. The total number of data
+              nodes and management nodes beginning with this version is
+              63, of which up to 48 can be data nodes.
+            </para>
+
+            &mccge-warning-end-cluster;
+
           </listitem>
 
           <listitem>
             <para>
-              The maximum number of metadata objects in MySQL 5.1
-              Cluster is 20320. This limit is hard-coded.
+              The maximum number of metadata objects in MySQL &current-series;
+              Cluster and &mccge-series; is 20320. This limit is hard-coded.
             </para>
           </listitem>
 

@@ -21915,12 +21963,13 @@
 
     <para>
       In this section, we discuss changes in the implementation of MySQL
-      Cluster in MySQL &current-series; as compared to MySQL
+      Cluster in MySQL &current-series; and &mccge-series; as compared to MySQL
       &previous-series;.
 
-<!-- We will also discuss our roadmap for further
-      improvements to MySQL Cluster as currently planned for MySQL
-      &next-series;. -->
+<!-- 
+      We also discuss our roadmap for further improvements to MySQL Cluster 
+      as currently planned for MySQL &next-series;. 
+-->
     </para>
 
     <para>