From: Date: February 6 2008 1:54pm
Subject: svn commit - mysqldoc@docsrva: r9717 - in trunk: dynamic-docs/changelog dynamic-docs/command-optvars refman-5.1 refman-6.0
List-Archive: http://lists.mysql.com/commits/41771
Message-Id: <200802061254.m16CsTf3013148@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Author: jstephens
Date: 2008-02-06 13:54:28 +0100 (Wed, 06 Feb 2008)
New Revision: 9717
Log:
Documented RBR bugfixes:
Bug #27779, Bug #31552, Bug #31583, Bug #31609, Bug #32468
Documented new slave_exec_mode system variable (Thanks, Mats!)
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/dynamic-docs/command-optvars/mysqld.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-5.1/mysql-cluster-replication.xml
trunk/refman-6.0/dba-core.xml
trunk/refman-6.0/mysql-cluster-replication.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-02-06 10:46:08 UTC (rev 9716)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-02-06 12:54:28 UTC (rev 9717)
Changed blocks: 1, Lines Added: 161, Lines Deleted: 0; 3849 bytes
@@ -9,6 +9,167 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Introduced the slave_exec_mode system
+ variable to control whether idempotent or strict mode is used
+ for replication conflict resolution. Idempotent mode suppresses
+ duplicate-key, no-key-found, and some other errors, and is
+ needed for circular replication, multi-master replication, and
+ some other complex replication setups when using MySQL Cluster.
+ Strict mode is the default.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Slaves running MySQL 5.1.18 and later could not read binary logs
+ from older versions of the server.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ When using row-based replication from a master running MySQL
+ 5.1.21 or earlier to a slave running 5.1.22 or later, updates of
+ integer columns failed on the slave with Error in
+ Unknown event: row application failed.
+
+
+
+
+
+
+
+ When using row-based replication from a master running MySQL
+ 6.0.3 or earlier to a slave running 6.0.4 or later, updates of
+ integer columns failed on the slave with Error in
+ Unknown event: row application failed.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ When using row-based replication, deletes from a table with a
+ foreign key constraint failed on the slave.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ When using row-based replication, the slave stopped when
+ attempting to delete non-existent rows from a slave table
+ without a primary key. In addition, no error was reported when
+ this occurred.
+
+
+
+
+
+
+
+
+
Modified: trunk/dynamic-docs/command-optvars/mysqld.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqld.xml 2008-02-06 10:46:08 UTC (rev 9716)
+++ trunk/dynamic-docs/command-optvars/mysqld.xml 2008-02-06 12:54:28 UTC (rev 9717)
Changed blocks: 4, Lines Added: 36, Lines Deleted: 4; 1814 bytes
@@ -4362,6 +4362,38 @@
+
+
+
+
+ slave_exec_mode
+
+
+ Allows for switching between idempotent mode (key and some other
+ errors suppressed) and strict mode; strict mode is the default
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
@@ -10665,7 +10697,7 @@
-
+
@@ -12285,7 +12317,7 @@
-
+
@@ -18328,8 +18360,8 @@
-
-
+
+
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-02-06 10:46:08 UTC (rev 9716)
+++ trunk/refman-5.1/dba-core.xml 2008-02-06 12:54:28 UTC (rev 9717)
Changed blocks: 6, Lines Added: 29, Lines Deleted: 21; 3808 bytes
@@ -6927,9 +6927,9 @@
The current number of prepared statements. (The maximum
number of statements is given by the
- max_prepared_stmt_count system
- variable.) This variable was added in MySQL 5.1.10. In MySQL
- 5.1.14, it was converted to the global
+ max_prepared_stmt_count system variable.)
+ This variable was added in MySQL 5.1.10. In MySQL 5.1.14, it
+ was converted to the global
Prepared_stmt_count status variable.
@@ -7440,6 +7440,27 @@
+
+ slave_exec_mode
+
+
+
+
+
+ Controls whether IDEMPOTENT or
+ STRICT mode is used in replication
+ conflict resolution and error checking.
+ IDEMPOTENT mode causes suppression of
+ some errors, including duplicate-key and no-key-found
+ errors. Beginning with MySQL 5.1.24, this mode should be
+ employed in multi-master replication, circular replication,
+ and some other special replication scenarios.
+ STRICT mode is the default, and is
+ suitable for most other cases.
+
+
+
+ slave_load_tmpdir
@@ -8252,18 +8273,6 @@
-
-
- MySQL Enterprise
-
-
- Expert use of server system variables is part of the service
- offered by the MySQL Enterprise Monitor. To subscribe see
- .
-
-
-
-
@@ -9188,9 +9197,8 @@
command set used in the network layer. In other words, their
values increase whenever prepared statement API calls such
as mysql_stmt_prepare(),
- mysql_stmt_execute(), and so forth
- are executed. However,
- Com_stmt_prepare,
+ mysql_stmt_execute(), and so forth are
+ executed. However, Com_stmt_prepare,
Com_stmt_execute and
Com_stmt_close also increase for
PREPARE, EXECUTE, or
@@ -10228,8 +10236,8 @@
The current number of prepared statements. (The maximum
number of statements is given by the
- max_prepared_stmt_count system
- variable.) This variable was added in MySQL 5.1.14.
+ max_prepared_stmt_count system variable.)
+ This variable was added in MySQL 5.1.14.
@@ -10403,7 +10411,7 @@
&mccge-warning-begin;
-
+ Slave_heartbeat_period
Modified: trunk/refman-5.1/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-replication.xml 2008-02-06 10:46:08 UTC (rev 9716)
+++ trunk/refman-5.1/mysql-cluster-replication.xml 2008-02-06 12:54:28 UTC (rev 9717)
Changed blocks: 1, Lines Added: 23, Lines Deleted: 0; 1302 bytes
@@ -455,6 +455,29 @@
be noted that it has not yet been thoroughly tested and must
therefore still be considered experimental.
+
+
+
+ Beginning with MySQL 5.1.24, you should execute the
+ following statement before starting circular replication:
+
+
+mysql> SET GLOBAL SLAVE_EXEC_MODE = 'IDEMPOTENT';
+
+
+ This is necessary to suppress duplicate-key and other errors
+ that otherwise break circular replication of MySQL Cluster.
+ IDEMPOTENT mode is also required for
+ multi-master replication when using MySQL Cluster. (Bug
+ #31609)
+
+
+
+ See
+ Slave_exec_mode,
+ for more information.
+
+
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-02-06 10:46:08 UTC (rev 9716)
+++ trunk/refman-6.0/dba-core.xml 2008-02-06 12:54:28 UTC (rev 9717)
Changed blocks: 1, Lines Added: 21, Lines Deleted: 0; 1325 bytes
@@ -7159,6 +7159,27 @@
+
+ Slave_exec_mode
+
+
+
+
+
+ Controls whether IDEMPOTENT or
+ STRICT mode is used in replication
+ conflict resolution and error checking.
+ IDEMPOTENT mode causes suppression of
+ some errors, including duplicate-key and no-key-found
+ errors. Beginning with MySQL 6.0.5, this mode should be
+ employed in multi-master replication, circular replication,
+ and some other special replication scenarios.
+ STRICT mode is the default, and is
+ suitable for most other cases.
+
+
+
+ slave_load_tmpdir
Modified: trunk/refman-6.0/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-6.0/mysql-cluster-replication.xml 2008-02-06 10:46:08 UTC (rev 9716)
+++ trunk/refman-6.0/mysql-cluster-replication.xml 2008-02-06 12:54:28 UTC (rev 9717)
Changed blocks: 1, Lines Added: 23, Lines Deleted: 0; 1301 bytes
@@ -461,6 +461,29 @@
be noted that it has not yet been thoroughly tested and must
therefore still be considered experimental.
+
+
+
+ Beginning with MySQL 6.0.5, you should execute the following
+ statement before starting circular replication:
+
+
+mysql> SET GLOBAL SLAVE_EXEC_MODE = 'IDEMPOTENT';
+
+
+ This is necessary to suppress duplicate-key and other errors
+ that otherwise break circular replication of MySQL Cluster.
+ IDEMPOTENT mode is also required for
+ multi-master replication when using MySQL Cluster. (Bug
+ #31609)
+
+
+
+ See
+ Slave_exec_mode,
+ for more information.
+
+