<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h4 class="title">
      <a name="mysql-cluster-tcp-definition">
      </a>
      25.4.3.10 NDB Cluster TCP/IP Connections
     </h4>
    </div>
   </div>
  </div>
  <p>
   TCP/IP is the default transport mechanism for all connections
        between nodes in an NDB Cluster. Normally it is not necessary to
        define TCP/IP connections; NDB Cluster automatically sets up
        such connections for all data nodes, management nodes, and SQL
        or API nodes.
  </p>
  <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
   <div class="admon-title">
    Note
   </div>
   <p>
    For an exception to this rule, see
    <a class="xref" href="mysql-cluster-tcp-definition-direct.html" title="25.4.3.11 NDB Cluster TCP/IP Connections Using Direct Connections">
     Section 25.4.3.11, “NDB Cluster TCP/IP Connections Using Direct Connections”
    </a>
    .
   </p>
  </div>
  <p>
   To override the default connection parameters, it is necessary
        to define a connection using one or more
   <code class="literal">
    [tcp]
   </code>
   sections in the
   <code class="filename">
    config.ini
   </code>
   file. Each
   <code class="literal">
    [tcp]
   </code>
   section explicitly defines a TCP/IP
        connection between two NDB Cluster nodes, and must contain at a
        minimum the parameters
   <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-nodeid1">
    <code class="literal">
     NodeId1
    </code>
   </a>
   and
   <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-nodeid2">
    <code class="literal">
     NodeId2
    </code>
   </a>
   , as well as any
        connection parameters to override.
  </p>
  <p>
   It is also possible to change the default values for these
        parameters by setting them in the
   <code class="literal">
    [tcp
        default]
   </code>
   section.
  </p>
  <div class="important" style="margin-left: 0.5in; margin-right: 0.5in;">
   <div class="admon-title">
    Important
   </div>
   <p>
    Any
    <code class="literal">
     [tcp]
    </code>
    sections in the
    <code class="filename">
     config.ini
    </code>
    file should be listed
    <span class="emphasis">
     <em>
      last
     </em>
    </span>
    , following all other sections in the
          file. However, this is not required for a
    <code class="literal">
     [tcp
          default]
    </code>
    section. This requirement is a known issue
          with the way in which the
    <code class="filename">
     config.ini
    </code>
    file
          is read by the NDB Cluster management server.
   </p>
  </div>
  <p>
   Connection parameters which can be set in
   <code class="literal">
    [tcp]
   </code>
   and
   <code class="literal">
    [tcp default]
   </code>
   sections of the
   <code class="filename">
    config.ini
   </code>
   file are listed
        here:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-allowunresolvedhostnames">
      </a>
      <code class="literal">
       AllowUnresolvedHostNames
      </code>
     </p>
     <a class="indexterm" name="idm46045109570832">
     </a>
     <div class="informaltable">
      <a name="allowunresolvedhostnames-tcp-table">
      </a>
      <table frame="box" rules="all" summary="AllowUnresolvedHostNames TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          boolean
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          false
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          true, false
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      By default, when a management node fails to resolve a host
            name while trying to connect, this results in a fatal error.
            This behavior can be overridden by setting
      <code class="literal">
       AllowUnresolvedHostNames
      </code>
      to
      <code class="literal">
       true
      </code>
      in the
      <code class="literal">
       [tcp
            default]
      </code>
      section of the global configuration file
            (usually named
      <code class="filename">
       config.ini
      </code>
      ), in which
            case failure to resolve a host name is treated as a warning
            and
      <a class="link" href="mysql-cluster-programs-ndb-mgmd.html" title="25.5.4 ndb_mgmd — The NDB Cluster Management Server Daemon">
       <span class="command">
        <strong>
         ndb_mgmd
        </strong>
       </span>
      </a>
      startup continues
            uninterrupted.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-checksum">
      </a>
      <code class="literal">
       Checksum
      </code>
     </p>
     <a class="indexterm" name="idm46045109546400">
     </a>
     <div class="informaltable">
      <a name="checksum-tcp-table">
      </a>
      <table frame="box" rules="all" summary="Checksum TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          boolean
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          false
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          true, false
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      This parameter is disabled by default. When it is enabled
            (set to
      <code class="literal">
       Y
      </code>
      or
      <code class="literal">
       1
      </code>
      ),
            checksums for all messages are calculated before they placed
            in the send buffer. This feature ensures that messages are
            not corrupted while waiting in the send buffer, or by the
            transport mechanism.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-group">
      </a>
      <code class="literal">
       Group
      </code>
     </p>
     <p>
      When
      <a class="link" href="mysql-cluster-options-variables.html#sysvar_ndb_optimized_node_selection">
       <code class="literal">
        ndb_optimized_node_selection
       </code>
      </a>
      is enabled, node proximity is used in some cases to select
            which node to connect to. This parameter can be used to
            influence proximity by setting it to a lower value, which is
            interpreted as
      <span class="quote">
       “
       <span class="quote">
        closer
       </span>
       ”
      </span>
      . See the description of
            the system variable for more information.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-hostname1">
      </a>
      <code class="literal">
       HostName1
      </code>
     </p>
     <a class="indexterm" name="idm46045109520624">
     </a>
     <div class="informaltable">
      <a name="hostname1-tcp-table">
      </a>
      <table frame="box" rules="all" summary="HostName1 TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          name or IP address
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          [...]
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          ...
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      The
      <code class="literal">
       HostName1
      </code>
      and
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-hostname2">
       <code class="literal">
        HostName2
       </code>
      </a>
      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 host names or IP
            addresses.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-hostname2">
      </a>
      <code class="literal">
       HostName2
      </code>
     </p>
     <a class="indexterm" name="idm46045109498688">
     </a>
     <div class="informaltable">
      <a name="hostname2-tcp-table">
      </a>
      <table frame="box" rules="all" summary="HostName2 TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          name or IP address
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          [...]
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          ...
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      The
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-hostname1">
       <code class="literal">
        HostName1
       </code>
      </a>
      and
      <code class="literal">
       HostName2
      </code>
      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 host names or IP addresses.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-nodeid1">
      </a>
      <code class="literal">
       NodeId1
      </code>
     </p>
     <a class="indexterm" name="idm46045109476768">
     </a>
     <div class="informaltable">
      <a name="nodeid1-tcp-table">
      </a>
      <table frame="box" rules="all" summary="NodeId1 TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          numeric
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          [none]
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          1 - 255
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      To identify a connection between two nodes it is necessary
            to provide their node IDs in the
      <code class="literal">
       [tcp]
      </code>
      section of the configuration file as the values of
      <code class="literal">
       NodeId1
      </code>
      and
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-nodeid2">
       <code class="literal">
        NodeId2
       </code>
      </a>
      . These are
            the same unique
      <code class="literal">
       Id
      </code>
      values for each of
            these nodes as described in
      <a class="xref" href="mysql-cluster-api-definition.html" title="25.4.3.7 Defining SQL and Other API Nodes in an NDB Cluster">
       Section 25.4.3.7, “Defining SQL and Other API Nodes in an NDB Cluster”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-nodeid2">
      </a>
      <code class="literal">
       NodeId2
      </code>
     </p>
     <a class="indexterm" name="idm46045109452624">
     </a>
     <div class="informaltable">
      <a name="nodeid2-tcp-table">
      </a>
      <table frame="box" rules="all" summary="NodeId2 TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          numeric
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          [none]
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          1 - 255
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      To identify a connection between two nodes it is necessary
            to provide their node IDs in the
      <code class="literal">
       [tcp]
      </code>
      section of the configuration file as the values of
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-nodeid1">
       <code class="literal">
        NodeId1
       </code>
      </a>
      and
      <code class="literal">
       NodeId2
      </code>
      . These are the same unique
      <code class="literal">
       Id
      </code>
      values for each of these nodes as
            described in
      <a class="xref" href="mysql-cluster-api-definition.html" title="25.4.3.7 Defining SQL and Other API Nodes in an NDB Cluster">
       Section 25.4.3.7, “Defining SQL and Other API Nodes in an NDB Cluster”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-nodeidserver">
      </a>
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-nodeidserver">
       <code class="literal">
        NodeIdServer
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045109427968">
     </a>
     <a class="indexterm" name="idm46045109426896">
     </a>
     <div class="informaltable">
      <a name="nodeidserver-tcp-table">
      </a>
      <table frame="box" rules="all" summary="NodeIdServer TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          numeric
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          [none]
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          1 - 63
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Set the server side of a TCP connection.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-overloadlimit">
      </a>
      <code class="literal">
       OverloadLimit
      </code>
     </p>
     <a class="indexterm" name="idm46045109406624">
     </a>
     <div class="informaltable">
      <a name="overloadlimit-tcp-table">
      </a>
      <table frame="box" rules="all" summary="OverloadLimit TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          bytes
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          0
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          0 - 4294967039 (0xFFFFFEFF)
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      When more than this many unsent bytes are in the send
            buffer, the connection is considered overloaded.
     </p>
     <p>
      This parameter can be used to determine the amount of unsent
            data that must be present in the send buffer before the
            connection is considered overloaded. See
      <a class="xref" href="mysql-cluster-config-send-buffers.html" title="25.4.3.14 Configuring NDB Cluster Send Buffer Parameters">
       Section 25.4.3.14, “Configuring NDB Cluster Send Buffer Parameters”
      </a>
      , for
            more information.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-preferipversion">
      </a>
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-preferipversion">
       <code class="literal">
        PreferIPVersion
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045109384880">
     </a>
     <div class="informaltable">
      <a name="preferipversion-tcp-table">
      </a>
      <table frame="box" rules="all" summary="PreferIPVersion TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          enumeration
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          4
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          4, 6
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Initial System Restart:
            </strong>
           </span>
           Requires a complete shutdown of the
                    cluster, wiping and restoring the cluster file
                    system from a
           <a class="link" href="mysql-cluster-backup.html" title="25.6.8 Online Backup of NDB Cluster">
            backup
           </a>
           ,
                    and then restarting the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Determines the preference of DNS resolution for IP version 4
            or version 6. Because the configuration retrieval mechanism
            employed by NDB Cluster requires that all connections use
            the same preference, this parameter should be set in the
      <code class="literal">
       [tcp default]
      </code>
      of the
      <code class="filename">
       config.ini
      </code>
      global configuration file.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-presendchecksum">
      </a>
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-presendchecksum">
       <code class="literal">
        PreSendChecksum
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045109362656">
     </a>
     <div class="informaltable">
      <a name="presendchecksum-tcp-table">
      </a>
      <table frame="box" rules="all" summary="PreSendChecksum TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          boolean
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          false
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          true, false
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      If this parameter and
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-checksum">
       <code class="literal">
        Checksum
       </code>
      </a>
      are both
            enabled, perform pre-send checksum checks, and check all TCP
            signals between nodes for errors. Has no effect if
      <code class="literal">
       Checksum
      </code>
      is not also enabled.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-proxy">
      </a>
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-proxy">
       <code class="literal">
        Proxy
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045109340304">
     </a>
     <a class="indexterm" name="idm46045109339232">
     </a>
     <div class="informaltable">
      <a name="proxy-tcp-table">
      </a>
      <table frame="box" rules="all" summary="Proxy TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          string
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          [...]
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          ...
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Set a proxy for the TCP connection.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-receivebuffermemory">
      </a>
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-receivebuffermemory">
       <code class="literal">
        ReceiveBufferMemory
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045109318400">
     </a>
     <div class="informaltable">
      <a name="receivebuffermemory-tcp-table">
      </a>
      <table frame="box" rules="all" summary="ReceiveBufferMemory TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          bytes
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          2M
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          16K - 4294967039 (0xFFFFFEFF)
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Specifies the size of the buffer used when receiving data
            from the TCP/IP socket.
     </p>
     <p>
      The default value of this parameter is 2MB. The minimum
            possible value is 16KB; the theoretical maximum is 4GB.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-requirelinktls">
      </a>
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-requirelinktls">
       <code class="literal">
        RequireLinkTls
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045109297376">
     </a>
     <div class="informaltable">
      <a name="requirelinktls-tcp-table">
      </a>
      <table frame="box" rules="all" summary="RequireLinkTls TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          boolean
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          false
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          ...
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      If the node at either endpoint of this TCP connection
            requires TLS authentication, the value of this parameter is
      <code class="literal">
       true
      </code>
      , otherwise
      <code class="literal">
       false
      </code>
      .
            The value is set by
      <code class="literal">
       NDB
      </code>
      , and cannot be
            changed by the user.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-sendbuffermemory">
      </a>
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-sendbuffermemory">
       <code class="literal">
        SendBufferMemory
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045109274704">
     </a>
     <div class="informaltable">
      <a name="sendbuffermemory-tcp-table">
      </a>
      <table frame="box" rules="all" summary="SendBufferMemory TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          unsigned
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          2M
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          256K - 4294967039 (0xFFFFFEFF)
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      TCP transporters use a buffer to store all messages before
            performing the send call to the operating system. When this
            buffer reaches 64KB its contents are sent; these are also
            sent when a round of messages have been executed. To handle
            temporary overload situations it is also possible to define
            a bigger send buffer.
     </p>
     <p>
      If this parameter is set explicitly, then the memory is not
            dedicated to each transporter; instead, the value used
            denotes the hard limit for how much memory (out of the total
            available memory—that is,
      <code class="literal">
       TotalSendBufferMemory
      </code>
      ) that may be used
            by a single transporter. For more information about
            configuring dynamic transporter send buffer memory
            allocation in NDB Cluster, see
      <a class="xref" href="mysql-cluster-config-send-buffers.html" title="25.4.3.14 Configuring NDB Cluster Send Buffer Parameters">
       Section 25.4.3.14, “Configuring NDB Cluster Send Buffer Parameters”
      </a>
      .
     </p>
     <p>
      The default size of the send buffer is 2MB, which is the
            size recommended in most situations. The minimum size is 64
            KB; the theoretical maximum is 4 GB.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-sendsignalid">
      </a>
      <code class="literal">
       SendSignalId
      </code>
     </p>
     <a class="indexterm" name="idm46045109251344">
     </a>
     <div class="informaltable">
      <a name="sendsignalid-tcp-table">
      </a>
      <table frame="box" rules="all" summary="SendSignalId TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          boolean
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          false (debug builds: true)
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          true, false
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      To be able to retrace a distributed message datagram, it is
            necessary to identify each message. When this parameter is
            set to
      <code class="literal">
       Y
      </code>
      , message IDs are transported
            over the network. This feature is disabled by default in
            production builds, and enabled in
      <code class="literal">
       -debug
      </code>
      builds.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-tcpbind_inaddr_any">
      </a>
      <code class="literal">
       TcpBind_INADDR_ANY
      </code>
     </p>
     <p>
      Setting this parameter to
      <code class="literal">
       TRUE
      </code>
      or
      <code class="literal">
       1
      </code>
      binds
      <code class="literal">
       IP_ADDR_ANY
      </code>
      so
            that connections can be made from anywhere (for
            autogenerated connections). The default is
      <code class="literal">
       FALSE
      </code>
      (
      <code class="literal">
       0
      </code>
      ).
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-tcpspintime">
      </a>
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-tcpspintime">
       <code class="literal">
        TcpSpinTime
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045109223312">
     </a>
     <div class="informaltable">
      <a name="tcpspintime-tcp-table">
      </a>
      <table frame="box" rules="all" summary="TcpSpinTime TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          µsec
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          0
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          0 - 2000
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Controls spin for a TCP transporter; no enable, set to a
            nonzero value. This works for both the data node and
            management or SQL node side of the connection.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-tcp_maxseg_size">
      </a>
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-tcp_maxseg_size">
       <code class="literal">
        TCP_MAXSEG_SIZE
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045109202864">
     </a>
     <div class="informaltable">
      <a name="tcp_maxseg_size-tcp-table">
      </a>
      <table frame="box" rules="all" summary="TCP_MAXSEG_SIZE TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          unsigned
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          0
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          0 - 2G
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Determines the size of the memory set during TCP transporter
            initialization. The default is recommended for most common
            usage cases.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-tcp_rcv_buf_size">
      </a>
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-tcp_rcv_buf_size">
       <code class="literal">
        TCP_RCV_BUF_SIZE
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045109182352">
     </a>
     <div class="informaltable">
      <a name="tcp_rcv_buf_size-tcp-table">
      </a>
      <table frame="box" rules="all" summary="TCP_RCV_BUF_SIZE TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          unsigned
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          0
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          0 - 2G
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Determines the size of the receive buffer set during TCP
            transporter initialization. The default and minimum value is
            0, which allows the operating system or platform to set this
            value. The default is recommended for most common usage
            cases.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="ndbparam-tcp-tcp_snd_buf_size">
      </a>
      <a class="link" href="mysql-cluster-tcp-definition.html#ndbparam-tcp-tcp_snd_buf_size">
       <code class="literal">
        TCP_SND_BUF_SIZE
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045109161760">
     </a>
     <div class="informaltable">
      <a name="tcp_snd_buf_size-tcp-table">
      </a>
      <table frame="box" rules="all" summary="TCP_SND_BUF_SIZE TCP configuration parameter type and value information" width="35%">
       <colgroup>
        <col style="width: 50%"/>
        <col style="width: 50%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Version (or later)
         </th>
         <td>
          NDB 8.4.0
         </td>
        </tr>
        <tr>
         <th>
          Type or units
         </th>
         <td>
          unsigned
         </td>
        </tr>
        <tr>
         <th>
          Default
         </th>
         <td>
          0
         </td>
        </tr>
        <tr>
         <th>
          Range
         </th>
         <td>
          0 - 2G
         </td>
        </tr>
        <tr>
         <th>
          Restart Type
         </th>
         <td>
          <p>
           <span class="bold">
            <strong>
             Node Restart:
            </strong>
           </span>
           Requires a
           <a class="link" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
            rolling
                    restart
           </a>
           of the cluster. (NDB 8.4.0)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Determines the size of the send buffer set during TCP
            transporter initialization. The default and minimum value is
            0, which allows the operating system or platform to set this
            value. The default is recommended for most common usage
            cases.
     </p>
    </li>
   </ul>
  </div>
  <p>
   <a name="mysql-cluster-tcp-definition-restart-types">
   </a>
   <b>
    Restart types.
   </b>
   Information about the restart types used by the parameter
          descriptions in this section is shown in the following table:
  </p>
  <div class="table">
   <a name="idm46045109141424">
   </a>
   <p class="title">
    <b>
     Table 25.20 NDB Cluster restart types
    </b>
   </p>
   <div class="table-contents">
    <table>
     <colgroup>
      <col style="width: 10%"/>
      <col style="width: 30%"/>
      <col style="width: 60%"/>
     </colgroup>
     <thead>
      <tr>
       <th scope="col">
        Symbol
       </th>
       <th scope="col">
        Restart Type
       </th>
       <th scope="col">
        Description
       </th>
      </tr>
     </thead>
     <tbody>
      <tr>
       <th scope="row">
        N
       </th>
       <td>
        Node
       </td>
       <td>
        The parameter can be updated using a rolling restart (see
        <a class="xref" href="mysql-cluster-rolling-restart.html" title="25.6.5 Performing a Rolling Restart of an NDB Cluster">
         Section 25.6.5, “Performing a Rolling Restart of an NDB Cluster”
        </a>
        )
       </td>
      </tr>
      <tr>
       <th scope="row">
        S
       </th>
       <td>
        System
       </td>
       <td>
        All cluster nodes must be shut down completely, then restarted, to
              effect a change in this parameter
       </td>
      </tr>
      <tr>
       <th scope="row">
        I
       </th>
       <td>
        Initial
       </td>
       <td>
        Data nodes must be restarted using the
        <a class="link" href="mysql-cluster-programs-ndbd.html#option_ndbd_initial">
         <code class="option">
          --initial
         </code>
        </a>
        option
       </td>
      </tr>
     </tbody>
    </table>
   </div>
  </div>
  <br class="table-break"/>
 </div>
 <br/>
</div>
