List:Commits« Previous MessageNext Message »
From:jon.stephens Date:April 13 2010 8:37pm
Subject:svn commit - mysqldoc@docsrva: r19999 - in trunk: dynamic-docs/changelog refman-5.1
View as plain text  
Author: jstephens
Date: 2010-04-13 22:37:55 +0200 (Tue, 13 Apr 2010)
New Revision: 19999

Log:

Cluster 7.1 goes GA



Modified:
   trunk/dynamic-docs/changelog/mysqld-versions.xml
   trunk/refman-5.1/mysql-cluster-management.xml
   trunk/refman-5.1/mysql-cluster-multi-computer.xml
   trunk/refman-5.1/mysql-cluster-news-core.xml
   trunk/refman-5.1/mysql-cluster-programs-core.xml
   trunk/refman-5.1/mysql-cluster.xml


Modified: trunk/dynamic-docs/changelog/mysqld-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-versions.xml	2010-04-13 16:45:26 UTC (rev 19998)
+++ trunk/dynamic-docs/changelog/mysqld-versions.xml	2010-04-13 20:37:55 UTC (rev 19999)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 924 bytes

@@ -125,7 +125,7 @@
   <versionentry ver="5.1.46" reldate="Not yet released"/>
   <versionentry ver="5.1.45" reldate="01 March 2010"/>
   <versionentry ver="5.1.44" subver="ndb-7.1.4" reldate="Not yet released"/>
-  <versionentry ver="5.1.44" subver="ndb-7.1.3" reldate="Not yet released"/>
+  <versionentry ver="5.1.44" subver="ndb-7.1.3" reldate="12 April 2010" rellevel="General Availability"/>
   <versionentry ver="5.1.44" subver="ndb-7.0.15" reldate="Not yet released"/>
   <versionentry ver="5.1.44" subver="ndb-7.0.14" reldate="31 March 2010"/>
   <versionentry ver="5.1.44" subver="ndb-6.3.34" reldate="Not yet released"/>


Modified: trunk/refman-5.1/mysql-cluster-management.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-management.xml	2010-04-13 16:45:26 UTC (rev 19998)
+++ trunk/refman-5.1/mysql-cluster-management.xml	2010-04-13 20:37:55 UTC (rev 19999)
Changed blocks: 7, Lines Added: 30, Lines Deleted: 30; 6309 bytes

@@ -1027,7 +1027,7 @@
         </para>
 
 <programlisting>
-id=3    @10.100.2.67  (&mysql-cluster-current-7.0;, <emphasis role="bold">no nodegroup</emphasis>)
+id=3    @10.100.2.67  (&mysql-cluster-current-7.1;, <emphasis role="bold">no nodegroup</emphasis>)
 </programlisting>
 
         <para>

@@ -2043,12 +2043,12 @@
 2007-01-26 19:35:55 [MgmSrvr] INFO     -- Node 4: Resource 0 min: 0 max: 639 curr: 0
 2007-01-26 19:39:42 [MgmSrvr] INFO     -- Node 4: Node 9 Connected
 2007-01-26 19:39:42 [MgmSrvr] INFO     -- Node 1: Node 9 Connected
-2007-01-26 19:39:42 [MgmSrvr] INFO     -- Node 1: Node 9: API &mysql-cluster-current-7.0;
+2007-01-26 19:39:42 [MgmSrvr] INFO     -- Node 1: Node 9: API &mysql-cluster-current-7.1;
 2007-01-26 19:39:42 [MgmSrvr] INFO     -- Node 2: Node 9 Connected
-2007-01-26 19:39:42 [MgmSrvr] INFO     -- Node 2: Node 9: API &mysql-cluster-current-7.0;
+2007-01-26 19:39:42 [MgmSrvr] INFO     -- Node 2: Node 9: API &mysql-cluster-current-7.1;
 2007-01-26 19:39:42 [MgmSrvr] INFO     -- Node 3: Node 9 Connected
-2007-01-26 19:39:42 [MgmSrvr] INFO     -- Node 3: Node 9: API &mysql-cluster-current-7.0;
-2007-01-26 19:39:42 [MgmSrvr] INFO     -- Node 4: Node 9: API &mysql-cluster-current-7.0;
+2007-01-26 19:39:42 [MgmSrvr] INFO     -- Node 3: Node 9: API &mysql-cluster-current-7.1;
+2007-01-26 19:39:42 [MgmSrvr] INFO     -- Node 4: Node 9: API &mysql-cluster-current-7.1;
 2007-01-26 19:59:22 [MgmSrvr] ALERT    -- Node 2: Node 7 Disconnected
 2007-01-26 19:59:22 [MgmSrvr] ALERT    -- Node 2: Node 7 Disconnected
 </programlisting>

@@ -12187,15 +12187,15 @@
 Cluster Configuration
 ---------------------
 [ndbd(NDB)]     2 node(s)
-id=1    @192.168.0.1  (&mysql-cluster-current-7.0;, Nodegroup: 0, Master)
-id=2    @192.168.0.2  (&mysql-cluster-current-7.0;, Nodegroup: 0)
+id=1    @192.168.0.1  (&mysql-cluster-current-7.1;, Nodegroup: 0, Master)
+id=2    @192.168.0.2  (&mysql-cluster-current-7.1;, Nodegroup: 0)
 
 [ndb_mgmd(MGM)] 1 node(s)
