svn commit - mysqldoc@docsrva: r9523 - in trunk: dynamic-docs/changelog dynamic-docs/command-optvars refman-5.1

[jon]

Author: jstephens
Date: 2008-01-09 13:02:00 +0100 (Wed, 09 Jan 2008)
New Revision: 9523

Log:

Documented --ndb-log-orig server option and accompanying changes in
mysql.ndb_binlog_index table.

(Thanks, Tomas!)



Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/dynamic-docs/command-optvars/mysqld.xml
   trunk/refman-5.1/mysql-cluster-cge.xml
   trunk/refman-5.1/mysql-cluster-replication.xml


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2008-01-09 00:15:06 UTC (rev 9522)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2008-01-09 12:02:00 UTC (rev 9523)
Changed blocks: 1, Lines Added: 34, Lines Deleted: 0; 1523 bytes

@@ -9,6 +9,40 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="clusterreplication"/>
+      <manual type="ndb_binlog_index"/>
+      <manual type="ndb-log-orig"/>
+    </tags>
+
+    <versions>
+      <version ver="5.1.22-ndb-6.3.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Multi-way replication failover and recovery for
+        <literal>NDB</literal> is facilitated with the introduction of
+        the <option>--ndb-log-orig</option> option. When
+        <command>mysqld</command> is started with this option, the
+        originating server ID and epoch of each binlog event is recorded
+        in the <literal>mysql.ndb_binlog_index</literal> table, which
+        now contains two additional columns
+        <literal>orig_server_id</literal> and
+        <literal>orig_epoch</literal> for storing this information. In
+        such cases, a single epoch on a slave may be represented by
+        multiple rows in the slave&apos;s
+        <literal>ndb_binlog_index</literal> table, one for each epoch as
+        it originated from a master.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <tags>
       <highlight type="cluster"/>
       <manual type="OPTIMIZE TABLE"/>
     </tags>


Modified: trunk/dynamic-docs/command-optvars/mysqld.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqld.xml	2008-01-09 00:15:06 UTC (rev 9522)
+++ trunk/dynamic-docs/command-optvars/mysqld.xml	2008-01-09 12:02:00 UTC (rev 9523)
Changed blocks: 3, Lines Added: 32, Lines Deleted: 2; 1588 bytes

@@ -10,7 +10,7 @@
     <shortdescription lang="en">
       The number of failed attempts to connect to the MySQL server
     </shortdescription>
-    
+
     <types>
       <vartype isdynamic="no" class="status" scope="both"/>
     </types>

@@ -13471,6 +13471,34 @@
 
   </mysqloption>
 
+  <mysqloption section="ndb" id="ndb_log_orig">
+
+    <xrefto id="mysql-cluster-replication-schema"/>
+
+    <name>ndb_log_orig</name>
+
+    <shortdescription lang="en">
+      Log originating server id and epoch in mysql.ndb_binlog_index
+      table.
+    </shortdescription>
+
+    <types>
+      <vartype class="system"  scope="global" isdynamic="no"/>
+    </types>
+
+    <values vartype="boolean" platform="all">
+
+      <value default="OFF"/>
+
+    </values>
+
+    <versions>
+      <introduced version="5.1.22-ndb-6.3.2"/>
+      <manual version="5.1"/>
+    </versions>
+
+  </mysqloption>
+
   <mysqloption section="ndb" id="ndb_log_updated_only">
 
     <xrefto id="option_mysqld_ndb_log_updated_only"/>

@@ -20965,7 +20993,9 @@
 
     <name>falcon_max_transaction_backlog</name>
 
-    <shortdescription
lang="en">falcon_max_transaction_backlog</shortdescription>
+    <shortdescription lang="en">
+      falcon_max_transaction_backlog
+    </shortdescription>
 
     <types>
       <optype class="mycnf" format="falcon-max-transaction-backlog"/>


Modified: trunk/refman-5.1/mysql-cluster-cge.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-cge.xml	2008-01-09 00:15:06 UTC (rev 9522)
+++ trunk/refman-5.1/mysql-cluster-cge.xml	2008-01-09 12:02:00 UTC (rev 9523)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 908 bytes

@@ -662,6 +662,16 @@
 
           <listitem>
             <para>
