List:Commits« Previous MessageNext Message »
From:jon Date:July 24 2008 3:49pm
Subject:svn commit - mysqldoc@docsrva: r11350 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-6.0
View as plain text  
Author: jstephens
Date: 2008-07-24 17:49:45 +0200 (Thu, 24 Jul 2008)
New Revision: 11350

Log:

START SLAVE, Slave_IO_Running, Slave_SQL_Running, and @@init_slave

Fixes Docs Bug #38328



Modified:
   trunk/refman-4.1/dba-core.xml
   trunk/refman-4.1/replication.xml
   trunk/refman-4.1/sql-syntax-replication.xml
   trunk/refman-5.0/dba-core.xml
   trunk/refman-5.0/sql-syntax-replication.xml
   trunk/refman-5.1/dba-core.xml
   trunk/refman-5.1/sql-syntax-replication.xml


Modified: trunk/refman-4.1/dba-core.xml
===================================================================
--- trunk/refman-4.1/dba-core.xml	2008-07-24 15:29:17 UTC (rev 11349)
+++ trunk/refman-4.1/dba-core.xml	2008-07-24 15:49:45 UTC (rev 11350)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 2; 1260 bytes

@@ -4139,9 +4139,23 @@
             This variable is similar to <literal>init_connect</literal>,
             but is a string to be executed by a slave server each time
             the SQL thread starts. The format of the string is the same
-            as for the <literal>init_connect</literal> variable. This
-            variable was added in MySQL 4.1.2.
+            as for the <literal>init_connect</literal> variable.
           </para>
+
+          <note>
+            <para>
+              The SQL thread sends an acknowledgement to the client
+              before <literal>init_slave</literal> is executed.
+              Therefore, it is not guaranteed that
+              <literal>init_slave</literal> has been executed when
+              <literal>START SLAVE</literal> returns. See
+              <xref linkend="start-slave"/>, for more information.
+            </para>
+          </note>
+
+          <para>
+            This variable was added in MySQL 4.1.2.
+          </para>
         </listitem>
 
         <listitem>


Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml	2008-07-24 15:29:17 UTC (rev 11349)
+++ trunk/refman-4.1/replication.xml	2008-07-24 15:49:45 UTC (rev 11350)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 8; 698 bytes

@@ -4139,14 +4139,6 @@
 
     <title>Replication FAQ</title>
 
-<!--  
-      TODO: If I were to change this to a <qanda[set]/>, how badly would 
-      Paul kill me...? ;)
-      
-      More seriously, it would be nice to structure the Q-and-A bits 
-      better - perhaps using 2-item itemized lists? /JS
--->
-
     <para>
       <emphasis role="bold">Q</emphasis>: How do I configure a slave if
       the master is running and I do not want to stop it?


Modified: trunk/refman-4.1/sql-syntax-replication.xml
===================================================================
--- trunk/refman-4.1/sql-syntax-replication.xml	2008-07-24 15:29:17 UTC (rev 11349)
+++ trunk/refman-4.1/sql-syntax-replication.xml	2008-07-24 15:49:45 UTC (rev 11350)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 0; 1241 bytes

@@ -945,6 +945,19 @@
       <remark role="help-description-end"/>
 
       <para>
+        <literal>START SLAVE</literal> sends an acknowledgement to the
+        user after both the IO thread and the SQL thread have started.
+        However, the IO thread may not yet have connected. For this
+        reason, a successful <literal>START SLAVE</literal> causes
+        <literal>SHOW SLAVE STATUS</literal> to show
+        <literal>Slave_SQL_Running=Yes</literal>, but this does not
+        guarantee that <literal>Slave_IO_Running=Yes</literal> (because
+        <literal>Slave_IO_Running=Yes</literal> only if the IO thread is
+        running <emphasis>and connected</emphasis>). For more
+        information, see <xref linkend="show-slave-status"/>.
+      </para>
+
+      <para>
         As of MySQL 4.0.2, you can add <literal>IO_THREAD</literal> and
         <literal>SQL_THREAD</literal> options to the statement to name
         which of the threads to start.


Modified: trunk/refman-5.0/dba-core.xml
===================================================================
--- trunk/refman-5.0/dba-core.xml	2008-07-24 15:29:17 UTC (rev 11349)
+++ trunk/refman-5.0/dba-core.xml	2008-07-24 15:49:45 UTC (rev 11350)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 0; 911 bytes

@@ -4911,6 +4911,17 @@
             the SQL thread starts. The format of the string is the same
             as for the <literal>init_connect</literal> variable.
           </para>
+
+          <note>
+            <para>
+              The SQL thread sends an acknowledgement to the client
+              before <literal>init_slave</literal> is executed.
+              Therefore, it is not guaranteed that
+              <literal>init_slave</literal> has been executed when
+              <literal>START SLAVE</literal> returns. See
+              <xref linkend="start-slave"/>, for more information.
+            </para>
+          </note>
         </listitem>
 
         <listitem>


Modified: trunk/refman-5.0/sql-syntax-replication.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-replication.xml	2008-07-24 15:29:17 UTC (rev 11349)
+++ trunk/refman-5.0/sql-syntax-replication.xml	2008-07-24 15:49:45 UTC (rev 11350)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 0; 1287 bytes

@@ -930,6 +930,20 @@
       <remark role="help-description-end"/>
 
       <para>
+        <literal>START SLAVE</literal> sends an acknowledgement to the
+        user after both the IO thread and the SQL thread have started.
+        However, the IO thread may not yet have connected. For this
+        reason, a successful <literal>START SLAVE</literal> causes
+        <literal>SHOW SLAVE STATUS</literal> to show
+        <literal>Slave_SQL_Running=Yes</literal>, but this does not
+        guarantee that <literal>Slave_IO_Running=Yes</literal> (because
+        <literal>Slave_IO_Running=Yes</literal> only if the IO thread is
+        running <emphasis>and connected</emphasis>). For more
+        information, see <xref linkend="show-slave-status"/>, and
+        <xref linkend="replication-administration-status"/>.
+      </para>
+
+      <para>
         You can add <literal>IO_THREAD</literal> and
         <literal>SQL_THREAD</literal> options to the statement to name
         which of the threads to start.


Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml	2008-07-24 15:29:17 UTC (rev 11349)
+++ trunk/refman-5.1/dba-core.xml	2008-07-24 15:49:45 UTC (rev 11350)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 1; 960 bytes

@@ -5185,6 +5185,17 @@
             the SQL thread starts. The format of the string is the same
             as for the <literal>init_connect</literal> variable.
           </para>
+
+          <note>
+            <para>
+              The SQL thread sends an acknowledgement to the client
+              before <literal>init_slave</literal> is executed.
+              Therefore, it is not guaranteed that
+              <literal>init_slave</literal> has been executed when
+              <literal>START SLAVE</literal> returns. See
+              <xref linkend="start-slave"/>, for more information.
+            </para>
+          </note>
         </listitem>
 
         <listitem>

@@ -23184,4 +23195,3 @@
   </section>
 
 </chapter>
-


Modified: trunk/refman-5.1/sql-syntax-replication.xml
===================================================================


Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 120 bytes


Thread
svn commit - mysqldoc@docsrva: r11350 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-6.0jon24 Jul