List:Commits« Previous MessageNext Message »
From:jon.stephens Date:April 5 2011 12:36pm
Subject:svn commit - mysqldoc@oter02: r25730 - in trunk: dynamic-docs/changelog refman-5.6
View as plain text  
Author: js221926
Date: 2011-04-05 14:36:15 +0200 (Tue, 05 Apr 2011)
New Revision: 25730

Log:

Changelog entry for Replication BUG#11765887 / BUG#58897

Related additions/improvements to replication status log tables/options info (Thanks, Alfranio!)



Modified:
   trunk/dynamic-docs/changelog/mysqld-2.xml
   trunk/refman-5.6/dba-log-files.xml
   trunk/refman-5.6/introduction.xml
   trunk/refman-5.6/replication-implementation.xml
   trunk/refman-5.6/replication-options-core.xml


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2011-04-05 06:06:22 UTC (rev 25729)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2011-04-05 12:36:15 UTC (rev 25730)
Changed blocks: 1, Lines Added: 39, Lines Deleted: 0; 1372 bytes

@@ -6,6 +6,45 @@
 ]>
 <changelog>
 
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="replication"/>
+      <manual type="slave_master_info"/>
+      <manual type="slave_relay_log_info"/>
+      <manual type="storage engines"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="11765887"/>
+      <fixes bugid="58897"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        It is no longer possible to change the storage engine used by
+        the <literal>mysql.slave_master_info</literal> and
+        <literal>mysql.slave_relay_log_info</literal> tables while
+        replication is running. This means that, in order to make
+        replication crash-safe, you must make sure that both of these
+        tables use a transactional storage engine before starting
+        replication.
+      </para>
+
+      <para>
+        For more information, see <xref linkend="slave-logs"/>, and
+        <xref linkend="replication-options-slave-log-tables"/>.
+      </para>
+
+    </message>
+
+  </logentry>
+
   <logentry entrytype="feature">
 
     <tags>


Modified: trunk/refman-5.6/dba-log-files.xml
===================================================================
--- trunk/refman-5.6/dba-log-files.xml	2011-04-05 06:06:22 UTC (rev 25729)
+++ trunk/refman-5.6/dba-log-files.xml	2011-04-05 12:36:15 UTC (rev 25730)
Changed blocks: 2, Lines Added: 6, Lines Deleted: 1; 752 bytes

@@ -789,7 +789,7 @@
 
     <para>
       Beginning with MySQL 5.6.2, the binary log is crash-safe. Only
-      complete events (or transactions) are logged or read back.
+      complete events or transactions are logged or read back.
     </para>
 
     <para>

@@ -1441,6 +1441,11 @@
         </para>
       </warning>
 
+      <para>
+        For information about logs kept by replication slaves, see
+        <xref linkend="slave-logs"/>.
+      </para>
+
     </section>
 
     <section id="binary-log-mixed">


Modified: trunk/refman-5.6/introduction.xml
===================================================================
--- trunk/refman-5.6/introduction.xml	2011-04-05 06:06:22 UTC (rev 25729)
+++ trunk/refman-5.6/introduction.xml	2011-04-05 12:36:15 UTC (rev 25730)
Changed blocks: 1, Lines Added: 19, Lines Deleted: 0; 1393 bytes

@@ -607,6 +607,25 @@
           Both of these tables are created automatically, in the
           <literal>mysql</literal> system database.
         </para>
+
+        <important>
+          <para>
+            In order for replication to be crash-safe, the
+            <literal>slave_master_info</literal> and
+            <literal>slave_relay_log_info</literal> tables must each use
+            a transactional storage engine. By default, both of these
+            tables use <literal role="se">MyISAM</literal>; this means
+            that, prior to starting replication, you must change both of
+            these tables to use a transaction storage engine if you wish
+            for replication to be crash-safe. You can do this by means
+            of the appropriate
+            <literal role="stmt" condition="alter-table">ALTER TABLE ...
+            ENGINE=...</literal> statements. You should
+            <emphasis>not</emphasis> attempt to change the storage
+            engine used by either of these tables while replication is
+            actually running.
+          </para>
+        </important>
       </listitem>
 
       <listitem>


