svn commit - mysqldoc@docsrva: r7941 - trunk/refman-5.1

[jon]

Author: jstephens
Date: 2007-10-02 18:15:49 +0200 (Tue, 02 Oct 2007)
New Revision: 7941

Log:

New behaviour for --ndb_optimized_node_selection in CGE-6.3.4 (Mikael)



Modified:
   trunk/refman-5.1/dba-core.xml
   trunk/refman-5.1/mysql-cluster-cge.xml
   trunk/refman-5.1/news-5.1.xml


Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml	2007-10-02 14:18:25 UTC (rev 7940)
+++ trunk/refman-5.1/dba-core.xml	2007-10-02 16:15:49 UTC (rev 7941)
Changed blocks: 1, Lines Added: 83, Lines Deleted: 4; 4504 bytes

@@ -6260,15 +6260,94 @@
             </para>
 
             <para>
-              Causes an SQL node to contact the nearest data node in the
-              cluster. Enabled by default. Set to <literal>0</literal>
-              or <literal>OFF</literal> to disable, in which case the
-              SQL node attempts to contact data nodes in succession.
+              Causes an SQL node to use a data node on the same host
+              machine as transaction coordinator. Enabled by default.
+              Set to <literal>0</literal> or
<literal>OFF</literal> to
+              disable, in which case the SQL node uses each data node in
+              the cluster in succession. When this option is disabled,
+              or if there is no data node process running on the same
+              host as the SQL node, the SQL node attempts to use a given
+              data node 8 times before proceeding to the next one.
             </para>
 
             <para>
               Added in MySQL 4.1.9.
             </para>
+            
+            &mccge-warning-begin;
+            
+            <para>
+              In MySQL 5.1.22-ndb-6.3.4 and later &mccge-series;
+              6.3.<replaceable>x</replaceable> releases, this option
+              takes one of the integer values <literal>0</literal>,
+              <literal>1</literal>, <literal>2</literal>, or
+              <literal>3</literal>, with <literal>1</literal>
being the
+              default. These values affect node selection as follows:
+
+              <itemizedlist>
+
+                <listitem>
+                  <para>
+                    <literal>0</literal>: Each data node is employed as
+                    the transaction coordinator 8 times before the SQL
+                    node proceeds to the next data node. (This is the
+                    same behavior as caused by setting this option to
+                    <literal>0</literal> or
<literal>OFF</literal> in
+                    previous MySQL versions.)
+                  </para>
+                </listitem>
+
+                <listitem>
+                  <para>
+                    <literal>1</literal>: If a data node process is
+                    running on the the same host as the SQL node, this
+                    data node is used as the transaction coordinator.
+                    (This is the same behavior as caused by setting this
+                    option to <literal>1</literal> or
+                    <literal>ON</literal> in previous MySQL versions.)
+                  </para>
+                </listitem>
+
+                <listitem>
+                  <para>
+                    <literal>2</literal>: The SQL node follows the same
+                    behavior as if this option had been set to
+                    <literal>1</literal>; however, the setting is
+                    global.
+                  </para>
+                </listitem>
+
+                <listitem>
+                  <para>
+                    <literal>3</literal>: The data node housing the
+                    cluster partition accessed by the first statement of
+                    a given transaction is used as the transaction
+                    coordinator for the entire transaction. This is
+                    effective only if the first statement of the
+                    transaction accesses no more than one cluster
+                    partition; otherwise, the SQL node reverts to the
+                    round-robin behavior seen when this option is set to
+                    <literal>0</literal>.
+                  </para>
+                </listitem>
+
+              </itemizedlist>
+
+              <important>
+                <para>
+                  In MySQL 5.1.22-ndb-6.3.4 and later &mccge-series;
+                  6.3.<replaceable>x</replaceable> versions, it is no
+                  longer possible to
+                  <option>--ndb_optimized_node_selection</option> to
+                  <literal>ON</literal> or
<literal>OFF</literal>;
+                  attempting to do so causes <command>mysqld</command>
+                  to abort with an error.
+                </para>
+              </important>
+            </para>
+            
+            &mccge-warning-end-cluster;
+            
           </listitem>
 
           <listitem>


Modified: trunk/refman-5.1/mysql-cluster-cge.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-cge.xml	2007-10-02 14:18:25 UTC (rev 7940)
+++ trunk/refman-5.1/mysql-cluster-cge.xml	2007-10-02 16:15:49 UTC (rev 7941)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 712 bytes

@@ -576,6 +576,15 @@
             </para>
           </listitem>
 
+          <listitem>
+            <para>
+              New values and behaviors are introduced for
+              <option>--ndb_optimized_node_selection</option> allowing
+              for greater flexibility when an SQL node chooses a
+              transaction coordinator. (MySQL 5.1.22-ndb-6.3.4)
+            </para>
+          </listitem>
+
         </itemizedlist>
       </para>
 


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-10-02 14:18:25 UTC (rev 7940)
+++ trunk/refman-5.1/news-5.1.xml	2007-10-02 16:15:49 UTC (rev 7941)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 0; 761 bytes

@@ -771,6 +771,17 @@
           </para>
         </listitem>
 
+        <listitem>
+          <para>
+            The <option>--ndb_optimized_node_selection</option> startup
+            option for <command>mysqld</command> now allows a wider
+            range of values and corresponding behaviors for SQL nodes
+            when selecting a transaction coordinator. See
+            <xref linkend="server-system-variables"/>, for more
+            information.
+          </para>
+        </listitem>
+
       </itemizedlist>
 
 <!--