-id=10   @192.168.0.10  (&mysql-cluster-current-7.0;)
+id=10   @192.168.0.10  (&mysql-cluster-current-7.1;)
 
 [mysqld(API)]   2 node(s)
-id=20   @192.168.0.20  (&mysql-cluster-current-7.0;)
-id=21   @192.168.0.21  (&mysql-cluster-current-7.0;)
+id=20   @192.168.0.20  (&mysql-cluster-current-7.1;)
+id=21   @192.168.0.21  (&mysql-cluster-current-7.1;)
 </programlisting>
 
       <para>

@@ -12342,7 +12342,7 @@
 
 <programlisting>
 shell&gt; <userinput>ndb_mgmd -f config.ini --reload</userinput>
-2008-12-08 17:29:23 [MgmSrvr] INFO     -- NDB Cluster Management Server. &mysql-cluster-current-7.0;
+2008-12-08 17:29:23 [MgmSrvr] INFO     -- NDB Cluster Management Server. &mysql-cluster-current-7.1;
 2008-12-08 17:29:23 [MgmSrvr] INFO     -- Reading cluster configuration from 'config.ini'
 </programlisting>
         </listitem>

@@ -12363,17 +12363,17 @@
 Cluster Configuration
 ---------------------
 [ndbd(NDB)]     2 node(s)
-id=1    @192.168.0.1  (&mysql-cluster-current-7.0;, Nodegroup: 0, Master)
-id=2    @192.168.0.2  (&mysql-cluster-current-7.0;, Nodegroup: 0)
+id=1    @192.168.0.1  (&mysql-cluster-current-7.1;, Nodegroup: 0, Master)
+id=2    @192.168.0.2  (&mysql-cluster-current-7.1;, Nodegroup: 0)
 id=3 (not connected, accepting connect from 192.168.0.3)
 id=4 (not connected, accepting connect from 192.168.0.4)
 
 [ndb_mgmd(MGM)] 1 node(s)
-id=10   @192.168.0.10  (&mysql-cluster-current-7.0;)
+id=10   @192.168.0.10  (&mysql-cluster-current-7.1;)
 
 [mysqld(API)]   2 node(s)
-id=20   @192.168.0.20  (&mysql-cluster-current-7.0;)
-id=21   @192.168.0.21  (&mysql-cluster-current-7.0;)
+id=20   @192.168.0.20  (&mysql-cluster-current-7.1;)
+id=21   @192.168.0.21  (&mysql-cluster-current-7.1;)
 </programlisting>
 
       <formalpara>

@@ -12489,17 +12489,17 @@
 Cluster Configuration
 ---------------------
 [ndbd(NDB)]     2 node(s)
-id=1    @192.168.0.1  (&mysql-cluster-current-7.0;, Nodegroup: 0, Master)
-id=2    @192.168.0.2  (&mysql-cluster-current-7.0;, Nodegroup: 0)
-id=3    @192.168.0.3  (&mysql-cluster-current-7.0;, <emphasis role="bold">no nodegroup</emphasis>)
-id=4    @192.168.0.4  (&mysql-cluster-current-7.0;, <emphasis role="bold">no nodegroup</emphasis>)
+id=1    @192.168.0.1  (&mysql-cluster-current-7.1;, Nodegroup: 0, Master)
+id=2    @192.168.0.2  (&mysql-cluster-current-7.1;, Nodegroup: 0)
+id=3    @192.168.0.3  (&mysql-cluster-current-7.1;, <emphasis role="bold">no nodegroup</emphasis>)
+id=4    @192.168.0.4  (&mysql-cluster-current-7.1;, <emphasis role="bold">no nodegroup</emphasis>)
 
 [ndb_mgmd(MGM)] 1 node(s)
-id=10   @192.168.0.10  (&mysql-cluster-current-7.0;)
+id=10   @192.168.0.10  (&mysql-cluster-current-7.1;)
 
 [mysqld(API)]   2 node(s)
-id=20   @192.168.0.20  (&mysql-cluster-current-7.0;)
-id=21   @192.168.0.21  (&mysql-cluster-current-7.0;)
+id=20   @192.168.0.20  (&mysql-cluster-current-7.1;)
+id=21   @192.168.0.21  (&mysql-cluster-current-7.1;)
 </programlisting>
 
       <formalpara>

@@ -12533,17 +12533,17 @@
 Cluster Configuration
 ---------------------
 [ndbd(NDB)]     2 node(s)
-id=1    @192.168.0.1  (&mysql-cluster-current-7.0;, Nodegroup: 0, Master)
-id=2    @192.168.0.2  (&mysql-cluster-current-7.0;, Nodegroup: 0)
-id=3    @192.168.0.3  (&mysql-cluster-current-7.0;, <emphasis role="bold">Nodegroup: 1</emphasis>)
-id=4    @192.168.0.4  (&mysql-cluster-current-7.0;, <emphasis role="bold">Nodegroup: 1</emphasis>)
+id=1    @192.168.0.1  (&mysql-cluster-current-7.1;, Nodegroup: 0, Master)
+id=2    @192.168.0.2  (&mysql-cluster-current-7.1;, Nodegroup: 0)
+id=3    @192.168.0.3  (&mysql-cluster-current-7.1;, <emphasis role="bold">Nodegroup: 1</emphasis>)
+id=4    @192.168.0.4  (&mysql-cluster-current-7.1;, <emphasis role="bold">Nodegroup: 1</emphasis>)
 
 [ndb_mgmd(MGM)] 1 node(s)
