| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | February 27 2007 2:18pm |
| Subject: | svn commit - mysqldoc@docsrva: r5081 - branches/telcos/refman-5.1 | ||
| View as plain text | |||
Author: jstephens Date: 2007-02-27 14:18:44 +0100 (Tue, 27 Feb 2007) New Revision: 5081 Log: Reformat. Modified: branches/telcos/refman-5.1/installing.xml branches/telcos/refman-5.1/mysql-cluster.xml branches/telcos/refman-5.1/news-5.1.xml Modified: branches/telcos/refman-5.1/installing.xml =================================================================== --- branches/telcos/refman-5.1/installing.xml 2007-02-27 13:15:28 UTC (rev 5080) +++ branches/telcos/refman-5.1/installing.xml 2007-02-27 13:18:44 UTC (rev 5081) Changed blocks: 8, Lines Added: 29, Lines Deleted: 31; 5335 bytes @@ -46,24 +46,23 @@ that not all platforms are equally suitable for running MySQL ¤t-series;, and that MySQL ¤t-series; — like the standard version of MySQL Cluster — does not run on - Microsoft Windows. + Microsoft Windows. </para> - + <para> In general, MySQL ¤t-series; should compile and run on any platform that is supported by MySQL Cluster. The official list - of platforms supported by MySQL Cluster is maintained on the - <ulink url="http://www.mysql.com/support/supportedplatforms/cluster.html">Supported + of platforms supported by MySQL Cluster is maintained on the + <ulink url="http://www.mysql.com/support/supportedplatforms/cluster.html">Supported Platforms: MySQL Cluster</ulink> page on MySQL AB's Support website. </para> - </listitem> <listitem> <para> <emphasis role="bold">Download the MySQL ¤t-series; source - code distribution</emphasis>. For instructions, see + code distribution</emphasis>. For instructions, see <xref linkend="general-installation-issues"/>. </para> </listitem> @@ -86,14 +85,14 @@ <para> <emphasis role="bold">Perform any necessary post-installation setup</emphasis>. For post-installation issues relating to the - MySQL Server (SQL node), read + MySQL Server (SQL node), read <xref linkend="post-installation"/>, this section contains important information about making sure the MySQL server is working properly. It also describes how to secure the initial MySQL user accounts, <emphasis>which have no passwords</emphasis> until you assign passwords. For post-installation issues relating to specifically to MySQL - Cluster data nodes and management nodes, see + Cluster data nodes and management nodes, see <xref linkend="mysql-cluster-configuration"/>. </para> </listitem> @@ -117,7 +116,7 @@ release can be downloaded from MySQL's FTP service. The precise location for the source download for each individual MySQL ¤t-series; release can be found in the changelog for that - release (see <xref linkend="news-5-1-x"/>). + release (see <xref linkend="news-5-1-x"/>). </para> <para> @@ -129,41 +128,40 @@ </para> </section> - + <section id="installation-layouts"> - + <title>Installation Layout</title> - + <indexterm> <primary>installation layout</primary> </indexterm> - + <indexterm> <primary>layout of installation</primary> </indexterm> - + <indexterm> <primary>directory structure</primary> <secondary>default</secondary> </indexterm> - + <indexterm> <primary>default installation location</primary> </indexterm> - + <para> This section describes the default layout of the directories created by installing the MySQL ¤t-series; source distributions provided by MySQL AB. </para> - + <para> - A source distribution is installed after you configure and - compile it. By default, the installation step installs files - under <filename>/usr/local</filename>, in the following - subdirectories: + A source distribution is installed after you configure and compile + it. By default, the installation step installs files under + <filename>/usr/local</filename>, in the following subdirectories: </para> - + <informaltable> <tgroup cols="2"> <colspec colwidth="35*"/> @@ -212,14 +210,14 @@ </tbody> </tgroup> </informaltable> - + <para> - You can create your own binary installation from a compiled - source distribution by executing the - <filename>scripts/make_binary_distribution</filename> script - from the top directory of the source distribution. + You can create your own binary installation from a compiled source + distribution by executing the + <filename>scripts/make_binary_distribution</filename> script from + the top directory of the source distribution. </para> - + </section> <section id="installing-source"> @@ -239,7 +237,7 @@ <indexterm> <primary>installation overview</primary> </indexterm> - + <para> Before you proceed with an installation from source, first check whether our binary is available for your platform and whether it @@ -5149,7 +5147,7 @@ well, such as the PHP <literal>mysql</literal> extension and the Python <literal>MySQLdb</literal> module. </para> - + <para> Additional information regarding upgrade and downgrade issues specific to MySQL Cluster and MySQL ¤t-series; can be found @@ -6049,7 +6047,7 @@ </listitem> </orderedlist> - + <para> Additional information regarding upgrade and downgrade issues specific to MySQL Cluster and MySQL ¤t-series; can be found Modified: branches/telcos/refman-5.1/mysql-cluster.xml =================================================================== --- branches/telcos/refman-5.1/mysql-cluster.xml 2007-02-27 13:15:28 UTC (rev 5080) +++ branches/telcos/refman-5.1/mysql-cluster.xml 2007-02-27 13:18:44 UTC (rev 5081) Changed blocks: 17, Lines Added: 36, Lines Deleted: 36; 9037 bytes @@ -59,7 +59,7 @@ number of platforms, including Linux, Solaris, Mac OS X, BSD, HP-UX, and many other Unix-style operating systems on a variety of hardware. For exact levels of support available for on specific - combinations of operating system versions, operating system + combinations of operating system versions, operating system distributions, and hardware platforms, please refer to the <ulink url="http://www.mysql.com/support/supportedplatforms/cluster.html">Cluster Supported Platforms list</ulink> maintained by the MySQL Support @@ -77,7 +77,7 @@ This chapter represents a work in progress, and its contents are subject to revision as MySQL ¤t-series; continues to evolve. Additional information can be found on the MySQL AB web site at - <ulink url="http://www.mysql.com/products/database/clustercge/"/>. + <ulink url="http://www.mysql.com/products/database/clustercge/"/>. </para> <indexterm> @@ -312,8 +312,8 @@ <emphasis role="bold">Note</emphasis>: In many contexts, the term <quote>node</quote> is used to indicate a computer, but when discussing MySQL Cluster it means a <emphasis>process</emphasis>. - It is possible to run any number of nodes on a single computer, for - which we use the term <firstterm>cluster host</firstterm>. + It is possible to run any number of nodes on a single computer, + for which we use the term <firstterm>cluster host</firstterm>. </para> <para> @@ -985,7 +985,7 @@ <secondary>obtaining</secondary> </indexterm> - <para> + <para> Once you have compiled the binaries (see <xref linkend="installing-source-tree"/>), you must install the appropriate executables on each cluster host. Each MySQL Cluster @@ -998,14 +998,14 @@ section covers the steps necessary to install the correct binaries for each type of Cluster node. </para> - + <para> We assume that the MySQL server has been installed to <filename>/usr/local/mysql</filename> (if you compiled MySQL using one of the supplied build scripts and did not change it in that regard, this is the location in which <command>make - install</command> places it); if you installed it - elsewhere, adjust the following instructions accordingly. + install</command> places it); if you installed it elsewhere, + adjust the following instructions accordingly. </para> <para> @@ -1052,7 +1052,7 @@ <command>adduser</command> and <command>addgroup</command>. </para> </listitem> - + <listitem> <para> Change location to the directory @@ -1085,12 +1085,12 @@ data node, we will use <filename>/usr/local/mysql/cluster</filename>: </para> - + <programlisting> shell> <userinput>cd ..</userinput> shell > <userinput>mkdir cluster</userinput> </programlisting> - + <para> We will use this piece of information when we configure the management node. (See @@ -1133,7 +1133,7 @@ Remember that the preceding steps must be performed separately on each machine where a data node or SQL node is to reside. </para> - + <para> <emphasis role="bold">Management Node Installation</emphasis> </para> @@ -1144,7 +1144,7 @@ binaries for the management server (<command>ndb_mgmd</command>) and client (<command>ndb_mgm</command>) are required. These can be found, respectively, in the <filename>libexec</filename> and - <filename>bin</filename> directories of the MySQL installation. + <filename>bin</filename> directories of the MySQL installation. </para> <para> @@ -1166,7 +1166,7 @@ represented in the following example as <literal>mgm-host</literal>) as the ones in which they are placed by <command>make install</command> on the machine - where you compiled MySQL: + where you compiled MySQL: </para> <programlisting> @@ -1174,17 +1174,17 @@ shell> <userinput>rsync libexec/ndb_mgmd root@mgm-host:/usr/local/mysql/libexec/ndb_mgmd</userinput> shell> <userinput>rsync bin/ndb_mgm root@mgm-host:/usr/local/mysql/bin/ndb_mgm</userinput> </programlisting> - + <para> <command>ndb_mgmd</command> and <command>ndb_mgm</command> can actually be located nearly anywhere on the management - node host's filesystem. + node host's filesystem. </para> <para> No other executables or library files are required on the management host, as long as you did a static build of MySQL - (recommended). + (recommended). </para> </listitem> @@ -1193,7 +1193,7 @@ Log in as system <literal>root</literal> on the management node host, then change location to the directories into which you copied the files, and then make both of them - executable: + executable: </para> <programlisting> @@ -1412,7 +1412,7 @@ <para> <emphasis role="bold">Note</emphasis>: The default port for Cluster management nodes is 1186; the default port for data - nodes is 2202. + nodes is 2202. </para> </section> @@ -1777,7 +1777,7 @@ when accessing one another. Setting or changing MySQL user accounts (including the <literal>root</literal> account) effects only applications that access the SQL node, not interaction - between nodes. + between nodes. </para> <para> @@ -2067,40 +2067,40 @@ <command>configure</command>. You can also use the <command>BUILD/compile-pentium-max</command> build script; however, you will very likely wish to modify it to suit your - local conditions. + local conditions. </para> - + <warning> <para> <command>BUILD/compile-pentium-max</command> by default builds the MySQL Server with support for the - <literal>InnoDB</literal> storage engine. <emphasis>You - must not deploy or make use of MySQL ¤t-series; - employing the <literal>InnoDB</literal> storage engine without - prior written permission to do so from MySQL AB</emphasis>. + <literal>InnoDB</literal> storage engine. <emphasis>You must + not deploy or make use of MySQL ¤t-series; employing the + <literal>InnoDB</literal> storage engine without prior written + permission to do so from MySQL AB</emphasis>. </para> - - <para> + + <para> If you wish to use <literal>InnoDB</literal> technology in - conjunction with your use of MySQL ¤t-series; and do - not already have authorization to do so as part of your MySQL + conjunction with your use of MySQL ¤t-series; and do not + already have authorization to do so as part of your MySQL Server license, contact your MySQL AB salesperson or other authorized MySQL AB representative for assistance in upgrading - your MySQL Server license. + your MySQL Server license. </para> </warning> - + <para> <command>BUILD/compile-pentium-max</command> also includes OpenSSL, so you must either have or obtain OpenSSL to build successfully, or else modify <command>compile-pentium-max</command> to exclude this - requirement. Of course, you can also just follow the standard + requirement. Of course, you can also just follow the standard instructions for compiling your own binaries, and then perform the usual tests and installation procedure. See <xref linkend="installing-source-tree"/>. </para> - + <para> You should also note that <command>compile-pentium-max</command> installs MySQL to the directory @@ -3204,7 +3204,7 @@ <literal>ArbitrationRank</literal> to 1 (the default value) and that of all SQL nodes to 0. </para> - + <para> Beginning with MySQL 5.1.15/NDB-6.1.3, it is possible to disable arbitration by setting @@ -14468,7 +14468,7 @@ <literal>NDB</literal>-specific indexes, internal triggers, and Cluster Disk Data objects as well. </para> - + <para> Beginning with MySQL 5.1.15/NDB-6.1.13, this utility also provides information about table events. Modified: branches/telcos/refman-5.1/news-5.1.xml =================================================================== --- branches/telcos/refman-5.1/news-5.1.xml 2007-02-27 13:15:28 UTC (rev 5080) +++ branches/telcos/refman-5.1/news-5.1.xml 2007-02-27 13:18:44 UTC (rev 5081) Changed blocks: 18, Lines Added: 79, Lines Deleted: 57; 11058 bytes @@ -35,17 +35,17 @@ <filename>TEMPLATE.news.xml</filename> template in the <filename>refman-common</filename> directory. </remark> - + <section id="news-5-1-15-ndb-6-1-3"> - + <title>Changes in release MySQL 5.1.15/NDB-6.1.3-beta (25 February 2007)</title> - + <para role="release-level"> This is a new Beta development release, fixing recently discovered bugs and incorporating improvements made since the previous ¤t-series; release. </para> - + <para> Like all releases for MySQL ¤t-series;, this is a source-only release which you must compile and install using the @@ -55,9 +55,9 @@ <ulink url="ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.15-ndb-6.1.3"/>. The file <filename>mysqlcom-5.1.15-ndb-6.1.3-telco.tar.gz</filename> in - this directory contains the complete source archive. + this directory contains the complete source archive. </para> - + <para role="release-non-production"> <emphasis role="bold">NOTE</emphasis>: Although MySQL has worked very hard to ensure a high level of quality, protect your data by @@ -65,27 +65,29 @@ refer to our bug database at <ulink url="http://bugs.mysql.com/"/> for more details about the individual bugs fixed in this version. </para> - + <para> - This is the fourth MySQL ¤t-series; Beta release. - It incorporates all bugfixes and feature changes made in MySQL + This is the fourth MySQL ¤t-series; Beta release. It + incorporates all bugfixes and feature changes made in MySQL 5.1.14/NDB-6.1.0, MySQL 5.1.15/NDB-6.1.1, and MySQL 5.1.15/NDB-6.1.2. This version also incorporates all bugfixes and feature changes which were added in the mainline 5.1.15 release; - information about these can be found in + information about these can be found in <xref linkend="news-5-1-15"/>. </para> - + <important> <formalpara> <title>Upgrading to MySQL 5.1.15/NDB-6.1.3 from a previous release</title> - + + + <para> This release is not binary compatible with any previous releases. This means that: - + <itemizedlist> - + <listitem> <para> You cannot perform an online upgrade to this release @@ -94,12 +96,12 @@ from one of these versions, you must shut down the cluster, replace all binaries, then restart the cluster. </para> - + <para> However, you <emphasis>can</emphasis> perform an online upgrade of a Cluster running MySQL 5.1.15/NDB-6.1.2 to MySQL 5.1.15/NDB-6.1.13, using the rolling upgrade - procedure described in + procedure described in <xref linkend="mysql-cluster-rolling-restart"/>. You should replace all binaries for all data nodes, management nodes, and SQL nodes as part of this process. @@ -107,7 +109,7 @@ each data with the <option>--initial</option> option. </para> </listitem> - + <listitem> <para> You must recompile any MySQL Cluster API applications @@ -115,26 +117,26 @@ includes all NDB API and MGM API applications. </para> </listitem> - + </itemizedlist> </para> </formalpara> </important> - - + <para> Functionality added or changed: </para> - + <itemizedlist> + <listitem> <para> The <command>ndb_show_tables</command> utility now displays - information about table events. (See + information about table events. (See <xref linkend="mysql-cluster-utilities-ndb-show-tables"/>.) </para> </listitem> - + <listitem> <para> It is now possible to disable arbitration by setting @@ -142,71 +144,88 @@ nodes. </para> </listitem> + </itemizedlist> - - + <para> This release fixes the folowing bugs: </para> - + <itemizedlist> + <listitem> <para> No appropriate error message was provided when there was insufficient REDO log file space for the cluster to start. - (Bug #25801) + (Bug #25801) </para> </listitem> - + <listitem> <para> <emphasis role="bold">Disk Data</emphasis>: Use of a tablespace whose <literal>INITIAL_SIZE</literal> was greater - than 1 GB could cause the cluster to crash. (Bug #26487) + than 1 GB could cause the cluster to crash. (Bug #26487) </para> </listitem> - + <listitem> <para> A memory allocation failure in the cluster Subscription Manager could cause the cluster to crash. (Bug #25239) </para> </listitem> - + <listitem> <para> - The <errorname>InvalidUndoBufferSize</errorname> error used - the same error code (<errorcode>763</errorcode>) as the - <errorname>IncompatibleVersions</errorname> error. - <errorname>InvalidUndoBufferSize</errorname> now uses its own - error code (<errorcode>779</errorcode>). (Bug #26490) + The + + <errorname>InvalidUndoBufferSize</errorname> + + error used the same error code ( + + <errorcode>763</errorcode> + + ) as the + + <errorname>IncompatibleVersions</errorname> + + error. + + <errorname>InvalidUndoBufferSize</errorname> + + now uses its own error code ( + + <errorcode>779</errorcode> + + ). (Bug #26490) </para> </listitem> - + <listitem> <para> <emphasis role="bold">Disk Data</emphasis>: A memory overflow could occur with tables having a large amount of data stored on disk, or with queries using a very high degree of - parallelism on Disk Data tables. (Bug #26514) + parallelism on Disk Data tables. (Bug #26514) </para> </listitem> - + <listitem> <para> The failure of a data node when restarting it with <option>--initial</option> could lead to failures of - subsequent data node restarts. (Bug #26481) + subsequent data node restarts. (Bug #26481) </para> </listitem> - + <listitem> <para> Takeover for local checkpointing due to multiple failures of master nodes was sometimes handled incorrectly. (Bug #26457) </para> </listitem> - + <listitem> <para> The <literal>LockPagesInMemory</literal> parameter was not @@ -216,7 +235,7 @@ failure due to missed heartbeats. (Bug #26454) </para> </listitem> - + <listitem> <para> Under some circumstances, following the restart of a @@ -225,15 +244,15 @@ events to the management node. (Bug #26293) </para> </listitem> - + <listitem> <para> An error was produced when <literal>SHOW TABLE STATUS</literal> was used on an <literal>NDB</literal> table that had no <literal>AUTO_INCREMENT</literal> column. (Bug - #21033) + #21033) </para> - + <note> <para> This improves on and supersedes an earlier fix that was made @@ -241,9 +260,9 @@ </para> </note> </listitem> - + </itemizedlist> - + </section> <section id="news-5-1-15-ndb-6-1-2"> @@ -254,7 +273,7 @@ This is a new Beta development release, fixing a recently discovered bug. </para> - + <para> Like all releases for MySQL ¤t-series;, this is a source-only release which you must compile and install using the @@ -264,9 +283,9 @@ <ulink url="ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.15-ndb-6.1.2"/>. The file <filename>mysqlcom-5.1.15-ndb-6.1.2-telco.tar.gz</filename> in - this directory contains the complete source archive. + this directory contains the complete source archive. </para> - + <para> Like all releases for MySQL ¤t-series;, this is a source-only release which you must compile and install using the @@ -276,7 +295,7 @@ <ulink url="ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.15-ndb-6.1.2"/>. The file <filename>mysqlcom-5.1.15-ndb-6.1.2-telco.tar.gz</filename> in - this directory contains the complete source archive. + this directory contains the complete source archive. </para> <para role="release-non-production"> @@ -359,7 +378,7 @@ This is a new Beta development release, fixing recently discovered bugs. </para> - + <para> Like all releases for MySQL ¤t-series;, this is a source-only release which you must compile and install using the @@ -371,7 +390,6 @@ <filename>mysqlcom-5.1.15-ndb-6.1.1-telco.tar.gz</filename> in this directory contains the complete source archive. </para> - <para role="release-non-production"> <emphasis role="bold">NOTE</emphasis>: Although MySQL has worked @@ -1853,7 +1871,7 @@ This is a new Beta development release, fixing recently discovered bugs. </para> - + <para> Like all releases for MySQL ¤t-series;, this is a source-only release which you must compile and install using the @@ -1862,7 +1880,9 @@ source code archive for this release from the MySQL FTP site at <ulink url="ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.14-ndb-6.1.0"/>. There are two version of the source archive in this directory: + <itemizedlist> + <listitem> <para> <filename>mysql-5.1.14-ndb-6.1.0-telco.tar.gz</filename>: @@ -1872,15 +1892,17 @@ setting. </para> </listitem> + <listitem> <para> <filename>mysqlcom-5.1.14-ndb-6.1.0-telco.tar.gz</filename>: - This is the commercial version. Customers who are using MySQL - ¤t-series; under a commercial licence + This is the commercial version. Customers who are using + MySQL ¤t-series; under a commercial licence <emphasis>must</emphasis> use this version in any setting covered under their licence agreement with MySQL AB. </para> </listitem> + </itemizedlist> </para>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r5081 - branches/telcos/refman-5.1 | jon | 27 Feb |
© 1995-2008 MySQL AB. All rights reserved.
Page generated in 0.634 sec. using MySQL 5.1.14-beta-log