Author: jstephens
Date: 2008-02-17 16:01:34 +0100 (Sun, 17 Feb 2008)
New Revision: 9887
Log:
Added some diagrams to multi-master upgrade doc in progress.
Added:
trunk/refman-common/images/published/rpl-circular-upgrade-2.png
trunk/refman-common/images/published/rpl-circular-upgrade-3.png
trunk/refman-common/images/published/rpl-circular-upgrade-4.png
trunk/refman-common/images/source/rpl-circular-upgrade-3.dia
trunk/refman-common/images/source/rpl-circular-upgrade-4.dia
Modified:
trunk/refman-5.1/replication-multi-master-upgrade.xml
trunk/refman-common/images/source/rpl-circular-upgrade-2.dia
Property changes on: trunk/refman-common/images/published/rpl-circular-upgrade-2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/refman-common/images/published/rpl-circular-upgrade-3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/refman-common/images/published/rpl-circular-upgrade-4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/refman-common/images/source/rpl-circular-upgrade-3.dia
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Property changes on: trunk/refman-common/images/source/rpl-circular-upgrade-4.dia
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: trunk/refman-5.1/replication-multi-master-upgrade.xml
===================================================================
--- trunk/refman-5.1/replication-multi-master-upgrade.xml 2008-02-17 12:15:30 UTC (rev 9886)
+++ trunk/refman-5.1/replication-multi-master-upgrade.xml 2008-02-17 15:01:34 UTC (rev 9887)
Changed blocks: 5, Lines Added: 81, Lines Deleted: 36; 5138 bytes
@@ -39,43 +39,49 @@
slave of server B and a master to server A.
</para>
- <para>
- Each MySQL server involved in replication records those events that
- have been sent to it from another server for execution. For server
- C, at a given point in time, we need to answer the following
- questions:
+ <formalpara>
- <orderedlist>
+ <title>Questions about replication events</title>
- <listitem>
- <para>
- Which events have been received by server C from server B?
- </para>
- </listitem>
+ <para>
+ Each MySQL server involved in replication records those events
+ that have been sent to it from another server for execution. For
+ server C, at a given point in time, we need to answer the
+ following questions:
- <listitem>
- <para>
- Which events, received by server C from server B, have been
- executed on server C?
- </para>
- </listitem>
+ <orderedlist>
- <listitem>
- <para>
- Which events have been sent by server C to server A?
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Which events have been received by server C from server B?
+ </para>
+ </listitem>
- <listitem>
- <para>
- Which events, received by server A from server C, have been
- executed on server A?
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Which events, received by server C from server B, have been
+ executed on server C?
+ </para>
+ </listitem>
- </orderedlist>
- </para>
+ <listitem>
+ <para>
+ Which events have been sent by server C to server A?
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Which events, received by server A from server C, have been
+ executed on server A?
+ </para>
+ </listitem>
+
+ </orderedlist>
+ </para>
+
+ </formalpara>
+
<para>
To upgrade this server, we need to perform the following steps:
@@ -104,9 +110,12 @@
<para>
Execute a statement on B that generates an event which is
- easily identified. For this example, we assume that there is
- no table named marker in the test database, and perform the
- following statements to create it:
+ easily identified; this provides a point of reference to
+ assist in answering the <citetitle>Questions about
+ replication events</citetitle> listed previously. For this
+ example, we assume that there is no table named marker in
+ the test database, and perform the following statements to
+ create it:
<programlisting>
USE test;
@@ -159,7 +168,18 @@
This causes C to execute any remaining events sent from B up
to the point where the <quote>marker</quote> statement was
- issued, and then to stop.
+ issued, and then to stop. The place of the marker in the
+ sequence of events flowing from B to C is illustrated here:
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="../refman-common/images/published/rpl-circular-upgrade-2.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Marker event created on server B in
+ the flow of events from B to C</phrase>
+ </textobject>
+ </mediaobject>
</para>
</formalpara>
@@ -271,7 +291,18 @@
This causes any remaining unprocessed events up the marker
event on C to be executed on A, and causes A to stop once
- this has been done.
+ this has been done. The propagation of the marker to A from
+ C is shown here:
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="../refman-common/images/published/rpl-circular-upgrade-3.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Marker event propagates from server C
+ to server A</phrase>
+ </textobject>
+ </mediaobject>
</para>
</formalpara>
@@ -306,7 +337,21 @@
</listitem>
</orderedlist>
-
+
+ C is now isolated from the other two servers, which are now
+ replicating to each other, as shown here:
+
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="../refman-common/images/published/rpl-circular-upgrade-4.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Servers A and B in mutual replication; C is
+ isolated</phrase>
+ </textobject>
+ </mediaobject>
+
<itemizedlist>
<listitem>
Added: trunk/refman-common/images/published/rpl-circular-upgrade-2.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 357 bytes
Added: trunk/refman-common/images/published/rpl-circular-upgrade-3.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 357 bytes
Added: trunk/refman-common/images/published/rpl-circular-upgrade-4.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 357 bytes
Modified: trunk/refman-common/images/source/rpl-circular-upgrade-2.dia
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 158 bytes
Added: trunk/refman-common/images/source/rpl-circular-upgrade-3.dia
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 351 bytes
Added: trunk/refman-common/images/source/rpl-circular-upgrade-4.dia
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 351 bytes
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r9887 - in trunk: refman-5.1 refman-common/images/published refman-common/images/source | jon | 17 Feb |
