List:Commits« Previous MessageNext Message »
From:jon.stephens Date:December 15 2010 10:47am
Subject:svn commit - mysqldoc@docsrva: r24449 - in trunk: dynamic-docs/command-optvars refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: jstephens
Date: 2010-12-15 11:47:10 +0100 (Wed, 15 Dec 2010)
New Revision: 24449

Log:

Fixes Docs BUG#58908

(as well as some related NDB config param issues noticed while fixing)



Modified:
   trunk/dynamic-docs/command-optvars/ndb-config-params.xml
   trunk/refman-4.1/mysql-cluster-configuration-core.xml
   trunk/refman-5.0/mysql-cluster-configuration-core.xml
   trunk/refman-5.1/mysql-cluster-configuration-core.xml


Modified: trunk/dynamic-docs/command-optvars/ndb-config-params.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/ndb-config-params.xml	2010-12-15 08:09:24 UTC (rev 24448)
+++ trunk/dynamic-docs/command-optvars/ndb-config-params.xml	2010-12-15 10:47:10 UTC (rev 24449)
Changed blocks: 1, Lines Added: 156, Lines Deleted: 0; 4202 bytes

@@ -1508,6 +1508,162 @@
 
   </mysqloption>
 
+  <mysqloption id="hostname1-tcp">
+
+    <xrefto id="ndbparam-tcp-hostname1"/>
+
+    <name>HostName1</name>
+
+    <shortdescription>
+      Name or IP address of the first of the two computers joined by a
+      TCP connection.
+    </shortdescription>
+
+    <values vartype="string" platform="all" inversion="4.1.3" units="name or IP address">
+      <value default="" minimum="" maximum=""/>
+    </values>
+
+    <versions>
+      <introduced version="4.1.3"/>
+      <manual version="4.1"/>
+      <manual version="5.0"/>
+      <manual version="5.1"/>
+    </versions>
+
+    <restart type="node" initial="no"/>
+
+  </mysqloption>
+
+  <mysqloption id="hostname2-tcp">
+
+    <xrefto id="ndbparam-tcp-hostname2"/>
+
+    <name>HostName1</name>
+
+    <shortdescription>
+      Name or IP address of the second of the two computers joined by a
+      TCP connection.
+    </shortdescription>
+
+    <values vartype="string" platform="all" inversion="4.1.3" units="name or IP address">
+      <value default="" minimum="" maximum=""/>
+    </values>
+
+    <versions>
+      <introduced version="4.1.3"/>
+      <manual version="4.1"/>
+      <manual version="5.0"/>
+      <manual version="5.1"/>
+    </versions>
+
+    <restart type="node" initial="no"/>
+
+  </mysqloption>
+
+  <mysqloption id="hostname1-sci">
+
+    <xrefto id="ndbparam-sci-hostname1"/>
+
+    <name>HostName1</name>
+
+    <shortdescription>
+      Name or IP address of the first of the two computers joined by an
+      SCI connection.
+    </shortdescription>
+
+    <values vartype="string" platform="all" inversion="4.1.3" units="name or IP address">
+      <value default="" minimum="" maximum=""/>
+    </values>
+
+    <versions>
+      <introduced version="4.1.3"/>
+      <manual version="4.1"/>
+      <manual version="5.0"/>
+      <manual version="5.1"/>
+    </versions>
+
+    <restart type="node" initial="no"/>
+
+  </mysqloption>
+
+  <mysqloption id="hostname2-sci">
+
+    <xrefto id="ndbparam-sci-hostname2"/>
+
+    <name>HostName1</name>
+
+    <shortdescription>
+      Name or IP address of the second of the two computers joined by an
+      SCI connection.
+    </shortdescription>
+
+    <values vartype="string" platform="all" inversion="4.1.3" units="name or IP address">
+      <value default="" minimum="" maximum=""/>
+    </values>
+
+    <versions>
+      <introduced version="4.1.3"/>
+      <manual version="4.1"/>
+      <manual version="5.0"/>
+      <manual version="5.1"/>
+    </versions>
+
+    <restart type="node" initial="no"/>
+
+  </mysqloption>
+
+  <mysqloption id="hostname1-shm">
+
+    <xrefto id="ndbparam-shm-hostname1"/>
+
+    <name>HostName1</name>
+
+    <shortdescription>
+      Name or IP address of the first of the two computers joined by an
+      SHM connection.
+    </shortdescription>
+
+    <values vartype="string" platform="all" inversion="4.1.3" units="name or IP address">
+      <value default="" minimum="" maximum=""/>
+    </values>
+
+    <versions>
+      <introduced version="4.1.3"/>
+      <manual version="4.1"/>
+      <manual version="5.0"/>
+      <manual version="5.1"/>
+    </versions>
+
+    <restart type="node" initial="no"/>
+
+  </mysqloption>
+
+  <mysqloption id="hostname2-shm">
+
+    <xrefto id="ndbparam-shm-hostname2"/>
+
+    <name>HostName1</name>
+
+    <shortdescription>
+      Name or IP address of the second of the two computers joined by an
+      SHM connection.
+    </shortdescription>
+
+    <values vartype="string" platform="all" inversion="4.1.3" units="name or IP address">
+      <value default="" minimum="" maximum=""/>
+    </values>
+
+    <versions>
+      <introduced version="4.1.3"/>
+      <manual version="4.1"/>
+      <manual version="5.0"/>
+      <manual version="5.1"/>
+    </versions>
+
+    <restart type="node" initial="no"/>
+
+  </mysqloption>
+
   <mysqloption id="indexmemory-ndbd" section="cluster" subsection="ndbd">
 
     <xrefto id="ndbparam-ndbd-indexmemory"/>