Modified: trunk/refman-5.6/replication-implementation.xml
===================================================================
--- trunk/refman-5.6/replication-implementation.xml	2011-04-05 06:06:22 UTC (rev 25729)
+++ trunk/refman-5.6/replication-implementation.xml	2011-04-05 12:36:15 UTC (rev 25730)
Changed blocks: 2, Lines Added: 71, Lines Deleted: 0; 2863 bytes

@@ -287,6 +287,49 @@
 
     <title>Replication Relay and Status Logs</title>
 
+    <indexterm>
+      <primary>replication</primary>
+      <secondary>relay logs</secondary>
+    </indexterm>
+
+    <indexterm>
+      <primary>replication</primary>
+      <secondary>status logs</secondary>
+    </indexterm>
+
+    <indexterm>
+      <primary>relay logs (replication)</primary>
+    </indexterm>
+
+    <indexterm>
+      <primary>status logs (replication)</primary>
+    </indexterm>
+
+    <indexterm>
+      <primary>mysql.slave_master_info table</primary>
+    </indexterm>
+
+    <indexterm>
+      <primary>mysql.slave_relay_log_info table</primary>
+    </indexterm>
+
+    <indexterm>
+      <primary>--master-info-repository option</primary>
+    </indexterm>
+
+    <indexterm>
+      <primary>--relay-log-info-repository option</primary>
+    </indexterm>
+
+    <indexterm>
+      <primary>replication log tables</primary>
+    </indexterm>
+
+    <indexterm>
+      <primary>ALTER TABLE</primary>
+      <secondary>and replication log tables</secondary>
+    </indexterm>
+
     <para>
       During replication, a slave server creates several logs that hold
       the binary log events relayed from the master to the slave, and to

@@ -345,6 +388,34 @@
 
     </itemizedlist>
 
+    <para>
+      In order for replication to be crash-safe when using tables for
+      logging status and relay information, the tables must use a
+      transactional storage engine, such as
+      <literal role="se">InnoDB</literal>. However, the
+      <literal>slave_master_info</literal> and
+      <literal>slave_relay_log_info</literal> tables use
+      <literal role="se">MyISAM</literal> by default. This means that
+      you must change the storage engine used by these tables before
+      starting replication. You can do this by issuing the following
+      statements on the slave:
+    </para>
+
+<programlisting>
+ALTER TABLE mysql.slave_master_info ENGINE=InnoDB;
+ALTER TABLE mysql.slave_relay_log_info ENGINE=InnoDB;
+</programlisting>
+
+    <para>
+      The <literal role="stmt">ALTER TABLE</literal> statements must be
+      executed by the MySQL <literal>root</literal> or other user
+      account with the appropriate privileges on the
+      <literal>mysql</literal> database. You should not attempt to do
+      this while replication is running; beginning with MySQL 5.6.3,
+      trying to execute an <literal role="stmt">ALTER TABLE</literal> on
+      either these tables while replication is ongoing is disallowed.
+    </para>
+
     <important>
       <para>
         Do not attempt to update or insert rows in the


Modified: trunk/refman-5.6/replication-options-core.xml
===================================================================
--- trunk/refman-5.6/replication-options-core.xml	2011-04-05 06:06:22 UTC (rev 25729)
+++ trunk/refman-5.6/replication-options-core.xml	2011-04-05 12:36:15 UTC (rev 25730)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 704 bytes

@@ -3274,7 +3274,7 @@
       option.
     </para>
 
-    <formalpara>
+    <formalpara id="replication-options-slave-log-tables">
 
       <title>Options for logging slave status to tables</title>
 

@@ -3370,7 +3370,7 @@
     </itemizedlist>
 
     <para>
-      For more information, see <xref linkend="slave-logs-status"/>.
+      For more information, see <xref linkend="slave-logs"/>.
     </para>
 
     <remark role="note">


Thread
svn commit - mysqldoc@oter02: r25730 - in trunk: dynamic-docs/changelog refman-5.6jon.stephens5 Apr