List:Commits« Previous MessageNext Message »
From:jon.stephens Date:June 21 2011 10:26am
Subject:svn commit - mysqldoc@oter02: r26566 - trunk/ndbapi
View as plain text  
Author: js221926
Date: 2011-06-21 12:26:36 +0200 (Tue, 21 Jun 2011)
New Revision: 26566

Log:


General revisions & updates




Modified:
   trunk/ndbapi/ndb-internals.xml
   trunk/ndbapi/overview.xml


Modified: trunk/ndbapi/ndb-internals.xml
===================================================================
--- trunk/ndbapi/ndb-internals.xml	2011-06-21 09:08:19 UTC (rev 26565)
+++ trunk/ndbapi/ndb-internals.xml	2011-06-21 10:26:36 UTC (rev 26566)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 631 bytes

@@ -11,8 +11,8 @@
 
     <para>
       This chapter contains information about MySQL Cluster that is not
-      strictly necessary for running the Cluster product, but can prove
-      useful for development and debugging purposes.
+      strictly necessary for running the MySQL Cluster product, but can
+      prove useful for development and debugging purposes.
     </para>
 
   </abstract>


Modified: trunk/ndbapi/overview.xml
===================================================================
--- trunk/ndbapi/overview.xml	2011-06-21 09:08:19 UTC (rev 26565)
+++ trunk/ndbapi/overview.xml	2011-06-21 10:26:36 UTC (rev 26566)
Changed blocks: 7, Lines Added: 387, Lines Deleted: 323; 28818 bytes

@@ -49,8 +49,8 @@
         transactions are ACID-compliant in that they provide a means to
         group operations in such a way that they succeed (commit) or
         fail as a unit (rollback). It is also possible to perform
-        operations in a "no-commit" or deferred mode, to be committed at
-        a later time.
+        operations in a <quote>no-commit</quote> or deferred mode, to be
+        committed at a later time.
       </para>
 
       <indexterm>

@@ -76,9 +76,9 @@
       <para>
         In addition, the NDB API provides object-oriented error-handling
         facilities in order to provide a means of recovering gracefully
-        from failed operations and other problems. See
+        from failed operations and other problems. (See
         <xref linkend="ndb-examples-handling-errors"/>, for a detailed
-        example.
+        example.)
       </para>
 
       <para>

@@ -91,8 +91,8 @@
         model (respectively) database connections, cluster connections,
         transactions, and operations. These classes and their subclasses
         are listed in <xref linkend="ndb-classes"/>. Error conditions in
-        the NDB API are handled using the
-        <literal role="ndbapi">NdbError</literal> structure.
+        the NDB API are handled using
+        <literal role="ndbapi">NdbError</literal>.
       </para>
 
       <indexterm>

@@ -112,19 +112,20 @@
 
       <note>
         <para>
-          NDB API applications access MySQL Cluster directly, without
-          accessing a MySQL Server. This means that such applications
-          are not bound by the MySQL privilege system; any NDB API
-          application can read or write to any
-          <literal role="se">NDB</literal> table stored in the cluster
-          at any time without restriction.
+          NDB API applications access the MySQL Cluster&apos;s data
+          store directly, without requiring a MySQL Server as an
+          intermediary. This means that such applications are not bound
+          by the MySQL privilege system; any NDB API application has
+          read and write access to any <literal role="se">NDB</literal>
+          table stored in the same MySQL Cluster at any time without
+          restriction.
         </para>
 
         <para>
           In MySQL Cluster NDB 7.2.0 and later, it is possible to
           distribute the MySQL grant tables, converting them from the
-          <literal role="se">MyISAM</literal> storage engine to
-          <literal role="se">NDB</literal>. Thus, if this has been done,
+          default (<literal role="se">MyISAM</literal>) storage engine
+          to <literal role="se">NDB</literal>. Once this has been done,
           NDB API applications can access any of the MySQL grant tables.
           This means that such applications can read or write user
           names, passwords, and any other data stored in these tables.

@@ -142,17 +143,17 @@
         known as the <firstterm>MGM API</firstterm>, is a C-language
         programming interface intended to provide administrative
         services for the cluster. These include starting and stopping