-id=10   @192.168.0.10  (&mysql-cluster-current-7.0;)
+id=10   @192.168.0.10  (&mysql-cluster-current-7.1;)
 
 [mysqld(API)]   2 node(s)
-id=20   @192.168.0.20  (&mysql-cluster-current-7.0;)
-id=21   @192.168.0.21  (&mysql-cluster-current-7.0;)
+id=20   @192.168.0.20  (&mysql-cluster-current-7.1;)
+id=21   @192.168.0.21  (&mysql-cluster-current-7.1;)
 </programlisting>
 
       <formalpara>


Modified: trunk/refman-5.1/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-multi-computer.xml	2010-04-13 16:45:26 UTC (rev 19998)
+++ trunk/refman-5.1/mysql-cluster-multi-computer.xml	2010-04-13 20:37:55 UTC (rev 19999)
Changed blocks: 20, Lines Added: 39, Lines Deleted: 38; 13254 bytes

@@ -307,12 +307,12 @@
       installing a MySQL Cluster after building MySQL from source. For
       setting up a cluster using MySQL&apos;s binaries, the first step
       in the installation process for each cluster host is to download
-      the latest MySQL Cluster NDB 6.2, MySQL Cluster NDB 6.3, or MySQL
-      Cluster NDB 7.0 binary archive
-      (<filename>mysql-cluster-gpl-&ndb-engine-current-6.2;-linux-i686-glibc23.tar.gz</filename>,
-      <filename>mysql-cluster-gpl-&ndb-engine-current-6.3;-linux-i686-glibc23.tar.gz</filename>,
+      the latest MySQL Cluster NDB 6.3, MySQL Cluster NDB 7.0, or MySQL
+      Cluster NDB 7.1 binary archive
+      (<filename>mysql-cluster-gpl-&ndb-engine-current-6.3;-linux-i686-glibc23.tar.gz</filename>,
+      <filename>mysql-cluster-gpl-&ndb-engine-current-7.0;-linux-i686-glibc23.tar.gz</filename>,
       or
-      <filename>mysql-cluster-gpl-&ndb-engine-current-7.0;-linux-i686-glibc23.tar.gz</filename>,
+      <filename>mysql-cluster-gpl-&ndb-engine-current-7.1;-linux-i686-glibc23.tar.gz</filename>,
       respectively) from the
       <ulink url="&base-url-cluster-downloads;">MySQL Cluster downloads
       area</ulink>. We assume that you have placed this file in each

@@ -322,8 +322,8 @@
     </para>
 
     <para>
-      When compiling MySQL Cluster NDB 7.0 from source, no special
-      options are required for building multi-threaded data node
+      When compiling MySQL Cluster NDB 7.0 or later from source, no
+      special options are required for building multi-threaded data node
       binaries. On Unix platforms, configuring the build with any of the
       options <option>--plugins=ndbcluster</option>,
       <option>--plugins=max</option>, or,

@@ -372,10 +372,10 @@
       <listitem>
         <para>
           The <emphasis role="bold">Server</emphasis> RPM (for example,
-          <filename>MySQL-Cluster-gpl-server-&ndb-engine-current-6.2;-0.sles10.i586.rpm</filename>,
           <filename>MySQL-Cluster-gpl-server-&ndb-engine-current-6.3;-0.sles10.i586.rpm</filename>,
+          <filename>MySQL-Cluster-gpl-server-&ndb-engine-current-7.0;-0.sles10.i586.rpm</filename>,
           or
-          <filename>MySQL-Cluster-gpl-server-&ndb-engine-current-7.0;-0.sles10.i586.rpm</filename>),
+          <filename>MySQL-Cluster-gpl-server-&ndb-engine-current-7.1;-0.sles10.i586.rpm</filename>),
           which supplies the core files needed to run a MySQL Server
           with <literal role="se">NDBCLUSTER</literal> storage engine
           support (that is, as a MySQL Cluster SQL node).

@@ -386,10 +386,10 @@
           administering a MySQL server, you should also obtain and
           install the <emphasis role="bold">Client</emphasis> RPM (for
           example,
-          <filename>MySQL-Cluster-gpl-client-&ndb-engine-current-6.2;-0.sles10.i586.rpm</filename>,
           <filename>MySQL-Cluster-gpl-client-&ndb-engine-current-6.3;-0.sles10.i586.rpm</filename>,
+          <filename>MySQL-Cluster-gpl-client-&ndb-engine-current-7.0;-0.sles10.i586.rpm</filename>,
           or
-          <filename>MySQL-Cluster-gpl-client-&ndb-engine-current-7.0;-0.sles10.i586.rpm</filename>).
+          <filename>MySQL-Cluster-gpl-client-&ndb-engine-current-7.1;-0.sles10.i586.rpm</filename>).
         </para>
       </listitem>
 