Modified: trunk/refman-4.1/mysql-cluster-configuration-core.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster-configuration-core.xml	2010-12-15 08:09:24 UTC (rev 24448)
+++ trunk/refman-4.1/mysql-cluster-configuration-core.xml	2010-12-15 10:47:10 UTC (rev 24449)
Changed blocks: 7, Lines Added: 133, Lines Deleted: 11; 6923 bytes

@@ -4397,10 +4397,26 @@
       <itemizedlist>
 
         <listitem>
-          <para id="ndbparam-tcp-nodeid">
-            <literal>NodeId1</literal>, <literal>NodeId2</literal>
+          <indexterm>
+            <primary>NodeId1</primary>
+          </indexterm>
+
+          <para id="ndbparam-tcp-nodeid1">
+            <literal>NodeId1</literal>
           </para>
 
+          <para condition="dynamic:optvar:item" role="4.1:ndb-config-params:nodeid1-tcp"/>
+
+          <indexterm>
+            <primary>NodeId2</primary>
+          </indexterm>
+
+          <para id="ndbparam-tcp-nodeid2">
+            <literal>NodeId2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="4.1:ndb-config-params:nodeid2-tcp"/>
+
           <para>
             To identify a connection between two nodes it is necessary
             to provide their node IDs in the <literal>[tcp]</literal>

@@ -4412,6 +4428,36 @@
 
         <listitem>
           <indexterm>
+            <primary>HostName1</primary>
+          </indexterm>
+
+          <para id="ndbparam-tcp-hostname1">
+            <literal>HostName1</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="4.1:ndb-config-params:hostname1-tcp"/>
+
+          <indexterm>
+            <primary>HostName2</primary>
+          </indexterm>
+
+          <para id="ndbparam-tcp-hostname2">
+            <literal>HostName2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="4.1:ndb-config-params:hostname2-tcp"/>
+
+          <para>
+            The <literal>HostName1</literal> and
+            <literal>HostName2</literal> parameters can be used to
+            specify specific network interfaces to be used for a given
+            TCP connection between two nodes. The values used for these
+            parameters can be hostnames or IP addresses.
+          </para>
+        </listitem>
+
+        <listitem>
+          <indexterm>
             <primary>SendBufferMemory</primary>
           </indexterm>
 

@@ -4594,14 +4640,14 @@
 </programlisting>
 
       <para>
-        The <literal>HostName<replaceable>N</replaceable></literal>
-        parameter, where <replaceable>N</replaceable> is an integer, is
-        used only when specifying direct TCP/IP connections.
+        The <literal role="ndbparam:tcp">HostName1</literal> and
+        <literal role="ndbparam:tcp">HostName2</literal> parameters are
+        used only when specifying direct connections.
       </para>
 
       <para>
