DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 

(mysql.info.gz) MySQL Cluster SCI Definition

Info Catalog (mysql.info.gz) MySQL Cluster SHM Definition (mysql.info.gz) MySQL Cluster Config File
 
 16.3.4.9 MySQL Cluster SCI Transport Connections
 ................................................
 
 SCI Transporters as connection between nodes in the MySQL Cluster is
 only supported for special builds of MySQL Cluster using the `configure'
 parameter `--with-ndb-sci=/your/path/to/SCI'. The path should point to
 a directory that contains at least a lib and a include directory where
 SISCI libraries and header files are provided.
 
 It is strongly recommended to only use SCI Transporters for
 communication between ndbd processes. Also using SCI Transporters will
 mean that the ndbd process will never sleep so use SCI Transporters
 only for machines with at least 2 CPU's which are dedicated for use by
 ndbd process(es). There should be at least 1 CPU per ndbd process in
 this case and in addition at least one more is needed to also handle OS
 activities.
 
 `[SCI]NodeId1'
 
 `[SCI]NodeId2'
      To identify a connection between two nodes it is necessary to
      provide the node identity for both of them in `NodeId1' and
      `NodeId2'.
 
 `[SCI]Host1SciId0'
      This identifies the SCI node id on the first node identified by
      NodeId1.
 
 `[SCI]Host1SciId1'
      It is possible to set-up SCI Transporters for fail-over between
      two SCI cards which then should use separate networks between the
      nodes. This identifies the node id and the second SCI card to be
      used on the first node.
 
 `[SCI]Host2SciId0'
      This identifies the SCI node id on the second node identified by
      NodeId2.
 
 `[SCI]Host2SciId1'
      It is possible to set-up SCI Transporters for fail-over between
      two SCI cards which then should use separate networks between the
      nodes. This identifies the node id and the second SCI card to be
      used on the second node.
 
 `[SCI]SharedBufferSize'
      Each SCI transporter has a shared memory segment between the two
      nodes. With this segment set to the default 1 MB most applications
      should be ok. Smaller sizes such as 256 kB has problems when
      performing many parallel inserts.  If the buffer is too small it
      can cause crashes of the ndbd process.
 
 `[SCI]SendLimit'
      A small buffer in front of the SCI media buffers up messages
      before sending them over the SCI network. By default this is set
      to 8kB. Most benchmark measurements shows that tops are reached at
      64 kB but 16kB reaches within a few percent of the performance and
      for all MySQL Cluster benchmarks it was no measurable difference
      in increasing it beyond 8kB.
 
 `[SCI]SendSignalId'
      To be able to retrace a distributed message diagram it is
      necessary to identify each message with an identity. By setting
      this parameter to Y these message identities are also transported
      over the network.  This feature is not enabled by default.
 
 `[SCI]Checksum'
      This parameter is also a Y/N parameter which is not enabled by
      default.  When enabled all messages are checksummed before put
      into the send buffer.  This feature enables control that messages
      are not corrupted while waiting in the send buffer. It is also a
      double check that the transport mechanism haven't corrupted the
      data.
 
Info Catalog (mysql.info.gz) MySQL Cluster SHM Definition (mysql.info.gz) MySQL Cluster Config File
automatically generated byinfo2html