-        Cluster nodes, handling Cluster logging, backups, and
-        restoration from backups, as well as various other management
-        tasks. A conceptual overview of MGM and its uses can be found in
-        <xref linkend="mgm-api"/>.
+        MySQL Cluster nodes, handling MySQL Cluster logging, backups,
+        and restoration from backups, as well as various other
+        management tasks. A conceptual overview of the MGM API and its
+        uses can be found in <xref linkend="mgm-api"/>.
       </para>
 
       <para>
         The MGM API's principal structures model the states of
         individual modes
         (<literal role="mgmapi">ndb_mgm_node_state</literal>), the state
-        of the Cluster as a whole
+        of the MySQL Cluster as a whole
         (<literal role="mgmapi">ndb_mgm_cluster_state</literal>), and
         management server response messages
         (<literal role="mgmapi">ndb_mgm_reply</literal>). See

@@ -171,8 +172,9 @@
     <abstract>
 
       <para>
-        Provides a glossary of terms which are unique to the NDB and MGM
-        APIs, or have a specialized meaning when applied therein.
+        This section provides a glossary of terms which are unique to
+        the NDB and MGM APIs, or that have a specialized meaning when
+        applied in the context of either or both of these APIs.
       </para>
 
     </abstract>

@@ -180,393 +182,455 @@
     <para>
       The terms in the following list are useful to an understanding of
       MySQL Cluster, the NDB API, or have a specialized meaning when
-      used in one of these contexts:
+      used in one of these:
     </para>
 
-    <itemizedlist>
+    <formalpara>
 
-      <listitem>
-        <para>
-          <indexterm>
-            <primary>backup</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+      <title>Backup</title>
 
-          <emphasis role="bold">Backup</emphasis>: A complete copy of
-          all cluster data, transactions and logs, saved to disk.
-        </para>
-      </listitem>
+      <para>
+        <indexterm>
+          <primary>backup</primary>
+          <secondary>defined</secondary>
+        </indexterm>
 
-      <listitem>
-        <para>
-          <indexterm>
-            <primary>restore</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+        A complete copy of all MySQL Cluster data, transactions and
+        logs, saved to disk.
+      </para>
 
-          <emphasis role="bold">Restore</emphasis>: Returning the
-          cluster to a previous state as stored in a backup.
-        </para>
-      </listitem>
+    </formalpara>
 
-      <listitem>
-        <para>
-          <indexterm>
-            <primary>checkpoint</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+    <formalpara>
 
-          <emphasis role="bold">Checkpoint</emphasis>: Generally
-          speaking, when data is saved to disk, it is said that a
-          checkpoint has been reached. When working with the
-          <literal>NDB</literal> storage engine, there are two sorts of
-          checkpoints which work together in order to ensure that a
-          consistent view of the cluster's data is maintained:
-        </para>
+      <title>Restore</title>
 
-        <itemizedlist>
+      <para>
+        <indexterm>
+          <primary>restore</primary>
+          <secondary>defined</secondary>
+        </indexterm>
 
-          <listitem>
-            <para>
-              <indexterm>
-                <primary>LCP (Local Checkpoint)</primary>
-                <secondary>defined</secondary>
-              </indexterm>
+        Return the cluster to a previous state, as stored in a backup.
+      </para>
 
-              <emphasis role="bold">Local Checkpoint (LCP)</emphasis>:
-              This is a checkpoint that is specific to a single node;
-              however, LCPs take place for all nodes in the cluster more
-              or less concurrently. An LCP involves saving all of a
-              node's data to disk, and so usually occurs every few
-              minutes, depending upon the amount of data stored by the
-              node.
-            </para>
+    </formalpara>
 
-            <para>
-              More detailed information about LCPs and their behavior
-              can be found in the MySQL Manual, in the sections
-              <xref linkend="mysql-cluster-ndbd-definition"/>, and
-              <xref linkend="mysql-cluster-config-lcp-params"/>.
-            </para>
-          </listitem>
+    <formalpara>
 
-          <listitem>
-            <para>
-              <indexterm>
-                <primary>GCP (Global Checkpoint)</primary>
-                <secondary>defined</secondary>
-              </indexterm>
+      <title>Checkpoint</title>
 
-              <emphasis role="bold">Global Checkpoint (GCP)</emphasis>:
-              A GCP occurs every few seconds, when transactions for all
-              nodes are synchronized and the REDO log is flushed to
-              disk.
-            </para>
+      <para>
+        <indexterm>
+          <primary>checkpoint</primary>
+          <secondary>defined</secondary>
+        </indexterm>
 
