| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | April 19 2006 2:47pm |
| Subject: | svn commit - mysqldoc@docsrva: r1863 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-common | ||
| View as plain text | |||
Author: jstephens Date: 2006-04-19 14:46:54 +0200 (Wed, 19 Apr 2006) New Revision: 1863 Log: New Cluster chapter section: Cluster Upgrades & Downgrades New subsections: Rolling Upgrades & Downgrades Upgrade/Downgrade Matrix (Fix for Documentation Bug #16150) Modified: trunk/refman-4.1/ndbcluster.xml trunk/refman-5.0/ndbcluster.xml trunk/refman-5.1/ndbcluster.xml trunk/refman-common/titles.en.ent Modified: trunk/refman-4.1/ndbcluster.xml =================================================================== --- trunk/refman-4.1/ndbcluster.xml 2006-04-18 23:05:14 UTC (rev 1862) +++ trunk/refman-4.1/ndbcluster.xml 2006-04-19 12:46:54 UTC (rev 1863) @@ -8507,6 +8507,876 @@ </section> + <section id="mysql-cluster-upgrade-downgrade"> + + <title>&title-mysql-cluster-upgrade-downgrade;</title> + + <para> + This portion of the MySQL Cluster chapter covers upgrading and + downgrading a MySQL Cluster from one MySQL release to another. It + discusses different types of Cluster upgrades and downgrades, and + provides a Cluster upgrade/downgrade compatibility matrix (see + <xref + linkend="mysql-cluster-upgrade-downgrade-compatibility"/>). + </para> + + <para> + <emphasis role="bold">Important</emphasis>: You are expected + already to be familiar with installing and configuring a MySQL + Cluster prior to attempting an upgrade or downgrade. See + <xref + linkend="mysql-cluster-configuration"/>. + </para> + + <para> + This section remains in development, and will be updated and + expanded considerably during the second quarter of 2006. + </para> + + <section id="mysql-cluster-upgrade-downgrade-rolling"> + + <title>&title-mysql-cluster-upgrade-downgrade-rolling;</title> + + <para> + This section discusses how to perform a <firstterm>rolling + upgrade</firstterm> of a MySQL Cluster installation, so called + because it involves stopping and starting (or restarting) each + node in turn, so that the cluster itself remains operational. + This type of upgrade is done where high availability of the + cluster is mandatory and no downtime of the cluster as a whole + is permissible. The information provided here also applies to + downgrades as well. + </para> + + <remark role="todo"> + [js] Possibly move this reference - and the matrix to which it + refers - to a separate Compatibility Matrix subsection of the + Cluster Upgrades section if/when it is created. For now, I'll + leave info covering all MySQL versions that support Cluster in + this matrix; eventually, we may wish to split it up. + </remark> + + <para> + There are a number of reasons why a rolling upgrade (or + downgrade) might be desired: + </para> + + <itemizedlist> + + <listitem> + <para> + <emphasis role="bold">Cluster Configuration + Change</emphasis>: To make a change in the cluster's + configuration, such as adding an SQL node or setting a + configuration parameter to a new value + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster Software + Upgrade/Downgrade</emphasis>: To upgrade the cluster to a + newer version of the MySQL Cluster software (or to downgrade + it to an older version) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Change on Node Host</emphasis>: To + make changes in the hardware or operating system on which + one or more cluster nodes are running + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster Reset</emphasis>: To reset the + cluster because it has reached an undesirable state + </para> + </listitem> + + </itemizedlist> + + <para> + The process for performing a rolling upgrade may be generalised + as follows: + </para> + + <orderedlist> + + <listitem> + <para> + Stop, reconfigure, then restart each cluster management node + (<command>ndb_mgmd</command> process) in turn + </para> + </listitem> + + <listitem> + <para> + Stop, reconfigure, then restart each cluster data node + (<command>ndbd</command> process) in turn + </para> + </listitem> + + </orderedlist> + + <para> + The specifics for implementing a particular rolling upgrade + depend upon the actual changes being made. A more detailed view + of the process is presented in the table shown here: + </para> + + <table> + + <caption> Steps for Cluster rolling upgrades — by + upgrade type </caption> + + <tbody> + <tr> + + <th colspan="8">UPGRADE TYPE:</th> + + </tr> + <tr> + + <th colspan="2">Cluster Configuration Change</th> + + <th colspan="2">Cluster Software Upgrade/Downgrade</th> + + <th colspan="2">Change on Node Host</th> + + <th colspan="2">Cluster Reset</th> + + </tr> + <tr> + + <th colspan="8">A. For each <command>ndb_mgmd</command> + process...</th> + + </tr> + <tr> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndb_mgmd</command> + </para> + </listitem> + + <listitem> + <para> + Make change in configuration file + </para> + </listitem> + + <listitem> + <para> + Start <command>ndb_mgmd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndb_mgmd</command> + </para> + </listitem> + + <listitem> + <para> + Replace <command>ndb_mgmd</command> binary with new + version + </para> + </listitem> + + <listitem> + <para> + Start <command>ndb_mgmd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndb_mgmd</command> + </para> + </listitem> + + <listitem> + <para> + Make desired changes in hardware/operating system + </para> + </listitem> + + <listitem> + <para> + Start <command>ndb_mgmd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <th colspan="2">( OR )</th> + + </tr> + <tr> + + <td> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndb_mgmd</command> + </para> + </listitem> + + <listitem> + <para> + Start <command>ndb_mgmd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td> Restart <command>ndb_mgmd</command> (optional) </td> + + </tr> + <tr> + + <th colspan="8">B. For each <command>ndbd</command> + process...</th> + + </tr> + <tr> + + <th colspan="2">( OR )</th> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndbd</command> + </para> + </listitem> + + <listitem> + <para> + Replace <command>ndbd</command> binary with new + version + </para> + </listitem> + + <listitem> + <para> + Start <command>ndbd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndbd</command> + </para> + </listitem> + + <listitem> + <para> + Make desired changes in hardware/operating system + </para> + </listitem> + + <listitem> + <para> + Start <command>ndbd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <th colspan="2">( OR )</th> + + </tr> + <tr> + + <td> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndbd</command> + </para> + </listitem> + + <listitem> + <para> + Start <command>ndbd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td> Restart <command>ndbd</command> + + </td> + + <td> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndbd</command> + </para> + </listitem> + + <listitem> + <para> + Start <command>ndbd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td> Restart <command>ndbd</command> + + </td> + + </tr> + </tbody> + + </table> + + </section> + + <section id="mysql-cluster-upgrade-downgrade-compatibility"> + + <title>&title-mysql-cluster-upgrade-downgrade-compatibility;</title> + + <para> + This section provides information regarding Cluster software and + table file compatibility between differing versions of the MySQL + Server for purposes of performing upgrades and downgrades. + </para> + + <para> + <emphasis role="bold">Important</emphasis>: Only compatibility + between MySQL versions with regard to <literal>NDB + Cluster</literal> is taken into account in this section, and + there are likely other issues to be considered. <emphasis>As + with any other MySQL software upgrade or downgrade, you are + strongly encouraged to review the relevant portions of the MySQL + Manual for the MySQL versions from which and to which you intend + to migrate, before attempting an upgrade or downgrade of the + MySQL Cluster software</emphasis>. See + <xref linkend="upgrade"/>. + </para> + + <remark role="note"> + [js] Table info extracted from the file + mysql-5.2/storage/ndb/src/common/util/version.c + </remark> + + <remark role="todo"> + [js] Update as new server versions are released + </remark> + + <para> + The following table shows Cluster upgrade and downgrade + compatibility between different versions of the MySQL Server. + </para> + + <table> + + <caption> Cluster Upgrade/Downgrade Compatibility — by + MySQL Server version </caption> + + <tbody> + <tr> + + <td colspan="2"> + + <para> + <emphasis role="bold">MySQL 4.1</emphasis> + </para> + + </td> + + <td> </td> + + <td colspan="2"> + + <para> + <emphasis role="bold">MySQL 5.0</emphasis> + </para> + + </td> + + <td> </td> + + <td colspan="2"> + + <para> + <emphasis role="bold">MySQL 5.1</emphasis> + </para> + + </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.21</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.20</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.19</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.18</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.17</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.16</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.15</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.14</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.19</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.13</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.18</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.12</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.17</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.11</td> + + <td>⇑ (see Notes)</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.16</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.10</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.15</td> + + <td>⇑ (see Notes)</td> + + <td> </td> + + <td>5.0.9</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.14</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.8</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.10</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.13</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.7</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.9</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.12</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.6</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.7</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.11</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.5</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.6</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.10</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.4</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.5</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.9</td> + + <td>⇑ / ⇓ (see Notes)</td> + + <td> </td> + + <td>5.0.3</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.4</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.8</td> + + <td>⇑</td> + + <td> </td> + + <td>5.0.2</td> + + <td>⇑</td> + + <td> </td> + + <td>5.1.3</td> + + <td>⇕</td> + + </tr> + <tr> + + <td colspan="1"> + + <para> + <emphasis>KEY</emphasis>: + </para> + + </td> + + <td colspan="7"> + + <itemizedlist> + + <listitem> + <para> + ⇕: Upwardly and downwardly compatible + </para> + </listitem> + + <listitem> + <para> + ⇑: Upwardly compatible only + </para> + </listitem> + + <listitem> + <para> + ⇓: Downwardly compatible only + </para> + </listitem> + + </itemizedlist> + + </td> + + </tr> + </tbody> + + </table> + + <para> + <emphasis role="bold">Notes</emphasis>: + </para> + + <itemizedlist> + + <listitem> + <para> + <emphasis role="bold">4.1 Series</emphasis>: + </para> + + <para> + You cannot upgrade directly from 4.1.8 to 4.1.10 (or newer); + you must first upgrade from 4.1.8 to 4.1.9, then upgrade to + 4.1.10. Similarly, you cannot downgrade directly from 4.1.10 + (or newer) to 4.1.8; you must first downgrade from 4.1.10 to + 4.1.9, then downgrade from 4.1.9 to 4.1.8. + </para> + + <para> + Cluster downgrades from 4.1.15 to 4.1.14 (or earlier + versions) are not supported. + </para> + + <para> + Cluster upgrades from MySQL Server versions previous to + 4.1.8 are not supported; when upgrading from these, you must + dump all <literal>NDB</literal> tables, install the new + version of the software, and then reload the tables from the + dump. + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">5.0 Series</emphasis>: + </para> + + <para> + MySQL 5.0.2 was the first public release in this series. + </para> + + <para> + Cluster downgrades from MySQL 5.0 to MySQL 4.1 are not + supported. + </para> + + <para> + Cluster downgrades from 5.0.12 to 5.0.11 (or earlier) are + not supported. + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">5.1 Series</emphasis>: + </para> + + <para> + MySQL 5.1.3 was the first public release in this series. + </para> + + <para> + You cannot downgrade a MySQL 5.1.6 or later Cluster using + Disk Data tables to MySQL 5.1.5 or earlier unless you + convert all such tables to in-memory Cluster tables first. + </para> + + <para> + There was no public release for MySQL 5.1.8. + </para> + </listitem> + + </itemizedlist> + + </section> + + </section> + <section id="mysql-cluster-interconnects"> <title>&title-mysql-cluster-interconnects;</title> Modified: trunk/refman-5.0/ndbcluster.xml =================================================================== --- trunk/refman-5.0/ndbcluster.xml 2006-04-18 23:05:14 UTC (rev 1862) +++ trunk/refman-5.0/ndbcluster.xml 2006-04-19 12:46:54 UTC (rev 1863) @@ -6527,6 +6527,876 @@ </section> + <section id="mysql-cluster-upgrade-downgrade"> + + <title>&title-mysql-cluster-upgrade-downgrade;</title> + + <para> + This portion of the MySQL Cluster chapter covers upgrading and + downgrading a MySQL Cluster from one MySQL release to another. It + discusses different types of Cluster upgrades and downgrades, and + provides a Cluster upgrade/downgrade compatibility matrix (see + <xref + linkend="mysql-cluster-upgrade-downgrade-compatibility"/>). + </para> + + <para> + <emphasis role="bold">Important</emphasis>: You are expected + already to be familiar with installing and configuring a MySQL + Cluster prior to attempting an upgrade or downgrade. See + <xref + linkend="mysql-cluster-configuration"/>. + </para> + + <para> + This section remains in development, and will be updated and + expanded considerably during the second quarter of 2006. + </para> + + <section id="mysql-cluster-upgrade-downgrade-rolling"> + + <title>&title-mysql-cluster-upgrade-downgrade-rolling;</title> + + <para> + This section discusses how to perform a <firstterm>rolling + upgrade</firstterm> of a MySQL Cluster installation, so called + because it involves stopping and starting (or restarting) each + node in turn, so that the cluster itself remains operational. + This type of upgrade is done where high availability of the + cluster is mandatory and no downtime of the cluster as a whole + is permissible. The information provided here also applies to + downgrades as well. + </para> + + <remark role="todo"> + [js] Possibly move this reference - and the matrix to which it + refers - to a separate Compatibility Matrix subsection of the + Cluster Upgrades section if/when it is created. For now, I'll + leave info covering all MySQL versions that support Cluster in + this matrix; eventually, we may wish to split it up. + </remark> + + <para> + There are a number of reasons why a rolling upgrade (or + downgrade) might be desired: + </para> + + <itemizedlist> + + <listitem> + <para> + <emphasis role="bold">Cluster Configuration + Change</emphasis>: To make a change in the cluster's + configuration, such as adding an SQL node or setting a + configuration parameter to a new value + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster Software + Upgrade/Downgrade</emphasis>: To upgrade the cluster to a + newer version of the MySQL Cluster software (or to downgrade + it to an older version) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Change on Node Host</emphasis>: To + make changes in the hardware or operating system on which + one or more cluster nodes are running + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster Reset</emphasis>: To reset the + cluster because it has reached an undesirable state + </para> + </listitem> + + </itemizedlist> + + <para> + The process for performing a rolling upgrade may be generalised + as follows: + </para> + + <orderedlist> + + <listitem> + <para> + Stop, reconfigure, then restart each cluster management node + (<command>ndb_mgmd</command> process) in turn + </para> + </listitem> + + <listitem> + <para> + Stop, reconfigure, then restart each cluster data node + (<command>ndbd</command> process) in turn + </para> + </listitem> + + </orderedlist> + + <para> + The specifics for implementing a particular rolling upgrade + depend upon the actual changes being made. A more detailed view + of the process is presented in the table shown here: + </para> + + <table> + + <caption> Steps for Cluster rolling upgrades — by + upgrade type </caption> + + <tbody> + <tr> + + <th colspan="8">UPGRADE TYPE:</th> + + </tr> + <tr> + + <th colspan="2">Cluster Configuration Change</th> + + <th colspan="2">Cluster Software Upgrade/Downgrade</th> + + <th colspan="2">Change on Node Host</th> + + <th colspan="2">Cluster Reset</th> + + </tr> + <tr> + + <th colspan="8">A. For each <command>ndb_mgmd</command> + process...</th> + + </tr> + <tr> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndb_mgmd</command> + </para> + </listitem> + + <listitem> + <para> + Make change in configuration file + </para> + </listitem> + + <listitem> + <para> + Start <command>ndb_mgmd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndb_mgmd</command> + </para> + </listitem> + + <listitem> + <para> + Replace <command>ndb_mgmd</command> binary with new + version + </para> + </listitem> + + <listitem> + <para> + Start <command>ndb_mgmd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndb_mgmd</command> + </para> + </listitem> + + <listitem> + <para> + Make desired changes in hardware/operating system + </para> + </listitem> + + <listitem> + <para> + Start <command>ndb_mgmd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <th colspan="2">( OR )</th> + + </tr> + <tr> + + <td> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndb_mgmd</command> + </para> + </listitem> + + <listitem> + <para> + Start <command>ndb_mgmd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td> Restart <command>ndb_mgmd</command> (optional) </td> + + </tr> + <tr> + + <th colspan="8">B. For each <command>ndbd</command> + process...</th> + + </tr> + <tr> + + <th colspan="2">( OR )</th> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndbd</command> + </para> + </listitem> + + <listitem> + <para> + Replace <command>ndbd</command> binary with new + version + </para> + </listitem> + + <listitem> + <para> + Start <command>ndbd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndbd</command> + </para> + </listitem> + + <listitem> + <para> + Make desired changes in hardware/operating system + </para> + </listitem> + + <listitem> + <para> + Start <command>ndbd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <th colspan="2">( OR )</th> + + </tr> + <tr> + + <td> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndbd</command> + </para> + </listitem> + + <listitem> + <para> + Start <command>ndbd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td> Restart <command>ndbd</command> + + </td> + + <td> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndbd</command> + </para> + </listitem> + + <listitem> + <para> + Start <command>ndbd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td> Restart <command>ndbd</command> + + </td> + + </tr> + </tbody> + + </table> + + </section> + + <section id="mysql-cluster-upgrade-downgrade-compatibility"> + + <title>&title-mysql-cluster-upgrade-downgrade-compatibility;</title> + + <para> + This section provides information regarding Cluster software and + table file compatibility between differing versions of the MySQL + Server for purposes of performing upgrades and downgrades. + </para> + + <para> + <emphasis role="bold">Important</emphasis>: Only compatibility + between MySQL versions with regard to <literal>NDB + Cluster</literal> is taken into account in this section, and + there are likely other issues to be considered. <emphasis>As + with any other MySQL software upgrade or downgrade, you are + strongly encouraged to review the relevant portions of the MySQL + Manual for the MySQL versions from which and to which you intend + to migrate, before attempting an upgrade or downgrade of the + MySQL Cluster software</emphasis>. See + <xref linkend="upgrade"/>. + </para> + + <remark role="note"> + [js] Table info extracted from the file + mysql-5.2/storage/ndb/src/common/util/version.c + </remark> + + <remark role="todo"> + [js] Update as new server versions are released + </remark> + + <para> + The following table shows Cluster upgrade and downgrade + compatibility between different versions of the MySQL Server. + </para> + + <table> + + <caption> Cluster Upgrade/Downgrade Compatibility — by + MySQL Server version </caption> + + <tbody> + <tr> + + <td colspan="2"> + + <para> + <emphasis role="bold">MySQL 4.1</emphasis> + </para> + + </td> + + <td> </td> + + <td colspan="2"> + + <para> + <emphasis role="bold">MySQL 5.0</emphasis> + </para> + + </td> + + <td> </td> + + <td colspan="2"> + + <para> + <emphasis role="bold">MySQL 5.1</emphasis> + </para> + + </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.21</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.20</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.19</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.18</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.17</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.16</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.15</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.14</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.19</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.13</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.18</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.12</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.17</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.11</td> + + <td>⇑ (see Notes)</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.16</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.10</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.15</td> + + <td>⇑ (see Notes)</td> + + <td> </td> + + <td>5.0.9</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.14</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.8</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.10</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.13</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.7</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.9</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.12</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.6</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.7</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.11</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.5</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.6</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.10</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.4</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.5</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.9</td> + + <td>⇑ / ⇓ (see Notes)</td> + + <td> </td> + + <td>5.0.3</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.4</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.8</td> + + <td>⇑</td> + + <td> </td> + + <td>5.0.2</td> + + <td>⇑</td> + + <td> </td> + + <td>5.1.3</td> + + <td>⇕</td> + + </tr> + <tr> + + <td colspan="1"> + + <para> + <emphasis>KEY</emphasis>: + </para> + + </td> + + <td colspan="7"> + + <itemizedlist> + + <listitem> + <para> + ⇕: Upwardly and downwardly compatible + </para> + </listitem> + + <listitem> + <para> + ⇑: Upwardly compatible only + </para> + </listitem> + + <listitem> + <para> + ⇓: Downwardly compatible only + </para> + </listitem> + + </itemizedlist> + + </td> + + </tr> + </tbody> + + </table> + + <para> + <emphasis role="bold">Notes</emphasis>: + </para> + + <itemizedlist> + + <listitem> + <para> + <emphasis role="bold">4.1 Series</emphasis>: + </para> + + <para> + You cannot upgrade directly from 4.1.8 to 4.1.10 (or newer); + you must first upgrade from 4.1.8 to 4.1.9, then upgrade to + 4.1.10. Similarly, you cannot downgrade directly from 4.1.10 + (or newer) to 4.1.8; you must first downgrade from 4.1.10 to + 4.1.9, then downgrade from 4.1.9 to 4.1.8. + </para> + + <para> + Cluster downgrades from 4.1.15 to 4.1.14 (or earlier + versions) are not supported. + </para> + + <para> + Cluster upgrades from MySQL Server versions previous to + 4.1.8 are not supported; when upgrading from these, you must + dump all <literal>NDB</literal> tables, install the new + version of the software, and then reload the tables from the + dump. + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">5.0 Series</emphasis>: + </para> + + <para> + MySQL 5.0.2 was the first public release in this series. + </para> + + <para> + Cluster downgrades from MySQL 5.0 to MySQL 4.1 are not + supported. + </para> + + <para> + Cluster downgrades from 5.0.12 to 5.0.11 (or earlier) are + not supported. + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">5.1 Series</emphasis>: + </para> + + <para> + MySQL 5.1.3 was the first public release in this series. + </para> + + <para> + You cannot downgrade a MySQL 5.1.6 or later Cluster using + Disk Data tables to MySQL 5.1.5 or earlier unless you + convert all such tables to in-memory Cluster tables first. + </para> + + <para> + There was no public release for MySQL 5.1.8. + </para> + </listitem> + + </itemizedlist> + + </section> + + </section> + <section id="mysql-cluster-management"> <title>&title-mysql-cluster-management;</title> Modified: trunk/refman-5.1/ndbcluster.xml =================================================================== --- trunk/refman-5.1/ndbcluster.xml 2006-04-18 23:05:14 UTC (rev 1862) +++ trunk/refman-5.1/ndbcluster.xml 2006-04-19 12:46:54 UTC (rev 1863) @@ -5512,6 +5512,876 @@ </section> + <section id="mysql-cluster-upgrade-downgrade"> + + <title>&title-mysql-cluster-upgrade-downgrade;</title> + + <para> + This portion of the MySQL Cluster chapter covers upgrading and + downgrading a MySQL Cluster from one MySQL release to another. It + discusses different types of Cluster upgrades and downgrades, and + provides a Cluster upgrade/downgrade compatibility matrix (see + <xref + linkend="mysql-cluster-upgrade-downgrade-compatibility"/>). + </para> + + <para> + <emphasis role="bold">Important</emphasis>: You are expected + already to be familiar with installing and configuring a MySQL + Cluster prior to attempting an upgrade or downgrade. See + <xref + linkend="mysql-cluster-configuration"/>. + </para> + + <para> + This section remains in development, and will be updated and + expanded considerably during the second quarter of 2006. + </para> + + <section id="mysql-cluster-upgrade-downgrade-rolling"> + + <title>&title-mysql-cluster-upgrade-downgrade-rolling;</title> + + <para> + This section discusses how to perform a <firstterm>rolling + upgrade</firstterm> of a MySQL Cluster installation, so called + because it involves stopping and starting (or restarting) each + node in turn, so that the cluster itself remains operational. + This type of upgrade is done where high availability of the + cluster is mandatory and no downtime of the cluster as a whole + is permissible. The information provided here also applies to + downgrades as well. + </para> + + <remark role="todo"> + [js] Possibly move this reference - and the matrix to which it + refers - to a separate Compatibility Matrix subsection of the + Cluster Upgrades section if/when it is created. For now, I'll + leave info covering all MySQL versions that support Cluster in + this matrix; eventually, we may wish to split it up. + </remark> + + <para> + There are a number of reasons why a rolling upgrade (or + downgrade) might be desired: + </para> + + <itemizedlist> + + <listitem> + <para> + <emphasis role="bold">Cluster Configuration + Change</emphasis>: To make a change in the cluster's + configuration, such as adding an SQL node or setting a + configuration parameter to a new value + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster Software + Upgrade/Downgrade</emphasis>: To upgrade the cluster to a + newer version of the MySQL Cluster software (or to downgrade + it to an older version) + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Change on Node Host</emphasis>: To + make changes in the hardware or operating system on which + one or more cluster nodes are running + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Cluster Reset</emphasis>: To reset the + cluster because it has reached an undesirable state + </para> + </listitem> + + </itemizedlist> + + <para> + The process for performing a rolling upgrade may be generalised + as follows: + </para> + + <orderedlist> + + <listitem> + <para> + Stop, reconfigure, then restart each cluster management node + (<command>ndb_mgmd</command> process) in turn + </para> + </listitem> + + <listitem> + <para> + Stop, reconfigure, then restart each cluster data node + (<command>ndbd</command> process) in turn + </para> + </listitem> + + </orderedlist> + + <para> + The specifics for implementing a particular rolling upgrade + depend upon the actual changes being made. A more detailed view + of the process is presented in the table shown here: + </para> + + <table> + + <caption> Steps for Cluster rolling upgrades — by + upgrade type </caption> + + <tbody> + <tr> + + <th colspan="8">UPGRADE TYPE:</th> + + </tr> + <tr> + + <th colspan="2">Cluster Configuration Change</th> + + <th colspan="2">Cluster Software Upgrade/Downgrade</th> + + <th colspan="2">Change on Node Host</th> + + <th colspan="2">Cluster Reset</th> + + </tr> + <tr> + + <th colspan="8">A. For each <command>ndb_mgmd</command> + process...</th> + + </tr> + <tr> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndb_mgmd</command> + </para> + </listitem> + + <listitem> + <para> + Make change in configuration file + </para> + </listitem> + + <listitem> + <para> + Start <command>ndb_mgmd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndb_mgmd</command> + </para> + </listitem> + + <listitem> + <para> + Replace <command>ndb_mgmd</command> binary with new + version + </para> + </listitem> + + <listitem> + <para> + Start <command>ndb_mgmd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndb_mgmd</command> + </para> + </listitem> + + <listitem> + <para> + Make desired changes in hardware/operating system + </para> + </listitem> + + <listitem> + <para> + Start <command>ndb_mgmd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <th colspan="2">( OR )</th> + + </tr> + <tr> + + <td> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndb_mgmd</command> + </para> + </listitem> + + <listitem> + <para> + Start <command>ndb_mgmd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td> Restart <command>ndb_mgmd</command> (optional) </td> + + </tr> + <tr> + + <th colspan="8">B. For each <command>ndbd</command> + process...</th> + + </tr> + <tr> + + <th colspan="2">( OR )</th> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndbd</command> + </para> + </listitem> + + <listitem> + <para> + Replace <command>ndbd</command> binary with new + version + </para> + </listitem> + + <listitem> + <para> + Start <command>ndbd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td colspan="2" rowspan="2"> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndbd</command> + </para> + </listitem> + + <listitem> + <para> + Make desired changes in hardware/operating system + </para> + </listitem> + + <listitem> + <para> + Start <command>ndbd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <th colspan="2">( OR )</th> + + </tr> + <tr> + + <td> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndbd</command> + </para> + </listitem> + + <listitem> + <para> + Start <command>ndbd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td> Restart <command>ndbd</command> + + </td> + + <td> + + <orderedlist> + + <listitem> + <para> + Stop <command>ndbd</command> + </para> + </listitem> + + <listitem> + <para> + Start <command>ndbd</command> + </para> + </listitem> + + </orderedlist> + + </td> + + <td> Restart <command>ndbd</command> + + </td> + + </tr> + </tbody> + + </table> + + </section> + + <section id="mysql-cluster-upgrade-downgrade-compatibility"> + + <title>&title-mysql-cluster-upgrade-downgrade-compatibility;</title> + + <para> + This section provides information regarding Cluster software and + table file compatibility between differing versions of the MySQL + Server for purposes of performing upgrades and downgrades. + </para> + + <para> + <emphasis role="bold">Important</emphasis>: Only compatibility + between MySQL versions with regard to <literal>NDB + Cluster</literal> is taken into account in this section, and + there are likely other issues to be considered. <emphasis>As + with any other MySQL software upgrade or downgrade, you are + strongly encouraged to review the relevant portions of the MySQL + Manual for the MySQL versions from which and to which you intend + to migrate, before attempting an upgrade or downgrade of the + MySQL Cluster software</emphasis>. See + <xref linkend="upgrade"/>. + </para> + + <remark role="note"> + [js] Table info extracted from the file + mysql-5.2/storage/ndb/src/common/util/version.c + </remark> + + <remark role="todo"> + [js] Update as new server versions are released + </remark> + + <para> + The following table shows Cluster upgrade and downgrade + compatibility between different versions of the MySQL Server. + </para> + + <table> + + <caption> Cluster Upgrade/Downgrade Compatibility — by + MySQL Server version </caption> + + <tbody> + <tr> + + <td colspan="2"> + + <para> + <emphasis role="bold">MySQL 4.1</emphasis> + </para> + + </td> + + <td> </td> + + <td colspan="2"> + + <para> + <emphasis role="bold">MySQL 5.0</emphasis> + </para> + + </td> + + <td> </td> + + <td colspan="2"> + + <para> + <emphasis role="bold">MySQL 5.1</emphasis> + </para> + + </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.21</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.20</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.19</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.18</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.17</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.16</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.15</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td colspan="3"> </td> + + <td>5.0.14</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.19</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.13</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.18</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.12</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.17</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.11</td> + + <td>⇑ (see Notes)</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.16</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.10</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.15</td> + + <td>⇑ (see Notes)</td> + + <td> </td> + + <td>5.0.9</td> + + <td>⇕</td> + + <td colspan="3"> </td> + + </tr> + <tr> + + <td>4.1.14</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.8</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.10</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.13</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.7</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.9</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.12</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.6</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.7</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.11</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.5</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.6</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.10</td> + + <td>⇕</td> + + <td> </td> + + <td>5.0.4</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.5</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.9</td> + + <td>⇑ / ⇓ (see Notes)</td> + + <td> </td> + + <td>5.0.3</td> + + <td>⇕</td> + + <td> </td> + + <td>5.1.4</td> + + <td>⇕</td> + + </tr> + <tr> + + <td>4.1.8</td> + + <td>⇑</td> + + <td> </td> + + <td>5.0.2</td> + + <td>⇑</td> + + <td> </td> + + <td>5.1.3</td> + + <td>⇕</td> + + </tr> + <tr> + + <td colspan="1"> + + <para> + <emphasis>KEY</emphasis>: + </para> + + </td> + + <td colspan="7"> + + <itemizedlist> + + <listitem> + <para> + ⇕: Upwardly and downwardly compatible + </para> + </listitem> + + <listitem> + <para> + ⇑: Upwardly compatible only + </para> + </listitem> + + <listitem> + <para> + ⇓: Downwardly compatible only + </para> + </listitem> + + </itemizedlist> + + </td> + + </tr> + </tbody> + + </table> + + <para> + <emphasis role="bold">Notes</emphasis>: + </para> + + <itemizedlist> + + <listitem> + <para> + <emphasis role="bold">4.1 Series</emphasis>: + </para> + + <para> + You cannot upgrade directly from 4.1.8 to 4.1.10 (or newer); + you must first upgrade from 4.1.8 to 4.1.9, then upgrade to + 4.1.10. Similarly, you cannot downgrade directly from 4.1.10 + (or newer) to 4.1.8; you must first downgrade from 4.1.10 to + 4.1.9, then downgrade from 4.1.9 to 4.1.8. + </para> + + <para> + Cluster downgrades from 4.1.15 to 4.1.14 (or earlier + versions) are not supported. + </para> + + <para> + Cluster upgrades from MySQL Server versions previous to + 4.1.8 are not supported; when upgrading from these, you must + dump all <literal>NDB</literal> tables, install the new + version of the software, and then reload the tables from the + dump. + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">5.0 Series</emphasis>: + </para> + + <para> + MySQL 5.0.2 was the first public release in this series. + </para> + + <para> + Cluster downgrades from MySQL 5.0 to MySQL 4.1 are not + supported. + </para> + + <para> + Cluster downgrades from 5.0.12 to 5.0.11 (or earlier) are + not supported. + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">5.1 Series</emphasis>: + </para> + + <para> + MySQL 5.1.3 was the first public release in this series. + </para> + + <para> + You cannot downgrade a MySQL 5.1.6 or later Cluster using + Disk Data tables to MySQL 5.1.5 or earlier unless you + convert all such tables to in-memory Cluster tables first. + </para> + + <para> + There was no public release for MySQL 5.1.8. + </para> + </listitem> + + </itemizedlist> + + </section> + + </section> + <section id="mysql-cluster-process-management"> <title>&title-mysql-cluster-process-management;</title> @@ -8712,7 +9582,7 @@ <literal>apply_status</literal> tables. respectively. </para> </listitem> - + <listitem> <para> Trying to set values for the @@ -11302,7 +12172,7 @@ engine support <literal>FULLTEXT</literal> indexes (these are supported by <literal>MyISAM</literal> only). However, you can index <literal>VARCHAR</literal> columns of - <literal>NDB</literal> tables. + <literal>NDB</literal> tables. </para> </listitem> @@ -11382,7 +12252,7 @@ <literal>SQL_LOG_BIN</literal>. (Bug #16680) </para> </listitem> - + <listitem> <para> The <literal>auto_increment_increment</literal> and Modified: trunk/refman-common/titles.en.ent =================================================================== --- trunk/refman-common/titles.en.ent 2006-04-18 23:05:14 UTC (rev 1862) +++ trunk/refman-common/titles.en.ent 2006-04-19 12:46:54 UTC (rev 1863) @@ -933,6 +933,9 @@ <!ENTITY title-mysql-cluster-single-user-mode "Single-User Mode"> <!ENTITY title-mysql-cluster-startup-phases "MySQL Cluster Startup Phases"> <!ENTITY title-mysql-cluster-tcp-definition "MySQL Cluster TCP/IP Connections"> +<!ENTITY title-mysql-cluster-upgrade-downgrade "Upgrading and Downgrading MySQL Cluster"> +<!ENTITY title-mysql-cluster-upgrade-downgrade-rolling "Performing a Rolling Upgrade or Downgrade"> +<!ENTITY title-mysql-cluster-upgrade-downgrade-compatibility "Cluster Upgrade and Downgrade Compatibility"> <!ENTITY title-mysql-commands "<command>mysql</command> Commands"> <!ENTITY title-mysql-commit "<literal>mysql_commit()</literal>"> <!ENTITY title-mysql-config-for-manpage "get compile options for compiling clients">
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r1863 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-common | jon | 19 Apr |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 1.192 sec. using MySQL 5.1.14-beta-log