@@ -397,10 +397,10 @@
         <para>
           The <emphasis role="bold">Cluster storage engine</emphasis>
           RPM (for example,
-          <filename>MySQL-Cluster-gpl-storage-&ndb-engine-current-6.2;-0.sles10.i586.rpm</filename>,
           <filename>MySQL-Cluster-gpl-storage-&ndb-engine-current-6.3;-0.sles10.i586.rpm</filename>,
+          <filename>MySQL-Cluster-gpl-storage-&ndb-engine-current-7.0;-0.sles10.i586.rpm</filename>,
           or
-          <filename>MySQL-Cluster-gpl-storage-&ndb-engine-current-7.0;-0.sles10.i586.rpm</filename>),
+          <filename>MySQL-Cluster-gpl-storage-&ndb-engine-current-7.1;-0.sles10.i586.rpm</filename>),
           which supplies the MySQL Cluster data node binary
           (<command>ndbd</command>).
         </para>

@@ -410,10 +410,10 @@
         <para>
           The <emphasis role="bold">Cluster storage engine management
           RPM</emphasis> (for example,
-          <filename>MySQL-Cluster-gpl-management-&ndb-engine-current-6.2;-0.sles10.i586.rpm</filename>,
           <filename>MySQL-Cluster-gpl-management-&ndb-engine-current-6.3;-0.sles10.i586.rpm</filename>,
+          <filename>MySQL-Cluster-gpl-management-&ndb-engine-current-7.0;-0.sles10.i586.rpm</filename>,
           or
-          <filename>MySQL-Cluster-gpl-management-&ndb-engine-current-7.0;-0.sles10.i586.rpm</filename>)
+          <filename>MySQL-Cluster-gpl-management-&ndb-engine-current-7.1;-0.sles10.i586.rpm</filename>)
           which provides the MySQL Cluster management server binary
           (<command>ndb_mgmd</command>).
         </para>

@@ -424,19 +424,19 @@
     <para>
       In addition, you should also obtain the <emphasis role="bold">NDB
       Cluster - Storage engine basic tools</emphasis> RPM (for example,
-      <filename>MySQL-Cluster-gpl-tools-&ndb-engine-current-6.2;-0.sles10.i586.rpm</filename>,
       <filename>MySQL-Cluster-gpl-tools-&ndb-engine-current-6.3;-0.sles10.i586.rpm</filename>,
+      <filename>MySQL-Cluster-gpl-tools-&ndb-engine-current-7.0;-0.sles10.i586.rpm</filename>,
       or
-      <filename>MySQL-Cluster-gpl-tools-&ndb-engine-current-7.0;-0.sles10.i586.rpm</filename>),
+      <filename>MySQL-Cluster-gpl-tools-&ndb-engine-current-7.1;-0.sles10.i586.rpm</filename>),
       which supplies several useful applications for working with a
       MySQL Cluster. The most important of these is the MySQL Cluster
       management client (<command>ndb_mgm</command>). The
       <emphasis role="bold">NDB Cluster - Storage engine extra
       tools</emphasis> RPM (for example,
-      <filename>MySQL-Cluster-gpl-extra-&ndb-engine-current-6.2;-0.sles10.i586.rpm</filename>,
       <filename>MySQL-Cluster-gpl-extra-&ndb-engine-current-6.3;-0.sles10.i586.rpm</filename>,
+      <filename>MySQL-Cluster-gpl-extra-&ndb-engine-current-7.0;-0.sles10.i586.rpm</filename>,
       or
-      <filename>MySQL-Cluster-gpl-extra-&ndb-engine-current-7.0;-0.sles10.i586.rpm</filename>)
+      <filename>MySQL-Cluster-gpl-extra-&ndb-engine-current-7.1;-0.sles10.i586.rpm</filename>)
       contains some additional testing and monitoring programs, but is
       not required to install a MySQL Cluster. (For more information
       about these additional programs, see

@@ -445,9 +445,9 @@
 
     <para>
       The MySQL Cluster version number in the RPM file names (shown here
-      as <literal>&ndb-engine-current-6.2;</literal>,
-      <literal>&ndb-engine-current-6.3;</literal>, or
-      <literal>&ndb-engine-current-7.0;</literal>) can vary according to
+      as <literal>&ndb-engine-current-6.3;</literal>,
+      <literal>&ndb-engine-current-7.0;</literal>, or
+      <literal>&ndb-engine-current-7.1;</literal>) can vary according to
       the version which you are actually using. <emphasis>It is very
       important that all of the Cluster RPMs to be installed have the
       same version number</emphasis>. The <literal>glibc</literal>

@@ -526,8 +526,8 @@
 
 <programlisting>
 shell&gt; <userinput>cd /var/tmp</userinput>
-shell&gt; <userinput>tar -C /usr/local -xzvf mysql-cluster-gpl-&ndb-engine-current-7.0;-linux-i686-glibc23.tar.gz</userinput>
-shell&gt; <userinput>ln -s /usr/local/mysql-cluster-gpl-&ndb-engine-current-7.0;-linux-i686-glibc23.tar.gz /usr/local/mysql</userinput>
+shell&gt; <userinput>tar -C /usr/local -xzvf mysql-cluster-gpl-&ndb-engine-current-7.1;-linux-i686-glibc23.tar.gz</userinput>
+shell&gt; <userinput>ln -s /usr/local/mysql-cluster-gpl-&ndb-engine-current-7.1;-linux-i686-glibc23.tar.gz /usr/local/mysql</userinput>
 </programlisting>
           </listitem>
 

@@ -614,7 +614,7 @@
         name of the RPM downloaded from the MySQL web site:
 
 <programlisting>