-            <para>
-              A related term is <firstterm>GCI</firstterm>, which stands
-              for <quote>Global Checkpoint ID</quote>. This marks the
-              point in the REDO log where a GCP took place.
-            </para>
-          </listitem>
+        Generally speaking, when data is saved to disk, it is said that
+        a checkpoint has been reached. When working with the
+        <literal>NDB</literal> storage engine, there are two sorts of
+        checkpoints which work together in order to ensure that a
+        consistent view of the cluster's data is maintained. These two
+        types, <firstterm>local checkpoints</firstterm> and
+        <firstterm>global checkpoints</firstterm>, are described in the
+        next few paragraphs:
+      </para>
 
-        </itemizedlist>
-      </listitem>
+    </formalpara>
 
-      <listitem>
-        <para>
-          <indexterm>
-            <primary>node</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+    <formalpara>
 
-          <indexterm>
-            <primary>management (MGM) node</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+      <title>Local checkpoint (LCP)</title>
 
-          <indexterm>
-            <primary>API node</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+      <para>
+        <indexterm>
+          <primary>LCP (Local Checkpoint)</primary>
+          <secondary>defined</secondary>
+        </indexterm>
 
-          <indexterm>
-            <primary>SQL node</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+        This is a checkpoint that is specific to a single node; however,
+        LCPs take place for all nodes in the cluster more or less
+        concurrently. An LCP involves saving all of a node's data to
+        disk, and so usually occurs every few minutes, depending upon
+        the amount of data stored by the node.
+      </para>
 
-          <indexterm>
-            <primary>data node</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+    </formalpara>
 
-          <emphasis role="bold">Node</emphasis>: A component of MySQL
-          Cluster. 3 node types are supported:
-        </para>
+    <para>
+      More detailed information about LCPs and their behavior can be
+      found in the MySQL Manual, in the sections
+      <xref linkend="mysql-cluster-ndbd-definition"/>, and
+      <xref linkend="mysql-cluster-config-lcp-params"/>.
+    </para>
 
-        <itemizedlist>
+    <formalpara>
 
-          <listitem>
-            <para>
-              <firstterm>Management (MGM) node</firstterm>: This is an
-              instance of <command>ndb_mgmd</command>, the cluster
-              management server daemon.
-            </para>
-          </listitem>
+      <title>Global checkpoint (GCP)</title>
 
-          <listitem>
-            <para>
-              <firstterm>Data node</firstterm> (sometimes also referred
-              to as a <quote>storage nodes</quote>, although this usage
-              is now discouraged): This is an instance of
-              <command>ndbd</command>, and stores cluster data.
-            </para>
-          </listitem>
+      <para>
+        <indexterm>
+          <primary>GCP (Global Checkpoint)</primary>
+          <secondary>defined</secondary>
+        </indexterm>
 
-          <listitem>
-            <para>
-              <firstterm>API node</firstterm>: This is an application
-              that accesses cluster data. <firstterm>SQL
-              node</firstterm> refers to a <command>mysqld</command>
-              process that is connected to the cluster as an API node.
-            </para>
-          </listitem>
+        A GCP occurs every few seconds, when transactions for all nodes
+        are synchronized and the REDO log is flushed to disk.
+      </para>
 
-        </itemizedlist>
+    </formalpara>
 
-        <para>
-          For more information about these node types, please refer to
-          <xref linkend="overview-cluster-concepts"/>, or to
-          <xref linkend="mysql-cluster-programs"/>, in the MySQL Manual.
-        </para>
-      </listitem>
+    <para>
+      A related term is <firstterm>GCI</firstterm>, which stands for
+      <quote>Global Checkpoint ID</quote>. This marks the point in the
+      REDO log where a GCP took place.
+    </para>
 
-      <listitem>
-        <para>
-          <indexterm>
-            <primary>node failure</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+    <formalpara>
 
-          <emphasis role="bold">Node Failure</emphasis>: MySQL Cluster
-          is not solely dependent upon the functioning of any single
-          node making up the cluster, which can continue to run even
-          when one node fails.
-        </para>
-      </listitem>
+      <title>Node</title>
 
-      <listitem>
-        <para>
-          <indexterm>
-            <primary>node restart</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+      <para>
+        <indexterm>
+          <primary>node</primary>
+          <secondary>defined</secondary>
+        </indexterm>
 