+              Recovery of multi-way replication setups (one master, many
+              slaves) is now supported via the
+              <option>--ndb-log-orig</option> server option and changes
+              in the <literal>mysql.ndb_binlog_index</literal> table.
+              (MySQL 5.1.22-ndb-6.3.2)
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
               New values and behaviors are introduced for
               <option>--ndb_optimized_node_selection</option> allowing
               for greater flexibility when an SQL node chooses a


Modified: trunk/refman-5.1/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-replication.xml	2008-01-09 00:15:06 UTC (rev 9522)
+++ trunk/refman-5.1/mysql-cluster-replication.xml	2008-01-09 12:02:00 UTC (rev 9523)
Changed blocks: 2, Lines Added: 44, Lines Deleted: 8; 2855 bytes

@@ -696,14 +696,14 @@
 
 <programlisting>        
 CREATE TABLE `ndb_binlog_index` (
-          `Position`  BIGINT(20) UNSIGNED NOT NULL,
-          `File`      VARCHAR(255) NOT NULL,
-          `epoch`     BIGINT(20) UNSIGNED NOT NULL,
-          `inserts`   BIGINT(20) UNSIGNED NOT NULL,
-          `updates`   BIGINT(20) UNSIGNED NOT NULL,
-          `deletes`   BIGINT(20) UNSIGNED NOT NULL,
-          `schemaops` BIGNINT(20) UNSIGNED NOT NULL,
-          PRIMARY KEY (`epoch`)
+    `Position`  BIGINT(20) UNSIGNED NOT NULL,
+    `File`      VARCHAR(255) NOT NULL,
+    `epoch`     BIGINT(20) UNSIGNED NOT NULL,
+    `inserts`   BIGINT(20) UNSIGNED NOT NULL,
+    `updates`   BIGINT(20) UNSIGNED NOT NULL,
+    `deletes`   BIGINT(20) UNSIGNED NOT NULL,
+    `schemaops` BIGNINT(20) UNSIGNED NOT NULL,
+    PRIMARY KEY (`epoch`)
 ) ENGINE=MYISAM  DEFAULT CHARSET=latin1;
 </programlisting>
 

@@ -729,7 +729,43 @@
         found in <xref linkend="news-5-1-14"/>.
       </para>
     </important>
+    
+    &mccge-warning-begin;
+    
+    <para>
+      Beginning with MySQL 5.1.22-ndb-6.3.2, this table has been changed
+      to facilitate 3-way replication recovery. Two columns
+      <literal>orig_server_id</literal> and
+      <literal>orig_epoch</literal> have been added to this table; when
+      <command>mysqld</command> is started with the
+      <option>--ndb-log-orig</option> option, these columns store,
+      respectively, the ID of the server on which the event originated
+      and the epoch in which the event took place on the originating
+      server. In addition, the table&apos;s primary key now includes
+      these two columns. The modified table definition is shown here:
 
+<programlisting>
+CREATE TABLE `ndb_binlog_index` (
+    `Position` BIGINT(20) UNSIGNED NOT NULL,
+    `File` VARCHAR(255) NOT NULL,
+    `epoch` BIGINT(20) UNSIGNED NOT NULL,
+    `inserts` INT(10) UNSIGNED NOT NULL,
+    `updates` INT(10) UNSIGNED NOT NULL,
+    `deletes` INT(10) UNSIGNED NOT NULL,
+    `schemaops` INT(10) UNSIGNED NOT NULL,
+    `orig_server_id` INT(10) UNSIGNED NOT NULL,
+    `orig_epoch` BIGINT(20) UNSIGNED NOT NULL,
+    `gci` INT(10) UNSIGNED NOT NULL
+    PRIMARY KEY (`epoch`,`orig_server_id`,`orig_epoch`)
+) ENGINE=MyISAM DEFAULT CHARSET=latin1;
+</programlisting>
+
+      The <literal>gci</literal> column was added in MySQL
+      5.1.22-ndb-6.2.6 and MySQL 5.1.22-ndb-6.3.2.
+    </para>
+    
+    &mccge-warning-end-cluster;
+
     <para>
       The following figure shows the relationship of the MySQL Cluster
       replication master server, its binlog injector thread, and the