-        The use of direct connections between data nodes can improve the
-        cluster's overall efficiency by enabling the data nodes to
+        The use of direct TCP connections between data nodes can improve
+        the cluster's overall efficiency by enabling the data nodes to
         bypass an Ethernet device such as a switch, hub, or router, thus
         cutting down on the cluster's latency. It is important to note
         that to take the best advantage of direct connections in this

@@ -4681,10 +4727,18 @@
             <secondary>node identifiers</secondary>
           </indexterm>
 
-          <para id="ndbparam-shm-nodeids">
-            <literal>NodeId1</literal>, <literal>NodeId2</literal>
+          <para id="ndbparam-shm-nodeid1">
+            <literal>NodeId1</literal>
           </para>
 
+          <para condition="dynamic:optvar:item" role="4.1:ndb-config-params:nodeid1-shm"/>
+
+          <para id="ndbparam-shm-nodeid2">
+            <literal>NodeId2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="4.1:ndb-config-params:nodeid2-shm"/>
+
           <para>
             To identify a connection between two nodes it is necessary
             to provide node identifiers for each of them, as

@@ -4694,6 +4748,36 @@
 
         <listitem>
           <indexterm>
+            <primary>HostName1</primary>
+          </indexterm>
+
+          <para id="ndbparam-shm-hostname2">
+            <literal>HostName1</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="4.1:ndb-config-params:hostname1-shm"/>
+
+          <indexterm>
+            <primary>HostName2</primary>
+          </indexterm>
+
+          <para>
+            <literal>HostName2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="4.1:ndb-config-params:hostname2-shm"/>
+
+          <para>
+            The <literal>HostName1</literal> and
+            <literal>HostName2</literal> parameters can be used to
+            specify specific network interfaces to be used for a given
+            SHM connection between two nodes. The values used for these
+            parameters can be hostnames or IP addresses.
+          </para>
+        </listitem>
+
+        <listitem>
+          <indexterm>
             <primary>ShmKey</primary>
           </indexterm>
 

@@ -4880,10 +4964,18 @@
             <secondary>node identifiers</secondary>
           </indexterm>
 
-          <para id="ndbparam-sci-nodeids">
-            <literal>NodeId1</literal>, <literal>NodeId2</literal>
+          <para id="ndbparam-sci-nodeid1">
+            <literal>NodeId1</literal>
           </para>
 
+          <para condition="dynamic:optvar:item" role="4.1:ndb-config-params:nodeid1-sci"/>
+
+          <para id="ndbparam-sci-nodeid2">
+            <literal>NodeId2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="4.1:ndb-config-params:nodeid2-sci"/>
+
           <para>
             To identify a connection between two nodes it is necessary
             to provide node identifiers for each of them, as

@@ -4952,6 +5044,36 @@
 
         <listitem>
           <indexterm>
+            <primary>HostName1</primary>
+          </indexterm>
+
+          <para id="ndbparam-sci-hostname1">
+            <literal>HostName1</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="4.1:ndb-config-params:hostname1-sci"/>
+
+          <indexterm>
+            <primary>HostName2</primary>
+          </indexterm>
+
+          <para id="ndbparam-sci-hostname2">
+            <literal>HostName2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="4.1:ndb-config-params:hostname2-sci"/>
+
+          <para>
+            The <literal>HostName1</literal> and
+            <literal>HostName2</literal> parameters can be used to
+            specify specific network interfaces to be used for a given
+            SCI connection between two nodes. The values used for these
+            parameters can be hostnames or IP addresses.
+          </para>
+        </listitem>
+
+        <listitem>
+          <indexterm>
             <primary>SharedBufferSize</primary>
           </indexterm>
 


Modified: trunk/refman-5.0/mysql-cluster-configuration-core.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster-configuration-core.xml	2010-12-15 08:09:24 UTC (rev 24448)
+++ trunk/refman-5.0/mysql-cluster-configuration-core.xml	2010-12-15 10:47:10 UTC (rev 24449)
Changed blocks: 7, Lines Added: 133, Lines Deleted: 11; 6955 bytes

@@ -4480,10 +4480,26 @@
       <itemizedlist>
 
         <listitem>