-          <emphasis role="bold">Node Restart</emphasis>: The process of
-          restarting a cluster node which has stopped on its own or been
-          stopped deliberately. This can be done for several different
-          reasons, including the following:
-        </para>
+        <indexterm>
+          <primary>management (MGM) node</primary>
+          <secondary>defined</secondary>
+        </indexterm>
 
-        <itemizedlist>
+        <indexterm>
+          <primary>API node</primary>
+          <secondary>defined</secondary>
+        </indexterm>
 
-          <listitem>
-            <para>
-              Restarting a node which has shut down on its own (when
-              this has occurred, it is known as <firstterm>forced
-              shutdown</firstterm> or <firstterm>node
-              failure</firstterm>; the other cases dicussed here involve
-              manually shutting down the node and restarting it)
-            </para>
-          </listitem>
+        <indexterm>
+          <primary>SQL node</primary>
+          <secondary>defined</secondary>
+        </indexterm>
 
-          <listitem>
-            <para>
-              To update the node's configuration
-            </para>
-          </listitem>
+        <indexterm>
+          <primary>data node</primary>
+          <secondary>defined</secondary>
+        </indexterm>
 
-          <listitem>
-            <para>
-              As part of a software or hardware upgrade
-            </para>
-          </listitem>
+        A component of MySQL Cluster. 3 node types are supported:
+      </para>
 
-          <listitem>
-            <para>
-              In order to defragment the node&apos;s
-              <literal role="ndbparam:ndbd">DataMemory</literal>
-            </para>
-          </listitem>
+    </formalpara>
 
-        </itemizedlist>
-      </listitem>
+    <itemizedlist>
 
       <listitem>
         <para>
-          <indexterm>
-            <primary>initial node restart</primary>
-            <secondary>defined</secondary>
-          </indexterm>
-
-          <emphasis role="bold">Initial Node Restart</emphasis>: The
-          process of starting a cluster node with its file system
-          removed. This is sometimes used in the course of software
-          upgrades and in other special circumstances.
+          A <firstterm>management (MGM) node</firstterm> is an instance
+          of <command>ndb_mgmd</command>, the MySQL Cluster management
+          server daemon.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <indexterm>
-            <primary>system crash</primary>
-            <secondary>defined</secondary>
-          </indexterm>
-
-          <emphasis role="bold">System Crash</emphasis> (or
-          <emphasis role="bold">System Failure</emphasis>): This can
-          occur when so many cluster nodes have failed that the
-          cluster's state can no longer be guaranteed.
+          A <firstterm>data node</firstterm> an instance of
+          <command>ndbd</command>, the MySQL Cluster data storage
+          daemon, and stores MySQL Cluster data. In MySQL Cluster NDB
+          7.0 and later, this may also be an instance of
+          <command>ndbmtd</command>, a multithreaded version of
+          <command>ndbd</command>.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <indexterm>
-            <primary>system restart</primary>
-            <secondary>defined</secondary>
-          </indexterm>
-
-          <emphasis role="bold">System Restart</emphasis>: The process
-          of restarting the cluster and reinitialising its state from
-          disk logs and checkpoints. This is required after either a
-          planned or an unplanned shutdown of the cluster.
+          An <firstterm>API node</firstterm>is an application that
+          accesses MySQL Cluster data. <firstterm>SQL node</firstterm>
+          refers to a <command>mysqld</command> (MySQL Server) process
+          that is connected to the MySQL CLuster as an API node.
         </para>
       </listitem>
 
+    </itemizedlist>
+
+    <para>
+      For more information about these node types, please refer to
+      <xref linkend="overview-cluster-concepts"/>, or to
+      <xref linkend="mysql-cluster-programs"/>, in the <citetitle>MySQL
+      Manual</citetitle>.
+    </para>
+
+    <formalpara>
+
+      <title>Node failure</title>
+
+      <para>
+        <indexterm>
+          <primary>node failure</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        A MySQL Cluster is not solely dependent upon the functioning of
+        any single node making up the cluster, which can continue to run
+        even when one node fails.
+      </para>
+
+    </formalpara>
+
+    <formalpara>
+
+      <title>Node restart</title>
+
+      <para>
+        <indexterm>
+          <primary>node restart</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        The process of restarting a MySQL Cluster node which has stopped
+        on its own or been stopped deliberately. This can be done for
+        several different reasons, listed here:
+      </para>
+
+    </formalpara>
+
+    <itemizedlist>
+
       <listitem>
         <para>