-shell&gt; <userinput>rpm -Uhv MySQL-Cluster-gpl-server-&ndb-engine-current-7.0;-0.sles10.i586.rpm</userinput>
+shell&gt; <userinput>rpm -Uhv MySQL-Cluster-gpl-server-&ndb-engine-current-7.1;-0.sles10.i586.rpm</userinput>
 </programlisting>
 
         This installs the MySQL server binary

@@ -636,7 +636,7 @@
             shown here:
 
 <programlisting>
-shell&gt; <userinput>rpm -Uhv MySQL-Cluster-gpl-client-&ndb-engine-current-7.0;-0.sles10.i586.rpm</userinput>
+shell&gt; <userinput>rpm -Uhv MySQL-Cluster-gpl-client-&ndb-engine-current-7.1;-0.sles10.i586.rpm</userinput>
 </programlisting>
 
             This installs the <command>mysql</command> client program.

@@ -687,7 +687,7 @@
         that of the RPM downloaded from the MySQL web site:
 
 <programlisting>
-shell&gt; <userinput>rpm -Uhv MySQL-Cluster-gpl-storage-&ndb-engine-current-7.0;-0.sles10.i586.rpm</userinput>
+shell&gt; <userinput>rpm -Uhv MySQL-Cluster-gpl-storage-&ndb-engine-current-7.1;-0.sles10.i586.rpm</userinput>
 </programlisting>
 
         The previous command installs the MySQL Cluster data node binary

@@ -763,8 +763,8 @@
 
 <programlisting>
 shell&gt; <userinput>cd /var/tmp</userinput>
-shell&gt; <userinput>tar -zxvf mysql-&mysql-cluster-current-7.0;-linux-i686-glibc23.tar.gz</userinput>
-shell&gt; <userinput>cd mysql-&mysql-cluster-current-7.0;-linux-i686-glibc23</userinput>
+shell&gt; <userinput>tar -zxvf mysql-&mysql-cluster-current-7.1;-linux-i686-glibc23.tar.gz</userinput>
+shell&gt; <userinput>cd mysql-&mysql-cluster-current-7.1;-linux-i686-glibc23</userinput>
 shell&gt; <userinput>cp bin/ndb_mgm* /usr/local/bin</userinput>
 </programlisting>
 

@@ -807,7 +807,7 @@
         downloaded from the MySQL web site):
 
 <programlisting>
-shell&gt; <userinput>rpm -Uhv MySQL-Cluster-gpl-management-&ndb-engine-current-7.0;-0.sles10.i586.rpm</userinput>
+shell&gt; <userinput>rpm -Uhv MySQL-Cluster-gpl-management-&ndb-engine-current-7.1;-0.sles10.i586.rpm</userinput>
 </programlisting>
 
         This installs the management server binary

@@ -828,7 +828,7 @@
       tools</emphasis> RPM downloaded from the MySQL web site):
 
 <programlisting>
-shell&gt; <userinput>rpm -Uhv MySQL-Cluster-gpl-tools-&ndb-engine-current-7.0;-0.sles10.i586.rpm</userinput>
+shell&gt; <userinput>rpm -Uhv MySQL-Cluster-gpl-tools-&ndb-engine-current-7.1;-0.sles10.i586.rpm</userinput>
 </programlisting>
 
       The <emphasis role="bold">Storage engine basic tools</emphasis>

@@ -842,7 +842,7 @@
           engine extra tools</emphasis> RPM, if you wish, as shown here:
 
 <programlisting>
-shell&gt; <userinput>rpm -Uhv MySQL-Cluster-gpl-extra-&ndb-engine-current-7.0;-0.sles10.i586.rpm</userinput>
+shell&gt; <userinput>rpm -Uhv MySQL-Cluster-gpl-extra-&ndb-engine-current-7.1;-0.sles10.i586.rpm</userinput>
 </programlisting>
 
           You may find the extra tools useful; however the

@@ -884,7 +884,8 @@
       <title>MySQL Cluster on Windows (<emphasis>alpha</emphasis>)</title>
 
       <para>
-        In MySQL Cluster NDB 7.0, experimental support is added for
+        In MySQL Cluster NDB 7.0 and MySQL Cluster NDB 7.1,
+        <emphasis>experimental</emphasis> support is provided for
         Microsoft Windows platforms. To compile MySQL Cluster from
         source on Windows, you must configure the build using the
         <literal>WITH_NDBCLUSTER_STORAGE_ENGINE</literal> option before

@@ -2035,7 +2036,7 @@
           <para>
             When upgrading the cluster from a MySQL Cluster NDB 6.3
             release to a MySQL Cluster NDB 7.0 release: Once you have
-            started upgraded the API nodes, you should not perform DDL
+            started upgrading the API nodes, you should not perform DDL
             operations until all management nodes and data nodes have
             been upgraded. DML operations should be unaffected, and can
             continue while the upgrade is in progress.

@@ -2699,9 +2700,9 @@
 
                 <para>
                   For upgrades to MySQL Cluster NDB 7.0 releases prior
-                  to version 7.0.9, a workaround are available:
-                  Following the upgrade, perform a second rolling
-                  restart of the cluster before before performing any
+                  to version 7.0.9, a workaround is available: Following
+                  the upgrade, perform a second rolling restart of the
+                  cluster before before performing any
                   <literal role="stmt">ALTER TABLE</literal> operations
                   involving indexes.
                 </para>