-          <para id="ndbparam-tcp-nodeid">
-            <literal>NodeId1</literal>, <literal>NodeId2</literal>
+          <indexterm>
+            <primary>NodeId1</primary>
+          </indexterm>
+
+          <para id="ndbparam-tcp-nodeid1">
+            <literal>NodeId1</literal>
           </para>
 
+          <para condition="dynamic:optvar:item" role="5.0:ndb-config-params:nodeid1-tcp"/>
+
+          <indexterm>
+            <primary>NodeId2</primary>
+          </indexterm>
+
+          <para id="ndbparam-tcp-nodeid2">
+            <literal>NodeId2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.0:ndb-config-params:nodeid2-tcp"/>
+
           <para>
             To identify a connection between two nodes it is necessary
             to provide their node IDs in the <literal>[tcp]</literal>

@@ -4495,6 +4511,36 @@
 
         <listitem>
           <indexterm>
+            <primary>HostName1</primary>
+          </indexterm>
+
+          <para id="ndbparam-tcp-hostname1">
+            <literal>HostName1</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.0:ndb-config-params:hostname1-tcp"/>
+
+          <indexterm>
+            <primary>HostName2</primary>
+          </indexterm>
+
+          <para id="ndbparam-tcp-hostname2">
+            <literal>HostName2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.0:ndb-config-params:hostname2-tcp"/>
+
+          <para>
+            The <literal>HostName1</literal> and
+            <literal>HostName2</literal> parameters can be used to
+            specify specific network interfaces to be used for a given
+            TCP connection between two nodes. The values used for these
+            parameters can be hostnames or IP addresses.
+          </para>
+        </listitem>
+
+        <listitem>
+          <indexterm>
             <primary>SendBufferMemory</primary>
           </indexterm>
 

@@ -4677,14 +4723,14 @@
 </programlisting>
 
       <para>
-        The <literal>HostName<replaceable>N</replaceable></literal>
-        parameter, where <replaceable>N</replaceable> is an integer, is
-        used only when specifying direct TCP/IP connections.
+        The <literal role="ndbparam:tcp">HostName1</literal> and
+        <literal role="ndbparam:tcp">HostName2</literal> parameters are
+        used only when specifying direct TCP connections.
       </para>
 
       <para>
-        The use of direct connections between data nodes can improve the
-        cluster's overall efficiency by enabling the data nodes to
+        The use of direct TCP connections between data nodes can improve
+        the cluster's overall efficiency by enabling the data nodes to
         bypass an Ethernet device such as a switch, hub, or router, thus
         cutting down on the cluster's latency. It is important to note
         that to take the best advantage of direct connections in this

@@ -4763,10 +4809,18 @@
             <secondary>node identifiers</secondary>
           </indexterm>
 
-          <para id="ndbparam-shm-nodeids">
-            <literal>NodeId1</literal>, <literal>NodeId2</literal>
+          <para id="ndbparam-shm-nodeid1">
+            <literal>NodeId1</literal>
           </para>
 
+          <para condition="dynamic:optvar:item" role="5.0:ndb-config-params:nodeid1-shm"/>
+
+          <para id="ndbparam-shm-nodeid2">
+            <literal>NodeId2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.0:ndb-config-params:nodeid2-shm"/>
+
           <para>
             To identify a connection between two nodes it is necessary
             to provide node identifiers for each of them, as

@@ -4776,6 +4830,36 @@
 
         <listitem>
           <indexterm>
+            <primary>HostName1</primary>
+          </indexterm>
+
+          <para id="ndbparam-shm-hostname1">
+            <literal>HostName1</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.0:ndb-config-params:hostname1-shm"/>
+
+          <indexterm>
+            <primary>HostName2</primary>
+          </indexterm>
+
+          <para id="ndbparam-shm-hostname2">
+            <literal>HostName2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.0:ndb-config-params:hostname2-shm"/>
+
+          <para>
+            The <literal>HostName1</literal> and
+            <literal>HostName2</literal> parameters can be used to
+            specify specific network interfaces to be used for a given
+            SHM connection between two nodes. The values used for these
+            parameters can be hostnames or IP addresses.
+          </para>
+        </listitem>
+
+        <listitem>
+          <indexterm>
             <primary>ShmKey</primary>
           </indexterm>
 

@@ -4962,10 +5046,18 @@
             <secondary>node identifiers</secondary>
           </indexterm>
 