-          <indexterm>
-            <primary>fragment</primary>
-            <secondary>defined</secondary>
-          </indexterm>
-
-          <emphasis role="bold">Fragment</emphasis>: Contains a portion
-          of a database table; in other words, in the
-          <literal>NDB</literal> storage engine, a table is broken up
-          into and stored as a number of subsets, usually referred to as
-          fragments. A fragment is sometimes also called a
-          <firstterm>partition</firstterm>.
+          Restarting a node which has shut down on its own. (This is
+          known as <firstterm>forced shutdown</firstterm> or
+          <firstterm>node failure</firstterm>; the other cases discussed
+          here involve manually shutting down the node and restarting
+          it).
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <indexterm>
-            <primary>replica</primary>
-            <secondary>defined</secondary>
-          </indexterm>
-
-          <emphasis role="bold">Replica</emphasis>: Under the
-          <literal>NDB</literal> storage engine, each table fragment has
-          number of replicas in order to provide redundancy.
+          To update the node&apos;s configuration.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <indexterm>
-            <primary>transporter</primary>
-            <secondary>defined</secondary>
-          </indexterm>
-
-          <emphasis role="bold">Transporter</emphasis>: A protocol
-          providing data transfer across a network. The NDB API supports
-          4 different types of transporter connections: TCP/IP (local),
-          TCP/IP (remote), SCI, and SHM. TCP/IP is, of course, the
-          familiar network protocol that underlies HTTP, FTP, and so
-          forth, on the Internet. SCI (Scalable Coherent Interface) is a
-          high-speed protocol used in building multiprocessor systems
-          and parallel-processing applications. SHM stands for
-          Unix-style shared memory segments. For an informal
-          introduction to SCI, see
-          <ulink url="http://www.dolphinics.com/corporate/scitech.html">this
-          essay</ulink> at dolphinics.com.
+          As part of a software or hardware upgrade.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <indexterm>
-            <primary>NDB</primary>
-            <secondary>defined</secondary>
-          </indexterm>
-
-          <literal>NDB</literal>: This originally stood for
-          <quote>Network Database</quote>. It now refers to the storage
-          engine used by MySQL AB to enable its MySQL Cluster
-          distributed database.
+          In order to defragment the node&apos;s
+          <literal role="ndbparam:ndbd">DataMemory</literal>.
         </para>
       </listitem>
 
-      <listitem>
-        <para>
-          <indexterm>
-            <primary>ACC</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+    </itemizedlist>
 
-          <indexterm>
-            <primary>Access Manager</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+    <formalpara>
 
-          <emphasis role="bold">ACC</emphasis>: Access Manager. Handles
-          hash indexes of primary keys providing speedy access to the
-          records.
-        </para>
-      </listitem>
+      <title>Initial node restart</title>
 
-      <listitem>
-        <para>
-          <indexterm>
-            <primary>TUP</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+      <para>
+        <indexterm>
+          <primary>initial node restart</primary>
+          <secondary>defined</secondary>
+        </indexterm>
 
-          <indexterm>
-            <primary>Tuple Manager</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+        The process of starting a MySQL Cluster node with its file
+        system having been removed. This is sometimes used in the course
+        of software upgrades and in other special circumstances.
+      </para>
 
-          <emphasis role="bold">TUP</emphasis>: Tuple Manager. This
-          handles storage of tuples (records) and contains the filtering
-          engine used to filter out records and attributes when
-          performing reads or updates.
-        </para>
-      </listitem>
+    </formalpara>
 
-      <listitem>
-        <para>
-          <indexterm>
-            <primary>TC</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+    <formalpara>
 
-          <indexterm>
-            <primary>Transaction Coordinator</primary>
-            <secondary>defined</secondary>
-          </indexterm>
+      <title>System crash (system failure)</title>
 
-          <emphasis role="bold">TC</emphasis>: Transaction Coordinator.
-          Handles co-ordination of transactions and timeouts; serves as
-          the interface to the NDB API for indexes and scan operations.
-        </para>
-      </listitem>
+      <para>
+        <indexterm>
+          <primary>system crash</primary>
+          <secondary>defined</secondary>
+        </indexterm>
 
-    </itemizedlist>
+        This can occur when so many data nodes have failed that the
+        MySQL Cluster&apos;s state can no longer be guaranteed.
+      </para>
 
