MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon.stephens Date:May 30 2009 7:00am
Subject:svn commit - mysqldoc@docsrva: r15135 - in trunk: dynamic-docs/command-optvars refman-5.1
View as plain text  
Author: jstephens
Date: 2009-05-30 09:00:19 +0200 (Sat, 30 May 2009)
New Revision: 15135

Log:

Fix for Docs Bug #39432

Also corrected --ndb-log-update-as-write version introduced



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


Modified: trunk/dynamic-docs/command-optvars/mysqld.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqld.xml	2009-05-30 06:00:56 UTC (rev 15134)
+++ trunk/dynamic-docs/command-optvars/mysqld.xml	2009-05-30 07:00:19 UTC (rev 15135)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 564 bytes

@@ -14305,8 +14305,9 @@
     </values>
 
     <versions>
+      <introduced version="5.1.19-ndb-6.3.0"/>
+      <introduced version="5.1.22-ndb-6.2.5"/>
       <manual version="5.1"/>
-      <introduced version="5.1.19-ndb-6.3.0"/>
 <!--<manual version="6.0"/>-->
     </versions>
 


Modified: trunk/refman-5.1/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-replication.xml	2009-05-30 06:00:56 UTC (rev 15134)
+++ trunk/refman-5.1/mysql-cluster-replication.xml	2009-05-30 07:00:19 UTC (rev 15135)
Changed blocks: 2, Lines Added: 21, Lines Deleted: 3; 2092 bytes

@@ -724,6 +724,24 @@
           </para>
 
         </formalpara>
+
+        <para>
+          When replicating from <literal role="se">NDBCLUSTER</literal>
+          to a non-transactional storage engine such as
+          <literal role="se">MyISAM</literal>, you may encounter
+          unnecessary duplicate key errors when replicating
+          <literal role="stmt" condition="insert-on-duplicate">INSERT
+          ... ON DUPLICATE KEY UPDATE</literal> statements. You can
+          suppress these in MySQL Cluster NDB 6.2 by using
+          <option role="mysqld">--ndb-log-update-as-write=0</option>,
+          which forces all columns from updated rows to be sent (and not
+          just those that were updated). For MySQL Cluster NDB 6.3.3 and
+          later, there are additional way to determine whether or not an
+          update to the row on the master should be applied on the slave
+          <command>mysqld</command>; see
+          <xref linkend="mysql-cluster-replication-conflict-resolution"/>,
+          for more information about these methods.
+        </para>
       </listitem>
 
       <listitem>

@@ -2893,9 +2911,9 @@
         image is not of great interest; however, when we need to
         determine on a per-update basis whether or not to use the
         updated values on a replication slave, we need to make sure that
-        both images are written to the master's binary log. This is done
-        with the <option>--ndb-log-update-as-write</option> startup
-        option for <command>mysqld</command>, as described later in this
+        both images are written to the master&apos;s binary log. This is
+        done with the <option>--ndb-log-update-as-write</option> option
+        for <command>mysqld</command>, as described later in this
         section.
 
         <important>


Thread
svn commit - mysqldoc@docsrva: r15135 - in trunk: dynamic-docs/command-optvars refman-5.1jon.stephens30 May