From: jon
Date: February 27 2007 7:47am
Subject: svn commit - mysqldoc@docsrva: r5076 - branches/telcos/refman-5.1
List-Archive: http://lists.mysql.com/commits/20625
Message-Id: <200702270747.l1R7lUxu020356@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2007-02-27 08:47:29 +0100 (Tue, 27 Feb 2007)
New Revision: 5076

Log:

Changes in ndb_show_tables and ArbitrationRank behaviour for 
telco-6.1.3 release.



Modified:
   branches/telcos/refman-5.1/mysql-cluster.xml
   branches/telcos/refman-5.1/news-5.1.xml


Modified: branches/telcos/refman-5.1/mysql-cluster.xml
===================================================================
--- branches/telcos/refman-5.1/mysql-cluster.xml	2007-02-27 06:33:03 UTC (rev 5075)
+++ branches/telcos/refman-5.1/mysql-cluster.xml	2007-02-27 07:47:29 UTC (rev 5076)
Changed blocks: 4, Lines Added: 13, Lines Deleted: 6; 1930 bytes

@@ -3419,7 +3419,7 @@
 
             <para>
               This parameter is used to define which nodes can act as
-              arbitrators. Only MGM nodes and SQL nodes can be
+              arbitrators. Only management nodes and SQL nodes can be
               arbitrators. <literal>ArbitrationRank</literal> can take
               one of the following values:
             </para>

@@ -3457,6 +3457,13 @@
               <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
+              <literal>ArbitrationRank</literal> to 0 on all management
+              and SQL nodes.
+            </para>
           </listitem>
 
           <listitem>

@@ -14708,11 +14715,6 @@
         <primary><command>ndb_show_tables</command></primary>
       </indexterm>
 
-      <remark role="todo">
-        [js] Remove references to Disk Data objects from the following
-        narrative for the 4.1 and 5.0 versions.
-      </remark>
-
       <para>
         <emphasis role="bold">Description</emphasis>: Displays a list of
         all <literal>NDB</literal> database objects in the cluster. By

@@ -14721,6 +14723,11 @@
         <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.
+      </para>
 
       <para>
         <emphasis role="bold">Usage</emphasis>:


Modified: branches/telcos/refman-5.1/news-5.1.xml
===================================================================
--- branches/telcos/refman-5.1/news-5.1.xml	2007-02-27 06:33:03 UTC (rev 5075)
+++ branches/telcos/refman-5.1/news-5.1.xml	2007-02-27 07:47:29 UTC (rev 5076)
Changed blocks: 3, Lines Added: 39, Lines Deleted: 5; 2567 bytes

@@ -68,8 +68,6 @@
       <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:

@@ -80,10 +78,22 @@
               <para>
                 You cannot perform an online upgrade to this release
                 from MySQL 5.1.14/NDB-6.1.0, MySQL 5.1.15/NDB-6.1.1, or
-                any of the mainline MySQL 5.1 releases. You must shut
-                down the cluster, replace all binaries, then restart the
-                cluster.
+                any of the mainline MySQL 5.1 releases. When upgrading
+                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 
+                <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.
+                When upgrading the data nodes, you will need to restart
+                each data with the <option>--initial</option> option.
+              </para>
             </listitem>
             
             <listitem>

@@ -99,7 +109,31 @@
       </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 
+          <xref linkend="mysql-cluster-utilities-ndb-show-tables"/>.)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          It is now possible to disable arbitration by setting
+          <literal>ArbitrationRank=0</literal> on all management and SQL
+          nodes.
+        </para>
+      </listitem>
+    </itemizedlist>
+    
+    
+    <para>
       This release fixes the folowing bugs:
     </para>