-          <para id="ndbparam-sci-nodeids">
-            <literal>NodeId1</literal>, <literal>NodeId2</literal>
+          <para id="ndbparam-sci-nodeid1">
+            <literal>NodeId1</literal>
           </para>
 
+          <para condition="dynamic:optvar:item" role="5.0:ndb-config-params:nodeid1-sci"/>
+
+          <para id="ndbparam-sci-nodeid2">
+            <literal>NodeId2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.0:ndb-config-params:nodeid2-sci"/>
+
           <para>
             To identify a connection between two nodes it is necessary
             to provide node identifiers for each of them, as

@@ -5034,6 +5126,36 @@
 
         <listitem>
           <indexterm>
+            <primary>HostName1</primary>
+          </indexterm>
+
+          <para id="ndbparam-sci-hostname1">
+            <literal>HostName1</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.0:ndb-config-params:hostname1-sci"/>
+
+          <indexterm>
+            <primary>HostName2</primary>
+          </indexterm>
+
+          <para id="ndbparam-sci-hostname2">
+            <literal>HostName2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.0:ndb-config-params:hostname2-sci"/>
+
+          <para>
+            The <literal>HostName1</literal> and
+            <literal>HostName2</literal> parameters can be used to
+            specify specific network interfaces to be used for a given
+            SCI connection between two nodes. The values used for these
+            parameters can be hostnames or IP addresses.
+          </para>
+        </listitem>
+
+        <listitem>
+          <indexterm>
             <primary>SharedBufferSize</primary>
           </indexterm>
 


Modified: trunk/refman-5.1/mysql-cluster-configuration-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-configuration-core.xml	2010-12-15 08:09:24 UTC (rev 24448)
+++ trunk/refman-5.1/mysql-cluster-configuration-core.xml	2010-12-15 10:47:10 UTC (rev 24449)
Changed blocks: 9, Lines Added: 115, Lines Deleted: 18; 7025 bytes

@@ -7750,27 +7750,26 @@
       <itemizedlist>
 
         <listitem>
+          <indexterm>
+            <primary>NodeId1</primary>
+          </indexterm>
+
           <para id="ndbparam-tcp-nodeid1">
-            <indexterm>
-              <primary>NodeId1</primary>
-            </indexterm>
-
-            <indexterm>
-              <primary>MySQL Cluster</primary>
-              <secondary>node identifiers</secondary>
-            </indexterm>
-
             <literal>NodeId1</literal>
           </para>
 
+          <para condition="dynamic:optvar:item" role="5.1:ndb-config-params:nodeid1-tcp"/>
+
+          <indexterm>
+            <primary>NodeId2</primary>
+          </indexterm>
+
           <para id="ndbparam-tcp-nodeid2">
-            <indexterm>
-              <primary>NodeId1</primary>
-            </indexterm>
-
             <literal>NodeId2</literal>
           </para>
 
+          <para condition="dynamic:optvar:item" role="5.1:ndb-config-params:nodeid2-tcp"/>
+
           <para>
             To identify a connection between two nodes it is necessary
             to provide their node IDs in the <literal>[tcp]</literal>

@@ -7781,6 +7780,36 @@
         </listitem>
 
         <listitem>
+          <indexterm>
+            <primary>HostName1</primary>
+          </indexterm>
+
+          <para id="ndbparam-tcp-hostname1">
+            <literal>HostName1</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.1:ndb-config-params:hostname1-tcp"/>
+
+          <indexterm>
+            <primary>HostName2</primary>
+          </indexterm>
+
+          <para id="ndbparam-tcp-hostname2">
+            <literal>HostName2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.1:ndb-config-params:hostname2-tcp"/>
+
+          <para>
+            The <literal>HostName1</literal> and
+            <literal>HostName2</literal> parameters can be used to
+            specify specific network interfaces to be used for a given
+            TCP connection between two nodes. The values used for these
+            parameters can be hostnames or IP addresses.
+          </para>
+        </listitem>
+
+        <listitem>
           <para id="ndbparam-tcp-overloadlimit">
             <indexterm>
               <primary>OverloadLimit</primary>

@@ -7999,14 +8028,14 @@
 </programlisting>
 
       <para>