@@ -2726,7 +2727,7 @@
                 release from a MySQL Cluster NDB 7.0 release, you should
                 not attempt to create any new tables until all data
                 nodes are using the new <command>ndbd</command> or
-                <command>ndbmtd</command> binary. This is because the
+                <command>ndbmtd</command> binaries. This is because the
                 older binaries do not provide support for native default
                 values; tables created with native default value support
                 cannot be used with NDB 7.0.x or earlier versions of the


Modified: trunk/refman-5.1/mysql-cluster-news-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-news-core.xml	2010-04-13 16:45:26 UTC (rev 19998)
+++ trunk/refman-5.1/mysql-cluster-news-core.xml	2010-04-13 20:37:55 UTC (rev 19999)
Changed blocks: 4, Lines Added: 42, Lines Deleted: 44; 5708 bytes

@@ -129,23 +129,24 @@
       <title condition="dynamic:changelog:vertitle" role="5.1.44-ndb-7.1.4:mysqld:all"/>
 
       <para role="release-level">
-        MySQL Cluster NDB 7.1.4 is a new beta release of MySQL Cluster,
+        MySQL Cluster NDB 7.1.4 is a new release of MySQL Cluster,
         incorporating new features in the
         <literal role="se">NDBCLUSTER</literal> storage engine and
         fixing recently discovered bugs in MySQL Cluster NDB 7.1.3 and
         previous MySQL Cluster releases.
       </para>
 
-<!--      
-      <formalpara>
+<!--
+        <formalpara>
         
-        <title>Obtaining MySQL Cluster NDB 7.1.3</title>
+        <title>Obtaining MySQL Cluster NDB 7.1.4</title>
         
-        
         <para>
-          It is a source-only
-          release, which can be downloaded from the MySQL FTP site, at
-          <uri>ftp://ftp.mysql.com/pub/mysql/download/mysql-5.1.44-ndb-7.1.4-beta.tgz</uri>.
+          The latest MySQL Cluster NDB 7.1 binaries for supported
+          platforms can be obtained from
+          <ulink url="&base-url-cluster-downloads;"/>. Source
+          code for the latest MySQL Cluster NDB 7.1 release can be
+          obtained from the same location.
         </para>
         
       </formalpara>

@@ -153,10 +154,9 @@
 
       <para>
         This release also incorporates all bugfixes and changes made in
-        previous MySQL Cluster NDB 6.1, 6.2, 6.3, and 7.0 releases, as
-        well as all bugfixes and feature changes which were added in
-        mainline MySQL 5.1 through MySQL 5.1.44 (see
-        <xref linkend="news-5-1-44"/>).
+        previous MySQL Cluster releases, as well as all bugfixes and
+        feature changes which were added in mainline MySQL 5.1 through
+        MySQL 5.1.44 (see <xref linkend="news-5-1-44"/>).
       </para>
 
       <para condition="dynamic:changelog:entrylist" role="5.1.44-ndb-7.1.4:mysqld:all"/>

@@ -168,34 +168,34 @@
       <title condition="dynamic:changelog:vertitle" role="5.1.44-ndb-7.1.3:mysqld:all"/>
 
       <para role="release-level">
-        MySQL Cluster NDB 7.1.3 is a new beta release of MySQL Cluster,
-        incorporating new features in the
+        MySQL Cluster NDB 7.1.3 is the first <emphasis>General
+        Availability</emphasis> release in the MySQL Cluster NDB 7.1
+        release series, incorporating new features in the
         <literal role="se">NDBCLUSTER</literal> storage engine and
-        fixing recently discovered bugs in MySQL Cluster NDB 7.1.2 and
-        previous MySQL Cluster releases.
+        fixing recently discovered bugs in MySQL Cluster NDB 7.1.2-beta
+        and previous MySQL Cluster releases.
       </para>
 
-<!--      
       <formalpara>
-        
+
         <title>Obtaining MySQL Cluster NDB 7.1.3</title>
-        
-        
+
         <para>
-          It is a source-only
-          release, which can be downloaded from the MySQL FTP site, at
-          <uri>ftp://ftp.mysql.com/pub/mysql/download/mysql-5.1.44-ndb-7.1.3-beta.tgz</uri>.
+          The latest MySQL Cluster NDB 7.1 binaries for supported
+          platforms can be obtained from
+          <ulink url="&base-url-cluster-downloads;"/>. Source code for
+          the latest MySQL Cluster NDB 7.1 release can be obtained from
+          the same location.
         </para>
-        
+
       </formalpara>
--->
 
       <para>
         This release also incorporates all bugfixes and changes made in
-        previous MySQL Cluster NDB 6.1, 6.2, 6.3, and 7.0 releases, as
-        well as all bugfixes and feature changes which were added in
-        mainline MySQL 5.1 through MySQL 5.1.44 (see
-        <xref linkend="news-5-1-44"/>).
+        previous MySQL Cluster NDB 6.x, MySQL Cluster NDB 7.0, and MySQL
+        Cluster NDB 7.1 releases, as well as all bugfixes and feature
+        changes which were added in mainline MySQL 5.1 through MySQL
+        5.1.44 (see <xref linkend="news-5-1-44"/>).
       </para>
 
       <para condition="dynamic:changelog:entrylist" role="5.1.44-ndb-7.1.3:mysqld:all"/>

