Author: jstephens
Date: 2009-10-09 12:51:21 +0200 (Fri, 09 Oct 2009)
New Revision: 17042
Log:
Documented Replication bugfixes:
Bug #13963, Bug #45674, Bug #45848, Bug #45852
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2009-10-09 09:37:45 UTC (rev 17041)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2009-10-09 10:51:21 UTC (rev 17042)
Changed blocks: 1, Lines Added: 127, Lines Deleted: 0; 3372 bytes
@@ -9,6 +9,133 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="replication"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="45852"/>
+ </bugs>
+
+ <versions>
+ <version ver="6.0.14"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When using semi-synchronous replication, an error raised on the
+ slave while sending a response to the master caused the slave IO
+ thread to stop.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="replication"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="45848"/>
+ </bugs>
+
+ <versions>
+ <version ver="6.0.14"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Semi-synchronous replication used an extra connection from slave
+ to master to send replies. This was a regular client connection,
+ and used a normal
+ <literal role="stmt" condition="set-option">SET</literal>
+ statement to set the reply information on master. This was
+ visible to users and had the potential to add undesired extra
+ output to the query log, the output of <literal role="stmt">SHOW
+ PROCESSLIST</literal>, or both.
+ </para>
+
+ <para>
+ We have rectified this issue by reverting to the previous method
+ of sending replies to the master via the same connection that is
+ used to send binary logging information.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="replication"/>
+ <manual type="FLUSH STATUS"/>
+ <manual type="Rpl_semi_sync_master_yes_tx"/>
+ <manual type="Rpl_semi_sync_master_no_tx"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="45674"/>
+ </bugs>
+
+ <versions>
+ <version ver="6.0.14"/>
+ </versions>
+
+ <message>
+
+ <para>
+ <literal role="stmt" condition="flush">FLUSH STATUS</literal>
+ failed to reset the status variables
+ <literal role="statvar">Rpl_semi_sync_master_yes_tx</literal>
+ and
+ <literal role="statvar">Rpl_semi_sync_master_no_tx</literal>.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="replication"/>
+ <manual type="SHOW SLAVE HOSTS"/>
+ <manual type="--report-hosts"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="13963"/>
+ <seealsobug bugid="21132"/>
+ <seealsobug bugid="21869"/>
+ </bugs>
+
+ <versions>
+ <version ver="6.0.14"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Formerly, only slaves that had been started with the
+ <option role="mysqld">--report-hosts</option> option were
+ visible in the output of <literal role="stmt">SHOW SLAVE
+ HOSTS</literal>. Now, all slaves that are registered with the
+ master appear in <literal role="stmt">SHOW SLAVE HOSTS</literal>
+ output.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
<highlight type="clusterreplication"/>
<manual type="mysqlbinlog"/>
<manual type="--ndb-log-update-as-write"/>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r17042 - trunk/dynamic-docs/changelog | jon.stephens | 9 Oct |
