Author: jstephens
Date: 2008-02-10 14:29:30 +0100 (Sun, 10 Feb 2008)
New Revision: 9762
Log:
Removed references to MySQL-Max from cluster installation section
(user comment)
Modified:
trunk/refman-5.0/mysql-cluster-multi-computer.xml
trunk/refman-5.1/mysql-cluster-multi-computer.xml
trunk/refman-6.0/mysql-cluster-multi-computer.xml
Modified: trunk/refman-5.0/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster-multi-computer.xml 2008-02-09 23:37:45 UTC (rev 9761)
+++ trunk/refman-5.0/mysql-cluster-multi-computer.xml 2008-02-10 13:29:30 UTC (rev 9762)
Changed blocks: 13, Lines Added: 35, Lines Deleted: 37; 8409 bytes
@@ -398,12 +398,13 @@
</indexterm>
<para>
- Each MySQL Cluster host computer running data or SQL nodes must
- have installed on it a MySQL-max binary. For management nodes, it
- is not necessary to install the MySQL server binary, but you do
- have to install the management server daemon
- (<command>ndb_mgmd</command>). It is also a good idea to install
- the management client (<command>ndb_mgm</command>) on the
+ Each MySQL Cluster host computer running SQL nodes must have
+ installed on it a MySQL binary. For management nodes and data
+ nodes, it is not necessary to install the MySQL server binary, but
+ management nodes require the management server daemon
+ (<command>ndb_mgmd</command>) and data nodes require the data node
+ daemon (<command>ndbd</command>). It is also a good idea to
+ install the management client (<command>ndb_mgm</command>) on the
management server host. This section covers the steps necessary to
install the correct binaries for each type of Cluster node.
</para>
@@ -415,7 +416,7 @@
after building MySQL from source.) For setting up a cluster using
MySQL's binaries, the first step in the installation process for
each cluster host is to download the file
- <filename>mysql-max-¤t-version;-pc-linux-gnu-i686.tar.gz</filename>
+ <filename>mysql-¤t-version;-pc-linux-gnu-i686.tar.gz</filename>
from the <ulink url="&base-url-downloads;">MySQL downloads
area</ulink>. We assume that you have placed it in each machine's
<filename>/var/tmp</filename> directory. (If you do require a
@@ -424,7 +425,7 @@
<para>
RPMs are also available for both 32-bit and 64-bit Linux
- platforms. For a MySQL Cluster, four RPMs are required:
+ platforms. For a MySQL Cluster, three RPMs are required:
</para>
<itemizedlist>
@@ -432,22 +433,13 @@
<listitem>
<para>
The <emphasis role="bold">Server</emphasis> RPM (for example,
- <filename>MySQL-server-¤t-version;-0.glibc23.i386.rpm</filename>),
+ <filename>MySQL-Server-¤t-version;-0.glibc23.i386.rpm</filename>),
which supplies the core files needed to run a MySQL Server.
</para>
</listitem>
<listitem>
<para>
- The <emphasis role="bold">Server/Max</emphasis> RPM (for
- example,
- <filename>MySQL-Max-¤t-version;-0.glibc23.i386.rpm</filename>),
- which provides a MySQL Server binary with clustering support.
- </para>
- </listitem>
-
- <listitem>
- <para>
The <emphasis role="bold">NDB Cluster - Storage
engine</emphasis> RPM (for example,
<filename>MySQL-ndb-storage-¤t-version;-0.glibc23.i386.rpm</filename>),
@@ -558,7 +550,7 @@
<para>
Change location to the directory containing the downloaded
file, unpack the archive, and create a symlink to the
- <filename>mysql-max</filename> directory named
+ <filename>mysql</filename> directory named
<filename>mysql</filename>. Note that the actual file and
directory names will vary according to the MySQL version
number.
@@ -566,8 +558,8 @@
<programlisting>
shell> <userinput>cd /var/tmp</userinput>
-shell> <userinput>tar -C /usr/local -xzvf mysql-max-¤t-version;-pc-linux-gnu-i686.tar.gz</userinput>
-shell> <userinput>ln -s /usr/local/mysql-max-¤t-version;-pc-linux-gnu-i686 /usr/local/mysql</userinput>
+shell> <userinput>tar -C /usr/local -xzvf mysql-¤t-version;-pc-linux-gnu-i686.tar.gz</userinput>
+shell> <userinput>ln -s /usr/local/mysql-¤t-version;-pc-linux-gnu-i686 /usr/local/mysql</userinput>
</programlisting>
</listitem>
@@ -599,7 +591,7 @@
<para>
Note that the data directory on each machine hosting a
data node is <filename>/usr/local/mysql/data</filename>.
- We will use this piece of information when we configure
+ This piece of information is essential when configuring
the management node. (See
<xref linkend="mysql-cluster-multi-config"/>.)
</para>
@@ -637,7 +629,7 @@
</orderedlist>
Remember that the preceding steps must be performed separately
- on each machine where a data node or SQL node is to reside.
+ on each machine where an SQL node is to reside.
</para>
</formalpara>
@@ -648,16 +640,17 @@
<para>
On each machine to be used for hosting a cluster SQL node,
- install the <emphasis role="bold">MySQL Max</emphasis> RPM by
+ install the <emphasis role="bold">MySQL Server</emphasis> RPM by
executing the following command as the system root user,
replacing the name shown for the RPM as necessary to match the
name of the RPM downloaded from the MySQL AB web site:
<programlisting>
shell> <userinput>rpm -Uhv MySQL-server-¤t-version;-0.glibc23.i386.rpm</userinput>
-shell> <userinput>rpm -Uhv MySQL-Max-¤t-version;-0.glibc23.i386.rpm</userinput>
- This installs the MySQL Max server binary
- (<command>mysqld-max</command>) in the
+</programlisting>
+
+ This installs the MySQL server binary
+ (<command>mysqld</command>) in the
<filename>/usr/sbin</filename> directory, as well as all needed
MySQL Server support files. It also installs the
<command>mysql.server</command> and
@@ -667,7 +660,6 @@
should take care of general configuration issues (such as
creating the <literal>mysql</literal> user and group, if needed)
automatically.
-</programlisting>
</para>
</formalpara>
@@ -677,7 +669,8 @@
<title>SQL node installation — building from source</title>
<para>
- If you compile MySQL with clustering support (using the
+ If you compile MySQL with clustering support (for example, by
+ using the
<command>BUILD/compile-<replaceable>platform_name</replaceable>-max</command>
script appropriate to your platform), and perform the default
installation (using <command>make install</command> as the root
@@ -733,9 +726,12 @@
when doing a source build, this file is placed in the directory
<filename>/usr/local/mysql/libexec</filename>. For installing on
multiple data node hosts, only <command>ndbd</command> need be
- copied to the other host machine or machines.
- <command>ndbd</command> need not be in any particular location
- on the host's filesystem, as long as the location is known.
+ copied to the other host machine or machines. (This assumes that
+ all data node hosts use the same architecture and operating
+ system; otherwise you may need to compile separately for each
+ different platform.) <command>ndbd</command> need not be in any
+ particular location on the host's filesystem, as long as the
+ location is known.
</para>
</formalpara>
@@ -745,11 +741,13 @@
<title>Management node installation — <filename>.tar.gz</filename> binary</title>
<para>
- Installation for the management (MGM) node does not require
- installation of the <command>mysqld</command> binary. Only the
- binaries for the MGM server and client are required, which can
- be found in the downloaded archive. Again, we assume that you
- have placed this file in <filename>/var/tmp</filename>.
+ Installation of the management node does not require the
+ <command>mysqld</command> binary. Only the binary for the
+ management server is required, which can be found in the
+ downloaded archive. You most likely want to install the
+ management client as well; this can also be found in the
+ <filename>.tar.gz</filename> archive. Again, we assume that you
+ have placed this archive in <filename>/var/tmp</filename>.
</para>
</formalpara>
Modified: trunk/refman-5.1/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-multi-computer.xml 2008-02-09 23:37:45 UTC (rev 9761)
+++ trunk/refman-5.1/mysql-cluster-multi-computer.xml 2008-02-10 13:29:30 UTC (rev 9762)
Changed blocks: 14, Lines Added: 41, Lines Deleted: 67; 9879 bytes
@@ -398,12 +398,13 @@
</indexterm>
<para>
- Each MySQL Cluster host computer running data or SQL nodes must
- have installed on it a MySQL-max binary. For management nodes, it
- is not necessary to install the MySQL server binary, but you do
- have to install the management server daemon
- (<command>ndb_mgmd</command>). It is also a good idea to install
- the management client (<command>ndb_mgm</command>) on the
+ Each MySQL Cluster host computer running SQL nodes must have
+ installed on it a MySQL binary. For management nodes and data
+ nodes, it is not necessary to install the MySQL server binary, but
+ management nodes require the management server daemon
+ (<command>ndb_mgmd</command>) and data nodes require the data node
+ daemon (<command>ndbd</command>). It is also a good idea to
+ install the management client (<command>ndb_mgm</command>) on the
management server host. This section covers the steps necessary to
install the correct binaries for each type of Cluster node.
</para>
@@ -415,25 +416,16 @@
after building MySQL from source.) For setting up a cluster using
MySQL's binaries, the first step in the installation process for
each cluster host is to download the file
- <filename>mysql-max-¤t-version;-pc-linux-gnu-i686.tar.gz</filename>
+ <filename>mysql-¤t-version;-pc-linux-gnu-i686.tar.gz</filename>
from the <ulink url="&base-url-downloads;">MySQL downloads
area</ulink>. We assume that you have placed it in each machine's
<filename>/var/tmp</filename> directory. (If you do require a
custom binary, see <xref linkend="installing-source-tree"/>.)
</para>
-
- &mccge-warning-begin;
-
- <para>
- For &mccge-series;, binaries are not provided, and you must
- compile MySQL from source.
- </para>
-
- &mccge-warning-unsupported-begin;
- <para>
+ <para>
RPMs are also available for both 32-bit and 64-bit Linux
- platforms. For a MySQL Cluster, four RPMs are required:
+ platforms. For a MySQL Cluster, three RPMs are required:
</para>
<itemizedlist>
@@ -441,22 +433,13 @@
<listitem>
<para>
The <emphasis role="bold">Server</emphasis> RPM (for example,
- <filename>MySQL-server-¤t-version;-0.glibc23.i386.rpm</filename>),
+ <filename>MySQL-Server-¤t-version;-0.glibc23.i386.rpm</filename>),
which supplies the core files needed to run a MySQL Server.
</para>
</listitem>
<listitem>
<para>
- The <emphasis role="bold">Server/Max</emphasis> RPM (for
- example,
- <filename>MySQL-Max-¤t-version;-0.glibc23.i386.rpm</filename>),
- which provides a MySQL Server binary with clustering support.
- </para>
- </listitem>
-
- <listitem>
- <para>
The <emphasis role="bold">NDB Cluster - Storage
engine</emphasis> RPM (for example,
<filename>MySQL-ndb-storage-¤t-version;-0.glibc23.i386.rpm</filename>),
@@ -514,26 +497,17 @@
After installing from RPM, you still need to configure the cluster
as discussed in <xref linkend="mysql-cluster-multi-config"/>.
</para>
-
- &mccge-warning-end-cluster;
-
-
-
- <note>
+ <note>
<para>
After completing the installation, do not yet start any of the
binaries. We show you how to do so following the configuration
of all nodes.
</para>
</note>
-
- &mccge-warning-unsupported-begin;
+ <formalpara>
-
- <formalpara>
-
<title>Data and SQL Node Installation — <filename>.tar.gz</filename>
Binary</title>
@@ -576,7 +550,7 @@
<para>
Change location to the directory containing the downloaded
file, unpack the archive, and create a symlink to the
- <filename>mysql-max</filename> directory named
+ <filename>mysql</filename> directory named
<filename>mysql</filename>. Note that the actual file and
directory names will vary according to the MySQL version
number.
@@ -584,8 +558,8 @@
<programlisting>
shell> <userinput>cd /var/tmp</userinput>
-shell> <userinput>tar -C /usr/local -xzvf mysql-max-¤t-version;-pc-linux-gnu-i686.tar.gz</userinput>
-shell> <userinput>ln -s /usr/local/mysql-max-¤t-version;-pc-linux-gnu-i686 /usr/local/mysql</userinput>
+shell> <userinput>tar -C /usr/local -xzvf mysql-¤t-version;-pc-linux-gnu-i686.tar.gz</userinput>
+shell> <userinput>ln -s /usr/local/mysql-¤t-version;-pc-linux-gnu-i686 /usr/local/mysql</userinput>
</programlisting>
</listitem>
@@ -617,7 +591,7 @@
<para>
Note that the data directory on each machine hosting a
data node is <filename>/usr/local/mysql/data</filename>.
- We will use this piece of information when we configure
+ This piece of information is essential when configuring
the management node. (See
<xref linkend="mysql-cluster-multi-config"/>.)
</para>
@@ -655,7 +629,7 @@
</orderedlist>
Remember that the preceding steps must be performed separately
- on each machine where a data node or SQL node is to reside.
+ on each machine where an SQL node is to reside.
</para>
</formalpara>
@@ -666,16 +640,17 @@
<para>
On each machine to be used for hosting a cluster SQL node,
- install the <emphasis role="bold">MySQL Max</emphasis> RPM by
+ install the <emphasis role="bold">MySQL Server</emphasis> RPM by
executing the following command as the system root user,
replacing the name shown for the RPM as necessary to match the
name of the RPM downloaded from the MySQL AB web site:
<programlisting>
shell> <userinput>rpm -Uhv MySQL-server-¤t-version;-0.glibc23.i386.rpm</userinput>
-shell> <userinput>rpm -Uhv MySQL-Max-¤t-version;-0.glibc23.i386.rpm</userinput>
- This installs the MySQL Max server binary
- (<command>mysqld-max</command>) in the
+</programlisting>
+
+ This installs the MySQL server binary
+ (<command>mysqld</command>) in the
<filename>/usr/sbin</filename> directory, as well as all needed
MySQL Server support files. It also installs the
<command>mysql.server</command> and
@@ -685,19 +660,17 @@
should take care of general configuration issues (such as
creating the <literal>mysql</literal> user and group, if needed)
automatically.
-</programlisting>
</para>
</formalpara>
-
- &mccge-warning-end-cluster;
- <formalpara>
+ <formalpara>
<title>SQL node installation — building from source</title>
<para>
- If you compile MySQL with clustering support (using the
+ If you compile MySQL with clustering support (for example, by
+ using the
<command>BUILD/compile-<replaceable>platform_name</replaceable>-max</command>
script appropriate to your platform), and perform the default
installation (using <command>make install</command> as the root
@@ -718,10 +691,8 @@
</para>
</formalpara>
-
- &mccge-warning-unsupported-begin;
- <formalpara>
+ <formalpara>
<title>Data node installation — RPM Files</title>
@@ -755,9 +726,12 @@
when doing a source build, this file is placed in the directory
<filename>/usr/local/mysql/libexec</filename>. For installing on
multiple data node hosts, only <command>ndbd</command> need be
- copied to the other host machine or machines.
- <command>ndbd</command> need not be in any particular location
- on the host's filesystem, as long as the location is known.
+ copied to the other host machine or machines. (This assumes that
+ all data node hosts use the same architecture and operating
+ system; otherwise you may need to compile separately for each
+ different platform.) <command>ndbd</command> need not be in any
+ particular location on the host's filesystem, as long as the
+ location is known.
</para>
</formalpara>
@@ -767,11 +741,13 @@
<title>Management node installation — <filename>.tar.gz</filename> binary</title>
<para>
- Installation for the management (MGM) node does not require
- installation of the <command>mysqld</command> binary. Only the
- binaries for the MGM server and client are required, which can
- be found in the downloaded archive. Again, we assume that you
- have placed this file in <filename>/var/tmp</filename>.
+ Installation of the management node does not require the
+ <command>mysqld</command> binary. Only the binary for the
+ management server is required, which can be found in the
+ downloaded archive. You most likely want to install the
+ management client as well; this can also be found in the
+ <filename>.tar.gz</filename> archive. Again, we assume that you
+ have placed this archive in <filename>/var/tmp</filename>.
</para>
</formalpara>
@@ -869,10 +845,8 @@
(<command>ndb_mgm</command>) to the <filename>/usr/bin</filename>
directory.
</para>
-
- &mccge-warning-end-cluster;
- <formalpara>
+ <formalpara>
<title>Management node installation — building from source</title>
Modified: trunk/refman-6.0/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/refman-6.0/mysql-cluster-multi-computer.xml 2008-02-09 23:37:45 UTC (rev 9761)
+++ trunk/refman-6.0/mysql-cluster-multi-computer.xml 2008-02-10 13:29:30 UTC (rev 9762)
Changed blocks: 13, Lines Added: 35, Lines Deleted: 37; 8409 bytes
@@ -398,12 +398,13 @@
</indexterm>
<para>
- Each MySQL Cluster host computer running data or SQL nodes must
- have installed on it a MySQL-max binary. For management nodes, it
- is not necessary to install the MySQL server binary, but you do
- have to install the management server daemon
- (<command>ndb_mgmd</command>). It is also a good idea to install
- the management client (<command>ndb_mgm</command>) on the
+ Each MySQL Cluster host computer running SQL nodes must have
+ installed on it a MySQL binary. For management nodes and data
+ nodes, it is not necessary to install the MySQL server binary, but
+ management nodes require the management server daemon
+ (<command>ndb_mgmd</command>) and data nodes require the data node
+ daemon (<command>ndbd</command>). It is also a good idea to
+ install the management client (<command>ndb_mgm</command>) on the
management server host. This section covers the steps necessary to
install the correct binaries for each type of Cluster node.
</para>
@@ -415,7 +416,7 @@
after building MySQL from source.) For setting up a cluster using
MySQL's binaries, the first step in the installation process for
each cluster host is to download the file
- <filename>mysql-max-¤t-version;-pc-linux-gnu-i686.tar.gz</filename>
+ <filename>mysql-¤t-version;-pc-linux-gnu-i686.tar.gz</filename>
from the <ulink url="&base-url-downloads;">MySQL downloads
area</ulink>. We assume that you have placed it in each machine's
<filename>/var/tmp</filename> directory. (If you do require a
@@ -424,7 +425,7 @@
<para>
RPMs are also available for both 32-bit and 64-bit Linux
- platforms. For a MySQL Cluster, four RPMs are required:
+ platforms. For a MySQL Cluster, three RPMs are required:
</para>
<itemizedlist>
@@ -432,22 +433,13 @@
<listitem>
<para>
The <emphasis role="bold">Server</emphasis> RPM (for example,
- <filename>MySQL-server-¤t-version;-0.glibc23.i386.rpm</filename>),
+ <filename>MySQL-Server-¤t-version;-0.glibc23.i386.rpm</filename>),
which supplies the core files needed to run a MySQL Server.
</para>
</listitem>
<listitem>
<para>
- The <emphasis role="bold">Server/Max</emphasis> RPM (for
- example,
- <filename>MySQL-Max-¤t-version;-0.glibc23.i386.rpm</filename>),
- which provides a MySQL Server binary with clustering support.
- </para>
- </listitem>
-
- <listitem>
- <para>
The <emphasis role="bold">NDB Cluster - Storage
engine</emphasis> RPM (for example,
<filename>MySQL-ndb-storage-¤t-version;-0.glibc23.i386.rpm</filename>),
@@ -558,7 +550,7 @@
<para>
Change location to the directory containing the downloaded
file, unpack the archive, and create a symlink to the
- <filename>mysql-max</filename> directory named
+ <filename>mysql</filename> directory named
<filename>mysql</filename>. Note that the actual file and
directory names will vary according to the MySQL version
number.
@@ -566,8 +558,8 @@
<programlisting>
shell> <userinput>cd /var/tmp</userinput>
-shell> <userinput>tar -C /usr/local -xzvf mysql-max-¤t-version;-pc-linux-gnu-i686.tar.gz</userinput>
-shell> <userinput>ln -s /usr/local/mysql-max-¤t-version;-pc-linux-gnu-i686 /usr/local/mysql</userinput>
+shell> <userinput>tar -C /usr/local -xzvf mysql-¤t-version;-pc-linux-gnu-i686.tar.gz</userinput>
+shell> <userinput>ln -s /usr/local/mysql-¤t-version;-pc-linux-gnu-i686 /usr/local/mysql</userinput>
</programlisting>
</listitem>
@@ -599,7 +591,7 @@
<para>
Note that the data directory on each machine hosting a
data node is <filename>/usr/local/mysql/data</filename>.
- We will use this piece of information when we configure
+ This piece of information is essential when configuring
the management node. (See
<xref linkend="mysql-cluster-multi-config"/>.)
</para>
@@ -637,7 +629,7 @@
</orderedlist>
Remember that the preceding steps must be performed separately
- on each machine where a data node or SQL node is to reside.
+ on each machine where an SQL node is to reside.
</para>
</formalpara>
@@ -648,16 +640,17 @@
<para>
On each machine to be used for hosting a cluster SQL node,
- install the <emphasis role="bold">MySQL Max</emphasis> RPM by
+ install the <emphasis role="bold">MySQL Server</emphasis> RPM by
executing the following command as the system root user,
replacing the name shown for the RPM as necessary to match the
name of the RPM downloaded from the MySQL AB web site:
<programlisting>
shell> <userinput>rpm -Uhv MySQL-server-¤t-version;-0.glibc23.i386.rpm</userinput>
-shell> <userinput>rpm -Uhv MySQL-Max-¤t-version;-0.glibc23.i386.rpm</userinput>
- This installs the MySQL Max server binary
- (<command>mysqld-max</command>) in the
+</programlisting>
+
+ This installs the MySQL server binary
+ (<command>mysqld</command>) in the
<filename>/usr/sbin</filename> directory, as well as all needed
MySQL Server support files. It also installs the
<command>mysql.server</command> and
@@ -667,7 +660,6 @@
should take care of general configuration issues (such as
creating the <literal>mysql</literal> user and group, if needed)
automatically.
-</programlisting>
</para>
</formalpara>
@@ -677,7 +669,8 @@
<title>SQL node installation — building from source</title>
<para>
- If you compile MySQL with clustering support (using the
+ If you compile MySQL with clustering support (for example, by
+ using the
<command>BUILD/compile-<replaceable>platform_name</replaceable>-max</command>
script appropriate to your platform), and perform the default
installation (using <command>make install</command> as the root
@@ -733,9 +726,12 @@
when doing a source build, this file is placed in the directory
<filename>/usr/local/mysql/libexec</filename>. For installing on
multiple data node hosts, only <command>ndbd</command> need be
- copied to the other host machine or machines.
- <command>ndbd</command> need not be in any particular location
- on the host's filesystem, as long as the location is known.
+ copied to the other host machine or machines. (This assumes that
+ all data node hosts use the same architecture and operating
+ system; otherwise you may need to compile separately for each
+ different platform.) <command>ndbd</command> need not be in any
+ particular location on the host's filesystem, as long as the
+ location is known.
</para>
</formalpara>
@@ -745,11 +741,13 @@
<title>Management node installation — <filename>.tar.gz</filename> binary</title>
<para>
- Installation for the management (MGM) node does not require
- installation of the <command>mysqld</command> binary. Only the
- binaries for the MGM server and client are required, which can
- be found in the downloaded archive. Again, we assume that you
- have placed this file in <filename>/var/tmp</filename>.
+ Installation of the management node does not require the
+ <command>mysqld</command> binary. Only the binary for the
+ management server is required, which can be found in the
+ downloaded archive. You most likely want to install the
+ management client as well; this can also be found in the
+ <filename>.tar.gz</filename> archive. Again, we assume that you
+ have placed this archive in <filename>/var/tmp</filename>.
</para>
</formalpara>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r9762 - in trunk: refman-5.0 refman-5.1 refman-6.0 | jon | 10 Feb |