@@ -427,24 +427,22 @@
         recently discovered bugs in MySQL Cluster NDB 7.0.13.
       </para>
 
-<!--      
-        <formalpara>
-        
-        <title>Obtaining MySQL Cluster NDB 7.0.13</title>
-        
+      <formalpara>
+
+        <title>Obtaining MySQL Cluster NDB 7.0.14</title>
+
         <para>
-        The latest MySQL Cluster NDB 7.0 binaries for supported
-        platforms can be obtained from
-        <ulink url="&base-url-cluster-downloads;"/>. Source
-        code for the latest MySQL Cluster NDB 7.0 release can be
-        obtained from the same location. You can also access the MySQL
-        Cluster NDB 7.0 development source tree at
-        <ulink url="https://code.launchpad.net/~mysql/mysql-server/mysql-cluster-7.0"/>.
+          The latest MySQL Cluster NDB 7.0 binaries for supported
+          platforms can be obtained from
+          <ulink url="&base-url-cluster-downloads;"/>. Source code for
+          the latest MySQL Cluster NDB 7.0 release can be obtained from
+          the same location. You can also access the MySQL Cluster NDB
+          7.0 development source tree at
+          <ulink url="https://code.launchpad.net/~mysql/mysql-server/mysql-cluster-7.0"/>.
         </para>
-        
-        </formalpara>
-      -->
 
+      </formalpara>
+
       <para>
         This release also incorporates all bugfixes and changes made in
         previous MySQL Cluster NDB 6.1, 6.2, 6.3, and 7.0 releases, as


Modified: trunk/refman-5.1/mysql-cluster-programs-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-programs-core.xml	2010-04-13 16:45:26 UTC (rev 19998)
+++ trunk/refman-5.1/mysql-cluster-programs-core.xml	2010-04-13 20:37:55 UTC (rev 19999)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 662 bytes

@@ -3692,7 +3692,7 @@
 You can turn off this feature to get a quicker startup with -A
 
 Welcome to the MySQL monitor.  Commands end with ; or \g.
-Your MySQL connection id is 7 to server version: &mysql-cluster-current-7.0;
+Your MySQL connection id is 7 to server version: &mysql-cluster-current-7.1;
 
 Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
 


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2010-04-13 16:45:26 UTC (rev 19998)
+++ trunk/refman-5.1/mysql-cluster.xml	2010-04-13 20:37:55 UTC (rev 19999)
Changed blocks: 7, Lines Added: 49, Lines Deleted: 37; 7661 bytes

@@ -52,13 +52,13 @@
     <literal role="se">NDBCLUSTER</literal> storage engine was removed
     from the standard MySQL server binaries built by MySQL. Instead,
     users of MySQL Cluster binaries built by MySQL should upgrade to the
-    most recent binary release of MySQL Cluster NDB 6.3 or MySQL Cluster
-    7.0 for supported platforms &mdash; these include RPMs that should
+    most recent binary release of MySQL Cluster NDB 7.0 or MySQL Cluster
+    7.1 for supported platforms &mdash; these include RPMs that should
     work with most Linux distributions. MySQL Cluster users who build
     from source should be aware that, also beginning with MySQL 5.1.24,
     <literal role="se">NDBCLUSTER</literal> sources in the standard
     MySQL 5.1 tree are no longer maintained; these users should use the
