Author: jstephens
Date: 2008-02-18 13:46:32 +0100 (Mon, 18 Feb 2008)
New Revision: 9895
Log:
Remaining edits for multi-master replication upgrade draft doc
Modified:
trunk/refman-5.1/replication-multi-master-upgrade.xml
Modified: trunk/refman-5.1/replication-multi-master-upgrade.xml
===================================================================
--- trunk/refman-5.1/replication-multi-master-upgrade.xml 2008-02-18 12:45:46 UTC (rev 9894)
+++ trunk/refman-5.1/replication-multi-master-upgrade.xml 2008-02-18 12:46:32 UTC (rev 9895)
Changed blocks: 3, Lines Added: 103, Lines Deleted: 2; 4534 bytes
@@ -458,7 +458,17 @@
</programlisting>
Once A has executed all events up to and including the
- marker event, it stops.
+ marker event, it stops, as shown here:
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="../refman-common/images/published/rpl-circular-upgrade-6.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Second marker event propagates
+ from server B to server A</phrase>
+ </textobject>
+ </mediaobject>
</para>
</listitem>
@@ -489,6 +499,18 @@
START SLAVE;
</programlisting>
+
+ Replication now occurs as shown here:
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="../refman-common/images/published/rpl-circular-upgrade-7.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">Server B now replicates to server
+ C'</phrase>
+ </textobject>
+ </mediaobject>
</para>
</formalpara>
@@ -499,12 +521,91 @@
<title>Start replication from C' to A</title>
- <para></para>
+ <para>
+ This can be done as follows:
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Locate the file and position of the second marker
+ event in the binary log on server C'. This can be
+ found by issuing <literal>SHOW BINLOG EVENTS</literal>
+ on C' as previously described.
+ </para>
+
+ <para>
+ We denote the file and position within this file as
+ <replaceable>fileC'</replaceable> and
+ <replaceable>posC'</replaceable>, respectively.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Start replication on A from this point by issuing the
+ following statements, where
+ <replaceable>hostC'</replaceable> represents the
+ hostname or IP address of server C', and
+ <replaceable>fileC'</replaceable> and
+ <replaceable>posC'</replaceable> are defined as
+ stated in the previous item:
+
+<programlisting>
+CHANGE MASTER TO
+ MASTER_HOST=<replaceable>hostC'</replaceable>,
+ MASTER_LOG_FILE=<replaceable>fileC'</replaceable>,
+ MASTER_LOG_POS=<replaceable>posC'</replaceable>;
+
+START SLAVE;
+</programlisting>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
</formalpara>
</listitem>
+ <listitem>
+ <formalpara>
+
+ <title>Return server A to online status</title>
+
+ <para>
+ This can be done by setting
+ <literal>@@GLOBAL.MAX_CONNECTIONS</literal> to an
+ appropriate value, thereby permitting regular clients not
+ having the <literal>SUPER</literal> privilege once again to
+ connect.
+ </para>
+
+ </formalpara>
+ </listitem>
+
</orderedlist>
</para>
+ <para>
+ At this point, the original replication topology has been restored,
+ and all is as before, except that server C running MySQL version X
+ has been upgrade to C' running MySQL version Y, as shown here:
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="../refman-common/images/published/rpl-circular-upgrade-8.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase lang="en">The circular replication topology is now
+ restored, with server A replicating to server B, server B
+ replicating to server C', and server C' replicating to
+ server A</phrase>
+ </textobject>
+ </mediaobject>
+
+ You can now complete the software upgrade process by repeating the
+ steps shown previously for servers A and B, each in turn.
+ </para>
+
</section>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r9895 - trunk/refman-5.1 | jon | 18 Feb |
