svn commit - mysqldoc@oter02: r26633 - trunk/refman-5.1

[jon.stephens]

Author: js221926
Date: 2011-06-28 12:41:30 +0200 (Tue, 28 Jun 2011)
New Revision: 26633

Log:

Master and slave mysqlds must come from Cluster distribution, not 5.1. (BUG#61552)



Modified:
   trunk/refman-5.1/mysql-cluster-replication-core.xml


Modified: trunk/refman-5.1/mysql-cluster-replication-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-replication-core.xml	2011-06-28 08:41:34 UTC (rev 26632)
+++ trunk/refman-5.1/mysql-cluster-replication-core.xml	2011-06-28 10:41:30 UTC (rev 26633)
Changed blocks: 4, Lines Added: 45, Lines Deleted: 18; 4762 bytes

@@ -56,13 +56,14 @@
     conceptually very similar but can be more complex in practice, as it
     may be extended to cover a number of different configurations
     including replicating between two complete clusters. Although a
-    MySQL Cluster itself depends on the
-    <literal role="se">NDBCLUSTER</literal> storage engine for
-    clustering functionality, it is not necessary to use the Cluster
-    storage engine on the slave. However, for maximum availability, it
-    is possible to replicate from one MySQL Cluster to another, and it
-    is this type of configuration that we discuss, as shown in the
-    following figure:
+    MySQL Cluster itself depends on the <literal role="se">NDB</literal>
+    storage engine for clustering functionality, it is not necessary to
+    use <literal role="se">NDB</literal> as the storage engine for the
+    slave&apos;s copies of the replicated tables (see
+    <xref linkend="mysql-cluster-replication-ndb-non-ndb"/>). However,
+    for maximum availability, it is possible (and preferable) to
+    replicate from one MySQL Cluster to another, and it is this scenario
+    that we discuss, as shown in the following figure:
   </para>
 
   <mediaobject>

@@ -96,6 +97,27 @@
     <xref linkend="mysql-cluster-replication-pitr"/>.
   </para>
 
+  <formalpara id="mysql-cluster-replication-ndb-non-ndb">
+
+    <title>Replication from <literal>NDB</literal> to non-<literal>NDB</literal>
+      tables</title>
+
+    <para>
+      It is possible to replicate <literal role="se">NDB</literal>
+      tables from a MySQL Cluster acting as the master to tables using
+      other MySQL storage engines such as
+      <literal role="se">InnoDB</literal> or
+      <literal role="se">MyISAM</literal> on a slave
+      <command>mysqld</command>. However, because of differences between
+      the version of <command>mysqld</command> provided with MySQL
+      Cluster and that included with MySQL Server &current-series;, the
+      slave server must also use a <command>mysqld</command> binary from
+      the MySQL Cluster distribution. See
+      <xref linkend="mysql-cluster-replication-general"/>.
+    </para>
+
+  </formalpara>
+
   <section id="mysql-cluster-replication-abbreviations">
 
     <title>MySQL Cluster Replication: Abbreviations and Symbols</title>

@@ -182,7 +204,7 @@
 
   <section id="mysql-cluster-replication-general">
 
-    <title>MySQL Cluster Replication: Assumptions and General Requirements</title>
+    <title>General Requirements for MySQL Cluster Replication</title>
 
     <indexterm>
       <primary>MySQL Cluster replication</primary>

@@ -245,19 +267,24 @@
       <option>--server-id=<replaceable>id</replaceable></option> option,
       where <replaceable>id</replaceable> is a unique integer. Although
       it is not strictly necessary, we will assume for purposes of this
-      discussion that all MySQL installations are the same version.
+      discussion that all MySQL Cluster binaries are of the same release
+      version.
     </para>
 
     <para>
-      In any event, both MySQL servers involved in replication must be
-      compatible with one another with respect to both the version of
-      the replication protocol used and the SQL feature sets which they
-      support; the simplest and easiest way to assure that this is the
-      case is to use the same MySQL version for all servers involved.
-      Note that in many cases it is not possible to replicate to a slave
-      running a version of MySQL with a lower version number than that
-      of the master (see <xref linkend="replication-compatibility"/>,
-      for details).
+      It is generally true in MySQL Replication that both MySQL servers
+      (<command>mysqld</command> processes) involved must be compatible
+      with one another with respect to both the version of the
+      replication protocol used and the SQL feature sets which they
+      support (see <xref linkend="replication-compatibility"/>). It is
+      due to such differences between the binaries in the MySQL Cluster
+      and MySQL Server &current-series; distributions that MySQL Cluster
+      Replication has the additional requirement that both
+      <command>mysqld</command> binaries come from a MySQL Cluster
+      distribution. The simplest and easiest way to assure that the
+      <command>mysqld</command> servers are compatible is to use the
+      same MySQL Cluster distribution for all master and slave
+      <command>mysqld</command> binaries.
     </para>
 
     <para>