-    sources provided for MySQL Cluster NDB 6.2 or later. (Locations
+    sources provided for MySQL Cluster NDB 7.0 or later. (Locations
     where the sources can be obtained are listed later in this section.)
   </para>
 

@@ -84,22 +84,32 @@
     releases through &mysql-cluster-current-6.3;, MySQL Cluster NDB 7.0
     releases through &mysql-cluster-current-7.0; and MySQL Cluster NDB
     7.1 releases through &mysql-cluster-current-7.1;. Currently, the
-    MySQL Cluster NDB 6.3 and MySQL Cluster NDB 7.0 (formerly known as
-    <quote>MySQL Cluster NDB 6.4</quote>) release series are Generally
-    Available (GA). MySQL Cluster NDB 6.2, a previous GA release series,
-    is still supported, although we recommend that new deployments use
-    MySQL Cluster NDB 6.3 or MySQL Cluster NDB 7.0. MySQL Cluster NDB
-    7.1 is currently under development; we expect to make source and
+    MySQL Cluster NDB 7.0 (formerly known as <quote>MySQL Cluster NDB
+    6.4</quote>) and MySQL Cluster NDB 7.1 release series are Generally
+    Available (GA). MySQL Cluster NDB 6.2 and MySQL Cluster NDB 6.3 are
+    previous GA release series; although these are still supported, we
+    recommend that new deployments use MySQL Cluster NDB 7.0 or MySQL
+    Cluster NDB 7.1.
+
+    <remark role="note">
+      [js] Next sentence commented out until we have a successor to NDB
+      7.1.x.
+    </remark>
+
+<!--
+    MySQL Cluster NDB
+    7.2 is currently under development; we expect to make source and
     binaries built from the MySQL Cluster NDB 7.1 available for
     evaluation and testing purposes in the near future.
+-->
   </para>
 
   <para>
     This chapter also contains historical information about MySQL
     Cluster NDB 6.1, although this release series is no longer in active
-    development, and should not be used in new deployments. Users of
-    MySQL Cluster NDB 6.1 should upgrade to a later MySQL Cluster NDB
-    6.x or 7.x release series as soon as possible.
+    development, and no longer supported for new deployments. You should
+    upgrade to MySQL Cluster 6.3 or a MySQL Cluster NDB 7.x release
+    series as soon as possible.
   </para>
 
   <indexterm>

@@ -115,20 +125,22 @@
       MySQL Cluster is currently available and supported on a number of
       platforms, including Linux, Solaris, Mac OS X, and other
       Unix-style operating systems on a variety of hardware. Beginning
-      with MySQL Cluster NDB 7.0, MySQL Cluster is also available (on an
-      experimental basis) on Microsoft Windows platforms. For exact
-      levels of support available for on specific combinations of
-      operating system versions, operating system distributions, and
-      hardware platforms, please refer to
-      <citetitle>http://www.mysql.com/support/supportedplatforms/cluster.html</citetitle>,
-      maintained by the MySQL Support Team on the MySQL web site.
+      with MySQL Cluster NDB 7.0 and MySQL Cluster NDB 7.1, MySQL
+      Cluster is also available (on an experimental basis) on Microsoft
+      Windows platforms. For exact levels of support available for on
+      specific combinations of operating system versions, operating
+      system distributions, and hardware platforms, please refer to
+
+      <uri>http://www.mysql.com/support/supportedplatforms/cluster.html</uri>
+
+      , maintained by the MySQL Support Team on the MySQL web site.
     </para>
 
   </formalpara>
 
   <para>
     We are continuing to work to make MySQL Cluster available on all
-    operating systems supported by MySQL; we will update the information
+    operating systems supported by MySQL; we update the information
     provided here as this work continues.
   </para>
 

@@ -137,8 +149,8 @@
     <title>Availability</title>
 
     <para>
-      MySQL Cluster NDB 6.2, MySQL Cluster NDB 6.3, and MySQL Cluster
-      NDB 7.0 binary and source packages are available for supported
+      MySQL Cluster NDB 6.3, MySQL Cluster NDB 7.0, and MySQL Cluster
+      NDB 7.1 binary and source packages are available for supported
       platforms from <ulink url="&base-url-cluster-downloads;"/>.
     </para>
 

@@ -156,15 +168,15 @@
     <title>MySQL Cluster release numbers</title>
 
     <para>
-      Starting with MySQL Cluster NDB 6.1 and 6.2, MySQL Cluster follows
-      a somewhat different release pattern from the mainline MySQL 5.1
-      Cluster series of releases. In this Manual and other MySQL
-      documentation, we identify these and later MySQL Cluster releases
-      employing a version number that begins with <quote>NDB</quote>.
-      This version number is that of the
-      <literal role="es">NDBCLUSTER</literal> storage engine used, and
-      not of the MySQL server version on which the MySQL Cluster release
-      is based.
+      Starting with MySQL Cluster NDB 6.1 and MySQL Cluster NDB 6.2,
+      MySQL Cluster follows a somewhat different release pattern from
+      the mainline MySQL 5.1 Cluster series of releases. In this
+      <citetitle>Manual</citetitle> and other MySQL documentation, we
+      identify these and later MySQL Cluster releases employing a
+      version number that begins with <quote>NDB</quote>. This version
+      number is that of the <literal role="es">NDBCLUSTER</literal>
+      storage engine used in the release, and not of the MySQL server
+      version on which the MySQL Cluster release is based.
     </para>
 
   </formalpara>

@@ -195,13 +207,13 @@
 shell&gt; <userinput>mysql</userinput>
 Welcome to the MySQL monitor.  Commands end with ; or \g.
 Your MySQL connection id is 2
-Server version: &mysql-cluster-current-7.0; Source distribution
+Server version: &mysql-cluster-current-7.1; Source distribution
 
 Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
 
 mysql&gt; <userinput>SELECT VERSION()\G</userinput>
 *************************** 1. row ***************************
-VERSION(): &mysql-cluster-current-7.0;
+VERSION(): &mysql-cluster-current-7.1;
 1 row in set (0.00 sec)
 </programlisting>
 

@@ -215,14 +227,14 @@
 Cluster Configuration
 ---------------------
 [ndbd(NDB)]     2 node(s)
-id=1    @10.0.10.6  (&mysql-cluster-current-7.0;, Nodegroup: 0, Master)
-id=2    @10.0.10.8  (&mysql-cluster-current-7.0;, Nodegroup: 0)
+id=1    @10.0.10.6  (&mysql-cluster-current-7.1;, Nodegroup: 0, Master)
+id=2    @10.0.10.8  (&mysql-cluster-current-7.1;, Nodegroup: 0)
 
 [ndb_mgmd(MGM)] 1 node(s)
-id=3    @10.0.10.2  (&mysql-cluster-current-7.0;)
+id=3    @10.0.10.2  (&mysql-cluster-current-7.1;)
 
 [mysqld(API)]   2 node(s)
-id=4    @10.0.10.10  (&mysql-cluster-current-7.0;)
+id=4    @10.0.10.10  (&mysql-cluster-current-7.1;)
 id=5 (not connected, accepting connect from any host)
 </programlisting>
 


Thread
svn commit - mysqldoc@docsrva: r19999 - in trunk: dynamic-docs/changelog refman-5.1jon.stephens13 Apr