Author: jstephens
Date: 2007-04-20 11:15:00 +0200 (Fri, 20 Apr 2007)
New Revision: 6020
Log:
Noted incompatible change in mysql.ndb_apply_status table for 5.1.18
(see Bug #27936).
Updated Cluster upgrade/downgrade compatibility chart; converted base
file to XHTML.
Added "almost online" 5.1.17- _> 5.1.18+ upgrade procedure recommended
by Tomas.
Modified:
trunk/refman-4.1/images/cluster-upgrade-downgrade-table.png
trunk/refman-4.1/mysql-cluster.xml
trunk/refman-5.0/images/cluster-upgrade-downgrade-table.png
trunk/refman-5.0/mysql-cluster.xml
trunk/refman-5.1/images/cluster-upgrade-downgrade-table.png
trunk/refman-5.1/mysql-cluster.xml
trunk/refman-5.1/news-5.1.xml
trunk/refman-common/cluster-graphics/images/cluster-upgrade-downgrade-table.png
trunk/refman-common/cluster-graphics/upgrade-downgrade-compat-table.html
trunk/refman-common/images/cluster-upgrade-downgrade-table.png
Modified: trunk/refman-4.1/images/cluster-upgrade-downgrade-table.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 157 bytes
Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml 2007-04-20 08:51:39 UTC (rev 6019)
+++ trunk/refman-4.1/mysql-cluster.xml 2007-04-20 09:15:00 UTC (rev 6020)
Changed blocks: 1, Lines Added: 54, Lines Deleted: 0; 2870 bytes
@@ -8677,6 +8677,60 @@
changes in the cluster system tables.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ Online upgrades from MySQL 5.1.17 and earlier to 5.1.18 and
+ later are not supported for clusters using replication due
+ to incompatible changes in the
+ <literal>mysql.ndb_apply_status</literal> table. However, it
+ should not be necessary to shut down the cluster entirely,
+ if you follow this modified rolling restart procedure:
+
+ <orderedlist>
+ <listitem>
+ <para>
+ Stop the management server, update the
+ <literal>ndb_mgmd</literal> binary, then start it
+ again. For multiple management servers, repeat this
+ step for each management server in turn.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For each data node in turn: Stop the data node,
+ replace the <literal>ndbd</literal> binary with the
+ new version, then restart the data node. It is not
+ necessary to use <literal>--initial</literal> when
+ restarting any of the data nodes.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Stop <emphasis>all</emphasis> SQL nodes. Replace the
+ <command>mysqld</command> binary with the new version
+ for all SQL nodes, then restart them. It is not
+ necessary to start them one at a time, but they must
+ all be shut down at the same time before starting any
+ of them again using the 5.1.18 (or later)
+ <command>mysqld</command>. Otherwise — due to
+ the fact that
+ <literal>mysql.ndb_apply_status</literal> uses the
+ <literal>NDB</literal> storage engine and is thus
+ shared between all SQL nodes — there may be
+ conflicts between MySQL servers using the old and
+ new versions of the table.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ You can find more information about the changes to
+ <literal>ndb_apply_status</literal> in the <citetitle>MySQL
+ 5.1 Manual</citetitle>.
+ </para>
+ </listitem>
</itemizedlist>
Modified: trunk/refman-5.0/images/cluster-upgrade-downgrade-table.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 157 bytes
Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml 2007-04-20 08:51:39 UTC (rev 6019)
+++ trunk/refman-5.0/mysql-cluster.xml 2007-04-20 09:15:00 UTC (rev 6020)
Changed blocks: 1, Lines Added: 54, Lines Deleted: 0; 2869 bytes
@@ -8702,6 +8702,60 @@
changes in the cluster system tables.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ Online upgrades from MySQL 5.1.17 and earlier to 5.1.18 and
+ later are not supported for clusters using replication due
+ to incompatible changes in the
+ <literal>mysql.ndb_apply_status</literal> table. However, it
+ should not be necessary to shut down the cluster entirely,
+ if you follow this modified rolling restart procedure:
+
+ <orderedlist>
+ <listitem>
+ <para>
+ Stop the management server, update the
+ <literal>ndb_mgmd</literal> binary, then start it
+ again. For multiple management servers, repeat this
+ step for each management server in turn.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For each data node in turn: Stop the data node,
+ replace the <literal>ndbd</literal> binary with the
+ new version, then restart the data node. It is not
+ necessary to use <literal>--initial</literal> when
+ restarting any of the data nodes.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Stop <emphasis>all</emphasis> SQL nodes. Replace the
+ <command>mysqld</command> binary with the new version
+ for all SQL nodes, then restart them. It is not
+ necessary to start them one at a time, but they must
+ all be shut down at the same time before starting any
+ of them again using the 5.1.18 (or later)
+ <command>mysqld</command>. Otherwise — due to
+ the fact that
+ <literal>mysql.ndb_apply_status</literal> uses the
+ <literal>NDB</literal> storage engine and is thus
+ shared between all SQL nodes — there may be
+ conflicts between MySQL servers using the old and
+ new versions of the table.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ You can find more information about the changes to
+ <literal>ndb_apply_status</literal> in the <citetitle>MySQL
+ 5.1 Manual</citetitle>.
+ </para>
+ </listitem>
</itemizedlist>
Modified: trunk/refman-5.1/images/cluster-upgrade-downgrade-table.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 157 bytes
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-04-20 08:51:39 UTC (rev 6019)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-04-20 09:15:00 UTC (rev 6020)
Changed blocks: 4, Lines Added: 87, Lines Deleted: 15; 5747 bytes
@@ -8820,6 +8820,60 @@
changes in the cluster system tables.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ Online upgrades from MySQL 5.1.17 and earlier to 5.1.18 and
+ later are not supported for clusters using replication due
+ to incompatible changes in the
+ <literal>mysql.ndb_apply_status</literal> table. However, it
+ should not be necessary to shut down the cluster entirely,
+ if you follow this modified rolling restart procedure:
+
+ <orderedlist>
+ <listitem>
+ <para>
+ Stop the management server, update the
+ <literal>ndb_mgmd</literal> binary, then start it
+ again. For multiple management servers, repeat this
+ step for each management server in turn.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For each data node in turn: Stop the data node,
+ replace the <literal>ndbd</literal> binary with the
+ new version, then restart the data node. It is not
+ necessary to use <literal>--initial</literal> when
+ restarting any of the data nodes.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Stop <emphasis>all</emphasis> SQL nodes. Replace the
+ <command>mysqld</command> binary with the new version
+ for all SQL nodes, then restart them. It is not
+ necessary to start them one at a time, but they must
+ all be shut down at the same time before starting any
+ of them again using the 5.1.18 (or later)
+ <command>mysqld</command>. Otherwise — due to
+ the fact that
+ <literal>mysql.ndb_apply_status</literal> uses the
+ <literal>NDB</literal> storage engine and is thus
+ shared between all SQL nodes — there may be
+ conflicts between MySQL servers using the old and
+ new versions of the table.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ You can find more information about the changes to
+ <literal>ndb_apply_status</literal> in
+ <xref linkend="mysql-cluster-replication-schema"/>.
+ </para>
+ </listitem>
</itemizedlist>
@@ -17243,7 +17297,7 @@
<section id="mysql-cluster-replication-schema">
- <title>Replication Schema and Tables</title>
+ <title>Cluster Replication Schema and Tables</title>
<indexterm>
<primary>MySQL Cluster replication</primary>
@@ -17259,25 +17313,25 @@
<primary><literal>cluster_replication</literal> database (obsolete)</primary>
<!-- <see>MySQL Cluster replication</see> -->
</indexterm>
-
+
<indexterm>
<primary><literal>binlog_index</literal> table (obsolete)</primary>
-<!-- <seealso>MySQL Cluster replication</seealso> -->
+ <!-- <seealso>MySQL Cluster replication</seealso> -->
</indexterm>
-
+
<indexterm>
- <primary><literal>ndb_binlog_index</literal> table (MySQL CLuster replication)</primary>
-<!-- <seealso>MySQL Cluster replication</seealso> -->
+ <primary><literal>ndb_binlog_index</literal> table (MySQL Cluster replication)</primary>
+ <!-- <seealso>MySQL Cluster replication</seealso> -->
</indexterm>
-
+
<indexterm>
<primary><literal>cluster.binlog_index</literal> table (obsolete)</primary>
-<!-- <see>MySQL Cluster replication</see> -->
+ <!-- <see>MySQL Cluster replication</see> -->
</indexterm>
-
+
<indexterm>
<primary><literal>mysql.ndb_binlog_index</literal> table</primary>
-<!-- <see>MySQL Cluster replication</see> -->
+ <!-- <see>MySQL Cluster replication</see> -->
</indexterm>
<para>
@@ -17368,14 +17422,32 @@
<literal>ndb_apply_status</literal> can use the <literal>NDB
Cluster</literal> storage engine, as shown here:
</para>
-
+
<programlisting>
CREATE TABLE `ndb_apply_status` (
- `server_id` INT(10) UNSIGNED NOT NULL,
- `epoch` BIGINT(20) UNSIGNED NOT NULL,
- PRIMARY KEY USING HASH (`server_id`)
-) ENGINE=NDBCLUSTER DEFAULT CHARSET=latin1;
+ `server_id` INT(10) UNSIGNED NOT NULL,
+ `epoch` BIGINT(20) UNSIGNED NOT NULL,
+ `log_name` VARCHAR(255) CHARACTER SET latin1 COLLATE latin1_bin NOT NULL,
+ `start_pos` BIGINT(20) UNSIGNED NOT NULL,
+ `end_pos` BIGINT(20) UNSIGNED NOT NULL,
+ PRIMARY KEY (`server_id`) USING HASH
+) ENGINE=NDBCLUSTER DEFAULT CHARSET=latin1;
</programlisting>
+
+ <para>
+ The <literal>log_name</literal>, <literal>start_pos</literal>,
+ and <literal>end_pos</literal> columns were added in MySQL
+ 5.1.18.
+ </para>
+
+ <important>
+ <para>
+ If you are using MySQL Cluster replication, see
+ <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>
+ before upgrading to MySQL 5.1.18 or later from an earlier
+ version.
+ </para>
+ </important>
<para>
The <literal>ndb_binlog_index</literal> and
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-04-20 08:51:39 UTC (rev 6019)
+++ trunk/refman-5.1/news-5.1.xml 2007-04-20 09:15:00 UTC (rev 6020)
Changed blocks: 2, Lines Added: 21, Lines Deleted: 2; 1441 bytes
@@ -136,6 +136,26 @@
<xref linkend="mysql-cluster-restore"/>.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>
+ (Replication)/<emphasis role="bold">Incompatible
+ Change</emphasis>: The definition of the
+ <literal>mysql.ndb_apply_status</literal> table has changed
+ such that an online upgrade is not possible from MySQL 5.1.17
+ or earlier for a replication slave cluster; you must shut down
+ all SQL nodes as part of the upgrade procedure. See
+ <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>
+ before upgrading for details.
+ </para>
+
+ <para>
+ For more information about the changes to
+ <literal>mysql.ndb_apply_status</literal> see
+ <xref linkend="mysql-cluster-replication-schema"/>.
+ </para>
+ </listitem>
</itemizedlist>
@@ -5004,8 +5024,7 @@
<para>
For more information, see
- <xref
- linkend="mysql-cluster-replication-schema"/>.
+ <xref linkend="mysql-cluster-replication-schema"/>.
</para>
</listitem>
Modified: trunk/refman-common/cluster-graphics/images/cluster-upgrade-downgrade-table.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 177 bytes
Modified: trunk/refman-common/cluster-graphics/upgrade-downgrade-compat-table.html
===================================================================
--- trunk/refman-common/cluster-graphics/upgrade-downgrade-compat-table.html 2007-04-20 08:51:39 UTC (rev 6019)
+++ trunk/refman-common/cluster-graphics/upgrade-downgrade-compat-table.html 2007-04-20 09:15:00 UTC (rev 6020)
Changed blocks: 6, Lines Added: 33, Lines Deleted: 27; 6946 bytes
@@ -1,38 +1,42 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<style type="text/css">
td {padding-left:2px;}
-body {background-color:#FFF;}
+body {background-color:#FFFFFF;}
table, td {border-color:#000;}
img {
margin: 0px;
padding: 0px;
}
+body,td,th {
+ font-family: Arial, Helvetica, sans-serif;
+ font-size: small;
+ color: #000000;
+}
</style>
</head>
<body>
<table border="1" cellspacing="0" cellpadding="0">
<tr>
- <th height="30" colspan="3" nowrap scope="col">MySQL 4.1</th>
- <th width="25" rowspan="36" nowrap scope="col"> </th>
+ <th height="30" colspan="3" nowrap="nowrap" scope="col">MySQL 4.1</th>
+ <th width="25" rowspan="36" nowrap="nowrap" scope="col"> </th>
<th width="1" rowspan="36" bgcolor="#000000" scope="col"></th>
- <th width="25" rowspan="36" nowrap scope="col"> </th>
- <th height="30" colspan="3" nowrap scope="col">MySQL 5.0</th>
- <th width="25" rowspan="36" nowrap scope="col"> </th>
+ <th width="25" rowspan="36" nowrap="nowrap" scope="col"> </th>
+ <th height="30" colspan="3" nowrap="nowrap" scope="col">MySQL 5.0</th>
+ <th width="25" rowspan="36" nowrap="nowrap" scope="col"> </th>
<th width="1" rowspan="36" bgcolor="#000000" scope="col"></th>
- <th width="25" rowspan="36" nowrap scope="col"> </th>
- <th height="30" colspan="3" nowrap scope="col">MySQL 5.1</th>
+ <th width="25" rowspan="36" nowrap="nowrap" scope="col"> </th>
+ <th height="30" colspan="3" nowrap="nowrap" scope="col">MySQL 5.1</th>
</tr>
<tr>
<td colspan="3" rowspan="19" bgcolor="#CCCCCC" scope="col"> </td>
- <th rowspan="25" nowrap scope="col"><img src="images/up-down.png" width="20" height="520"></th>
+ <th rowspan="25" nowrap="nowrap" scope="col"><img src="images/up-down.png" alt="-" width="20" height="520"/></th>
<td scope="col"> 5.0.40 </td>
- <th rowspan="24" nowrap scope="col"> </th>
+ <th rowspan="24" nowrap="nowrap" scope="col"> </th>
<td colspan="3" rowspan="22" bgcolor="#CCCCCC" scope="col"> </td>
</tr>
<tr>
@@ -90,7 +94,7 @@
<td> 5.0.18 </td>
</tr>
<tr>
- <td rowspan="9" bgcolor="#FFFFFF" scope="col"><img src="images/up-down.png" width="20" height="180"></td>
+ <td rowspan="9" bgcolor="#FFFFFF" scope="col"><img src="images/up-down.png" alt="-" width="20" height="180"/></td>
<td bgcolor="#FFFFFF" scope="col"> 4.1.23 </td>
<td rowspan="8" bgcolor="#FFFFFF" scope="col"> </td>
<td> 5.0.17 </td>
@@ -106,24 +110,26 @@
<tr>
<td> 4.1.20 </td>
<td> 5.0.14 </td>
- <td rowspan="5" bgcolor="#FFFFFF" scope="col"><img src="images/up-down.png" width="20" height="100"></td>
+ <td bgcolor="#FFFFFF" scope="col"> </td>
<td bgcolor="#FFFFFF" scope="col"> 5.1.18 </td>
- <td width="25" rowspan="4" bgcolor="#FFFFFF" scope="col"> </td>
+ <td width="25" rowspan="2" bgcolor="#FFFFFF" scope="col"><img src="images/up.png" alt="-" width="20" height="40"/></td>
</tr>
<tr>
<td> 4.1.19 </td>
<td> 5.0.13 </td>
+ <td rowspan="4" bgcolor="#FFFFFF" scope="col"><img src="images/up-down.png" alt="-" width="20" height="80"/></td>
<td bgcolor="#FFFFFF" scope="col"> 5.1.17 </td>
</tr>
<tr>
<td> 4.1.18 </td>
<td> 5.0.12 </td>
- <td rowspan="2"><img src="images/up.png" width="20" height="40"></td>
+ <td rowspan="2"><img alt="-" src="images/up.png" width="20" height="40" border="0"/></td>
<td bgcolor="#FFFFFF"> 5.1.16 </td>
+ <td width="25" rowspan="2" bgcolor="#FFFFFF" scope="col"> </td>
</tr>
<tr>
<td> 4.1.17 </td>
- <td rowspan="10"><img src="images/up-down.png" width="20" height="200"></td>
+ <td rowspan="10"><img src="images/up-down.png" alt="" width="20" height="200"/></td>
<td> 5.0.11 </td>
<td> 5.1.15 </td>
</tr>
@@ -132,20 +138,20 @@
<td> 5.0.10 </td>
<td rowspan="9"></td>
<td> 5.1.14 </td>
- <td width="25" rowspan="2"><img src="images/up.png" width="20" height="40"></td>
+ <td width="25" rowspan="2"><img src="images/up.png" alt="-" width="20" height="40"/></td>
</tr>
<tr>
<td> 4.1.15 </td>
- <td rowspan="2"><img src="images/up.png" width="20" height="40"></td>
+ <td rowspan="2"><img src="images/up.png" alt="-" width="20" height="40"/></td>
<td> 5.0.9 </td>
<td bgcolor="#333333"> </td>
<td> 5.1.12 </td>
</tr>
<tr>
- <td height="30" rowspan="5"><img src="images/up-down.png" width="20" height="100"></td>
+ <td height="30" rowspan="5"><img src="images/up-down.png" alt="-" width="20" height="100"/></td>
<td> 4.1.14 </td>
<td> 5.0.8 </td>
- <td rowspan="7"><img src="images/up-down.png" width="20" height="140"></td>
+ <td rowspan="7"><img src="images/up-down.png" alt="-" width="20" height="140"/></td>
<td> 5.1.11 </td>
<td width="25" rowspan="7"> </td>
</tr>
@@ -167,12 +173,12 @@
</tr>
<tr>
<td> 4.1.10 </td>
- <td rowspan="2"><img src="images/up-down.png" width="20" height="40"></td>
+ <td rowspan="2"><img src="images/up-down.png" alt="-" width="20" height="40"/></td>
<td> 5.0.4 </td>
<td> 5.1.5 </td>
</tr>
<tr>
- <td height="30" rowspan="2"><img src="images/up-down.png" width="20" height="40"></td>
+ <td height="30" rowspan="2"><img src="images/up-down.png" alt="-" width="20" height="40"/></td>
<td> 4.1.9 </td>
<td> 5.0.3 </td>
<td> 5.1.4 </td>
@@ -185,7 +191,7 @@
</tr>
</table>
<h3>KEY:</h3>
-<p><img src="images/up-down.png" width="15" height="30" align="absmiddle"> Upgrades and downgrades supported</p>
-<p><img src="images/up.png" width="15" height="30" align="absmiddle"> Upgrade only</p>
+<p><img src="images/up-down.png" alt="-" width="15" height="30" align="middle"/> Upgrades and downgrades supported</p>
+<p><img src="images/up.png" alt="-" width="15" height="30" align="middle"/> Upgrade only</p>
</body>
</html>
Modified: trunk/refman-common/images/cluster-upgrade-downgrade-table.png
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 160 bytes
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6020 - in trunk: refman-4.1 refman-4.1/images refman-5.0 refman-5.0/images refman-5.1 refman-5.1/images refman-common/... | jon | 20 Apr |