-        The <literal>HostName<replaceable>N</replaceable></literal>
-        parameter, where <replaceable>N</replaceable> is an integer, is
-        used only when specifying direct TCP/IP connections.
+        The <literal role="ndbparam:tcp">HostName1</literal> and
+        <literal role="ndbparam:tcp">HostName2</literal> parameters are
+        used only when specifying direct connections.
       </para>
 
       <para>
-        The use of direct connections between data nodes can improve the
-        cluster's overall efficiency by enabling the data nodes to
+        The use of direct TCP connections between data nodes can improve
+        the cluster's overall efficiency by enabling the data nodes to
         bypass an Ethernet device such as a switch, hub, or router, thus
         cutting down on the cluster's latency. It is important to note
         that to take the best advantage of direct connections in this

@@ -8089,6 +8118,8 @@
             <literal>NodeId1</literal>
           </para>
 
+          <para condition="dynamic:optvar:item" role="5.1:ndb-config-params:nodeid1-shm"/>
+
           <para id="ndbparam-shm-nodeid2">
             <indexterm>
               <primary>NodeId2</primary>

@@ -8102,6 +8133,8 @@
             <literal>NodeId2</literal>
           </para>
 
+          <para condition="dynamic:optvar:item" role="5.1:ndb-config-params:nodeid2-shm"/>
+
           <para>
             To identify a connection between two nodes it is necessary
             to provide node identifiers for each of them, as

@@ -8110,6 +8143,36 @@
         </listitem>
 
         <listitem>
+          <indexterm>
+            <primary>HostName1</primary>
+          </indexterm>
+
+          <para id="ndbparam-shm-hostname1">
+            <literal>HostName1</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.1:ndb-config-params:hostname1-shm"/>
+
+          <indexterm>
+            <primary>HostName2</primary>
+          </indexterm>
+
+          <para id="ndbparam-shm-hostname2">
+            <literal>HostName2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.1:ndb-config-params:hostname2-shm"/>
+
+          <para>
+            The <literal>HostName1</literal> and
+            <literal>HostName2</literal> parameters can be used to
+            specify specific network interfaces to be used for a given
+            SHM connection between two nodes. The values used for these
+            parameters can be hostnames or IP addresses.
+          </para>
+        </listitem>
+
+        <listitem>
           <para id="ndbparam-shm-shmkey">
             <indexterm>
               <primary>ShmKey</primary>

@@ -8303,6 +8366,8 @@
             <literal>NodeId1</literal>
           </para>
 
+          <para condition="dynamic:optvar:item" role="5.1:ndb-config-params:nodeid1-sci"/>
+
           <para id="ndbparam-sci-nodeid2">
             <indexterm>
               <primary>NodeId2</primary>

@@ -8316,6 +8381,8 @@
             <literal>NodeId2</literal>
           </para>
 
+          <para condition="dynamic:optvar:item" role="5.1:ndb-config-params:nodeid2-sci"/>
+
           <para>
             To identify a connection between two nodes it is necessary
             to provide node identifiers for each of them, as

@@ -8385,6 +8452,36 @@
         </listitem>
 
         <listitem>
+          <indexterm>
+            <primary>HostName1</primary>
+          </indexterm>
+
+          <para id="ndbparam-sci-hostname1">
+            <literal>HostName1</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.1:ndb-config-params:hostname1-sci"/>
+
+          <indexterm>
+            <primary>HostName2</primary>
+          </indexterm>
+
+          <para id="ndbparam-sci-hostname2">
+            <literal>HostName2</literal>
+          </para>
+
+          <para condition="dynamic:optvar:item" role="5.1:ndb-config-params:hostname2-sci"/>
+
+          <para>
+            The <literal>HostName1</literal> and
+            <literal>HostName2</literal> parameters can be used to
+            specify specific network interfaces to be used for a given
+            SCI connection between two nodes. The values used for these
+            parameters can be hostnames or IP addresses.
+          </para>
+        </listitem>
+
+        <listitem>
           <para id="ndbparam-sci-sharedbuffersize">
             <indexterm>
               <primary>SharedBufferSize</primary>


Thread
svn commit - mysqldoc@docsrva: r24449 - in trunk: dynamic-docs/command-optvars refman-4.1 refman-5.0 refman-5.1jon.stephens15 Dec