+    </formalpara>
+
+    <formalpara>
+
+      <title>System restart</title>
+
+      <para>
+        <indexterm>
+          <primary>system restart</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        The process of restarting a MySQL Cluster and reinitializing its
+        state from disk logs and checkpoints. This is required after any
+        shutdown of the cluster, planned or unplanned.
+      </para>
+
+    </formalpara>
+
+    <formalpara>
+
+      <title>Fragment</title>
+
+      <para>
+        <indexterm>
+          <primary>fragment</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        Contains a portion of a database table. In the
+        <literal>NDB</literal> storage engine, a table is broken up into
+        and stored as a number of subsets, usually referred to as
+        fragments. A fragment is sometimes also called a
+        <firstterm>partition</firstterm>.
+      </para>
+
+    </formalpara>
+
+    <formalpara>
+
+      <title>Replica</title>
+
+      <para>
+        <indexterm>
+          <primary>replica</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        Under the <literal>NDB</literal> storage engine, each table
+        fragment has number of replicas in order to provide redundancy.
+      </para>
+
+    </formalpara>
+
+    <formalpara>
+
+      <title>Transporter</title>
+
+      <para>
+        <indexterm>
+          <primary>transporter</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        A protocol providing data transfer across a network. The NDB API
+        supports 4 different types of transporter connections: TCP/IP
+        (local), TCP/IP (remote), SCI, and SHM. TCP/IP is, of course,
+        the familiar network protocol that underlies HTTP, FTP, and so
+        forth, on the Internet. SCI (Scalable Coherent Interface) is a
+        high-speed protocol used in building multiprocessor systems and
+        parallel-processing applications. SHM stands for Unix-style
+        shared memory segments. For an informal introduction to SCI, see
+        <ulink url="http://www.dolphinics.com/corporate/scitech.html">this
+        essay at www.dolphinics.com</ulink>.
+      </para>
+
+    </formalpara>
+
+    <formalpara>
+
+      <title><literal>NDB</literal></title>
+
+      <para>
+        <indexterm>
+          <primary>NDB</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        This originally stood for <quote>Network DataBase</quote>. It
+        now refers to the MySQL storage engine (named
+        <literal role="se">NDB</literal> or
+        <literal role="se">NDBCLUSTER</literal>) used to enable the
+        MySQL Cluster distributed database system.
+      </para>
+
+    </formalpara>
+
+    <formalpara>
+
+      <title><literal>ACC</literal> (Access Manager)</title>
+
+      <para>
+        <indexterm>
+          <primary>ACC</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        <indexterm>
+          <primary>Access Manager</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        An NDB kernel block that handles hash indexes of primary keys
+        providing speedy access to the records. For more information,
+        see <xref linkend="ndb-internals-kernel-blocks-dbacc"/>.
+      </para>
+
+    </formalpara>
+
+    <formalpara>
+
+      <title><literal>TUP</literal> (Tuple Manager)</title>
+
+      <para>
+        <indexterm>
+          <primary>TUP</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        <indexterm>
+          <primary>Tuple Manager</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        This NDB kernel block handles storage of tuples (records) and
+        contains the filtering engine used to filter out records and
+        attributes when performing reads or updates. See
+        <xref linkend="ndb-internals-kernel-blocks-dbtup"/>, for more
+        information.
+      </para>
+
+    </formalpara>
+
+    <formalpara>
+
+      <title><literal role="bold">TC</literal> (Transaction Coordinator)</title>
+
+      <para>
+        <indexterm>
+          <primary>TC</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        <indexterm>
+          <primary>Transaction Coordinator</primary>
+          <secondary>defined</secondary>
+        </indexterm>
+
+        Handles coordination of transactions and timeouts in the NDB
+        kernel (see <xref linkend="ndb-internals-kernel-blocks-dbtc"/>).
+        Provides interfaces to the NDB API for performing indexes and
+        scan operations.
+      </para>
+
+    </formalpara>
+
     <para>
+      For more information, see
+      <xref linkend="ndb-internals-kernel-blocks"/>, elsewhere in this
+      <citetitle>Guide</citetitle>..
+    </para>
+
+    <para>
       See also <xref linkend="mysql-cluster-overview"/>, in the
       <citetitle>MySQL Manual</citetitle>.
     </para>


Thread
svn commit - mysqldoc@oter02: r26566 - trunk/ndbapijon.stephens21 Jun