List:Commits« Previous MessageNext Message »
From:jon.stephens Date:October 5 2010 12:10pm
Subject:svn commit - mysqldoc@docsrva: r22979 - trunk/ndbapi
View as plain text  
Author: jstephens
Date: 2010-10-05 14:10:52 +0200 (Tue, 05 Oct 2010)
New Revision: 22979

Log:

Degunking + general revisions -- DUMP Commands section



Modified:
   trunk/ndbapi/ndb-internals.xml


Modified: trunk/ndbapi/ndb-internals.xml
===================================================================
--- trunk/ndbapi/ndb-internals.xml	2010-10-05 10:40:42 UTC (rev 22978)
+++ trunk/ndbapi/ndb-internals.xml	2010-10-05 12:10:52 UTC (rev 22979)
Changed blocks: 59, Lines Added: 819, Lines Deleted: 920; 74489 bytes

@@ -427,55 +427,55 @@
       <para>
         <emphasis>Never use these commands on a production MySQL Cluster
         except under the express direction of MySQL Technical
-        Support</emphasis>. MySQL AB will <emphasis>not</emphasis> be
-        held responsible for adverse results arising from their use
-        under any other circumstances!
+        Support</emphasis>. Oracle will <emphasis>not</emphasis> be held
+        responsible for adverse results arising from their use under any
+        other circumstances!
       </para>
     </warning>
 
     <para>
       <literal>DUMP</literal> commands can be used in the Cluster
       management client (<command>ndb_mgm</command>) to dump debugging
-      information to the Cluster log. They are documented here rather
-      than in the MySQL Manual because:
+      information to the Cluster log. They are documented here, rather
+      than in the MySQL Manual, for the following reasons:
+    </para>
 
-      <itemizedlist>
+    <itemizedlist>
 
-        <listitem>
-          <para>
-            They are intended only for use in troubleshooting,
-            debugging, and similar activities by MySQL developers, QA,
-            and support personnel.
-          </para>
-        </listitem>
+      <listitem>
+        <para>
+          They are intended only for use in troubleshooting, debugging,
+          and similar activities by MySQL developers, QA, and support
+          personnel.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            Due to the way in which <literal>DUMP</literal> commands
-            interact with memory, they can cause a running MySQL Cluster
-            to malfunction or even to fail completely when used.
-          </para>
-        </listitem>
+      <listitem>
+        <para>
+          Due to the way in which <literal>DUMP</literal> commands
+          interact with memory, they can cause a running MySQL Cluster
+          to malfunction or even to fail completely when used.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            The formats, arguments, and even availability of these
-            commands are not guaranteed to be stable. <emphasis>All of
-            this information is subject to change at any time without
-            prior notice</emphasis>.
-          </para>
-        </listitem>
+      <listitem>
+        <para>
+          The formats, arguments, and even availability of these
+          commands are not guaranteed to be stable. <emphasis>All of
+          this information is subject to change at any time without
+          prior notice</emphasis>.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            For the preceding reasons, <literal>DUMP</literal> commands
-            are neither intended nor warranted for use in a production
-            environment by end-users.
-          </para>
-        </listitem>
+      <listitem>
+        <para>
+          For the preceding reasons, <literal>DUMP</literal> commands
+          are neither intended nor warranted for use in a production
+          environment by end-users.
+        </para>
+      </listitem>
 
-      </itemizedlist>
-    </para>
+    </itemizedlist>
 
     <para>
       General syntax:

@@ -503,61 +503,62 @@
     </para>
 
     <para>
-      Each listing includes this information:
+      Each listing includes the following information:
+    </para>
 
-      <itemizedlist>
+    <itemizedlist>
 
-        <listitem>
-          <para>
-            The <replaceable>code</replaceable> value
-          </para>
-        </listitem>
+      <listitem>
+        <para>
+          The <replaceable>code</replaceable> value
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            The relevant <literal>NDB</literal> kernel block or blocks
-            (see <xref linkend="ndb-internals-kernel-blocks"/>, for
-            information about these)
-          </para>
-        </listitem>
+      <listitem>
+        <para>
+          The relevant <literal>NDB</literal> kernel block or blocks
+          (see <xref linkend="ndb-internals-kernel-blocks"/>, for
+          information about these)
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            The <literal>DUMP</literal> code symbol where defined; if
-            undefined, this is indicated using a triple dash:
-            <literal>---</literal>.
-          </para>
-        </listitem>
+      <listitem>
+        <para>
+          The <literal>DUMP</literal> code symbol where defined; if
+          undefined, this is indicated using a triple dash:
+          <literal>---</literal>.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            Sample output; unless otherwise stated, it is assumed that
-            each <literal>DUMP</literal> command is invoked as shown
-            here:
+      <listitem>
+        <para>
+          Sample output; unless otherwise stated, it is assumed that
+          each <literal>DUMP</literal> command is invoked as shown here:
+        </para>
 
 <programlisting>
 ndb_mgm&gt; <userinput>2 DUMP <replaceable>code</replaceable></userinput>
 </programlisting>
 
-            Generally, this is from the cluster log; in some cases,
-            where the output may be generated in the node log instead,
-            this is indicated. Where the DUMP command produces errors,
-            the output is generally taken from the error log.
-          </para>
-        </listitem>
+        <para>
+          Generally, this is from the cluster log; in some cases, where
+          the output may be generated in the node log instead, this is
+          indicated. Where the DUMP command produces errors, the output
+          is generally taken from the error log.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            Where applicable, additional information such as possible
-            extra <replaceable>arguments</replaceable>, warnings, state
-            or other values returned in the <literal>DUMP</literal>
-            command's output, and so on. Otherwise its absence is
-            indicated with <quote>[N/A]</quote>.
-          </para>
-        </listitem>
+      <listitem>
+        <para>
+          Where applicable, additional information such as possible
+          extra <replaceable>arguments</replaceable>, warnings, state or
+          other values returned in the <literal>DUMP</literal> command's
+          output, and so on. Otherwise its absence is indicated with
+          <quote>[N/A]</quote>.
+        </para>
+      </listitem>
 
-      </itemizedlist>
-    </para>
+    </itemizedlist>
 
     <note>
       <para>

@@ -578,8 +579,8 @@
     </note>
 
     <para>
-      For information concerning other ndb_mgm client commands, see
-      <xref linkend="mysql-cluster-mgm-client-commands"/>.
+      For information concerning other <command>ndb_mgm</command> client
+      commands, see <xref linkend="mysql-cluster-mgm-client-commands"/>.
     </para>
 
     <remark role="note">

@@ -590,6 +591,11 @@
 
       <title><literal>DUMP</literal> Codes 1 to 999</title>
 
+      <para>
+        This section contains information about <literal>DUMP</literal>
+        codes 1 through 999, inclusive.
+      </para>
+
       <section id="ndb-internals-dump-command-1">
 
         <title><literal>DUMP 1</literal></title>

@@ -945,48 +951,49 @@
           <title>Additional Information</title>
 
           <para>
-            Possible node status values:
-
-            <informaltable>
-              <tgroup cols="2">
-                <colspec colwidth="40*"/>
-                <colspec colwidth="40*"/>
-                <tbody>
-                  <row>
-                    <entry><emphasis role="bold">Value</emphasis></entry>
-                    <entry><emphasis role="bold">Name</emphasis></entry>
-                  </row>
-                  <row>
-                    <entry>0</entry>
-                    <entry><literal>NOT_IN_CLUSTER</literal></entry>
-                  </row>
-                  <row>
-                    <entry>1</entry>
-                    <entry><literal>ALIVE</literal></entry>
-                  </row>
-                  <row>
-                    <entry>2</entry>
-                    <entry><literal>STARTING</literal></entry>
-                  </row>
-                  <row>
-                    <entry>3</entry>
-                    <entry><literal>DIED_NOW</literal></entry>
-                  </row>
-                  <row>
-                    <entry>4</entry>
-                    <entry><literal>DYING</literal></entry>
-                  </row>
-                  <row>
-                    <entry>5</entry>
-                    <entry><literal>DEAD</literal></entry>
-                  </row>
-                </tbody>
-              </tgroup>
-            </informaltable>
+            Possible node status values are shown in the following
+            table:
           </para>
 
         </formalpara>
 
+        <informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="40*"/>
+            <colspec colwidth="40*"/>
+            <tbody>
+              <row>
+                <entry><emphasis role="bold">Value</emphasis></entry>
+                <entry><emphasis role="bold">Name</emphasis></entry>
+              </row>
+              <row>
+                <entry>0</entry>
+                <entry><literal>NOT_IN_CLUSTER</literal></entry>
+              </row>
+              <row>
+                <entry>1</entry>
+                <entry><literal>ALIVE</literal></entry>
+              </row>
+              <row>
+                <entry>2</entry>
+                <entry><literal>STARTING</literal></entry>
+              </row>
+              <row>
+                <entry>3</entry>
+                <entry><literal>DIED_NOW</literal></entry>
+              </row>
+              <row>
+                <entry>4</entry>
+                <entry><literal>DYING</literal></entry>
+              </row>
+              <row>
+                <entry>5</entry>
+                <entry><literal>DEAD</literal></entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable>
+
       </section>
 
       <section id="ndb-internals-dump-command-18">

@@ -1121,8 +1128,12 @@
           <title>Additional Information</title>
 
           <para>
-            Can also be used to set these parameters, for example:
+            This command can also be used to set these parameters, as in
+            this example:
+          </para>
 
+        </formalpara>
+
 <programlisting>
 ndb_mgm&gt; <userinput>2 DUMP 20 3 3 64 512</userinput>
 Sending dump signal with data:

@@ -1131,18 +1142,14 @@
 Node 2: Backup: data: 3145728 log: 3145728 min: 65536 max: 524288
 </programlisting>
 
-            <warning>
-              <para>
-                You must set each of these parameters to the same value
-                on all nodes; otherwise, subsequent issuing of a
-                <literal>START BACKUP</literal> command crashes the
-                cluster.
-              </para>
-            </warning>
+        <warning>
+          <para>
+            You must set each of these parameters to the same value on
+            all nodes; otherwise, subsequent issuing of a <literal>START
+            BACKUP</literal> command crashes the cluster.
           </para>
+        </warning>
 
-        </formalpara>
-
       </section>
 
       <section id="ndb-internals-dump-command-21">

@@ -1274,13 +1281,9 @@
           <title>Additional Information</title>
 
           <para>
-            <warning>
-              <para>
-                It appears that <emphasis>any</emphasis> invocation of
-                <literal>DUMP 22</literal> causes the node or nodes to
-                crash.
-              </para>
-            </warning>
+            It appears that <emphasis>any</emphasis> invocation of
+            <literal>DUMP 22</literal> causes the node or nodes to
+            crash.
           </para>
 
         </formalpara>

@@ -1318,18 +1321,18 @@
           <para>
             Dumps all backup records and file entries belonging to those
             records.
-
-            <note>
-              <para>
-                The example shows a single record with a single file
-                only, but there may be multiple records and multiple
-                file lines within each record.
-              </para>
-            </note>
           </para>
 
         </formalpara>
 
+        <note>
+          <para>
+            The example shows a single record with a single file only,
+            but there may be multiple records and multiple file lines
+            within each record.
+          </para>
+        </note>
+
         <formalpara>
 
           <title>Sample Output</title>

@@ -1337,15 +1340,20 @@
           <para>
             With no backup in progress (<literal>BackupRecord</literal>
             shows as <literal>0</literal>):
+          </para>
 
+        </formalpara>
+
 <programlisting>
 Node 2: BackupRecord 0: BackupId: 5 MasterRef: f70002 ClientRef: 0
 Node 2:  State: 2
 Node 2:  file 0: type: 3 flags: H'0
 </programlisting>
 
-            While a backup is in progress
-            (<literal>BackupRecord</literal> is <literal>1</literal>):
+        <para>
+          While a backup is in progress (<literal>BackupRecord</literal>
+          is <literal>1</literal>):
+        </para>
 
 <programlisting>
 Node 2: BackupRecord 1: BackupId: 8 MasterRef: f40002 ClientRef: 80010001

@@ -1357,145 +1365,147 @@
 Node 2:  State: 2
 Node 2:  file 0: type: 3 flags: H'0
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>
 
           <para>
-            <literal>State</literal> values:
+            Possible <literal>State</literal> values are shown in the
+            following table:
+          </para>
 
-            <informaltable>
-              <tgroup cols="3">
-                <colspec colwidth="10*"/>
-                <colspec colwidth="20*"/>
-                <colspec colwidth="30*"/>
-                <tbody>
-                  <row>
-                    <entry><emphasis role="bold">Value</emphasis></entry>
-                    <entry><emphasis role="bold">State</emphasis></entry>
-                    <entry><emphasis role="bold">Description</emphasis></entry>
-                  </row>
-                  <row>
-                    <entry>0</entry>
-                    <entry><literal>INITIAL</literal></entry>
-                    <entry/>
-                  </row>
-                  <row>
-                    <entry>1</entry>
-                    <entry><literal>DEFINING</literal></entry>
-                    <entry>Defining backup content and parameters</entry>
-                  </row>
-                  <row>
-                    <entry>2</entry>
-                    <entry><literal>DEFINED</literal></entry>
-                    <entry><literal>DEFINE_BACKUP_CONF</literal> signal sent by slave, received on
-                      master</entry>
-                  </row>
-                  <row>
-                    <entry>3</entry>
-                    <entry><literal>STARTED</literal></entry>
-                    <entry>Creating triggers</entry>
-                  </row>
-                  <row>
-                    <entry>4</entry>
-                    <entry><literal>SCANNING</literal></entry>
-                    <entry>Scanning fragments</entry>
-                  </row>
-                  <row>
-                    <entry>5</entry>
-                    <entry><literal>STOPPING</literal></entry>
-                    <entry>Closing files</entry>
-                  </row>
-                  <row>
-                    <entry>6</entry>
-                    <entry><literal>CLEANING</literal></entry>
-                    <entry>Freeing resources</entry>
-                  </row>
-                  <row>
-                    <entry>7</entry>
-                    <entry><literal>ABORTING</literal></entry>
-                    <entry>Aborting backup</entry>
-                  </row>
-                </tbody>
-              </tgroup>
-            </informaltable>
+        </formalpara>
 
-            Types:
+        <informaltable>
+          <tgroup cols="3">
+            <colspec colwidth="10*"/>
+            <colspec colwidth="20*"/>
+            <colspec colwidth="30*"/>
+            <tbody>
+              <row>
+                <entry><emphasis role="bold">Value</emphasis></entry>
+                <entry><emphasis role="bold">State</emphasis></entry>
+                <entry><emphasis role="bold">Description</emphasis></entry>
+              </row>
+              <row>
+                <entry>0</entry>
+                <entry><literal>INITIAL</literal></entry>
+                <entry/>
+              </row>
+              <row>
+                <entry>1</entry>
+                <entry><literal>DEFINING</literal></entry>
+                <entry>Defining backup content and parameters</entry>
+              </row>
+              <row>
+                <entry>2</entry>
+                <entry><literal>DEFINED</literal></entry>
+                <entry><literal>DEFINE_BACKUP_CONF</literal> signal sent by slave, received on
+                  master</entry>
+              </row>
+              <row>
+                <entry>3</entry>
+                <entry><literal>STARTED</literal></entry>
+                <entry>Creating triggers</entry>
+              </row>
+              <row>
+                <entry>4</entry>
+                <entry><literal>SCANNING</literal></entry>
+                <entry>Scanning fragments</entry>
+              </row>
+              <row>
+                <entry>5</entry>
+                <entry><literal>STOPPING</literal></entry>
+                <entry>Closing files</entry>
+              </row>
+              <row>
+                <entry>6</entry>
+                <entry><literal>CLEANING</literal></entry>
+                <entry>Freeing resources</entry>
+              </row>
+              <row>
+                <entry>7</entry>
+                <entry><literal>ABORTING</literal></entry>
+                <entry>Aborting backup</entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable>
 
-            <informaltable>
-              <tgroup cols="2">
-                <colspec colwidth="10*"/>
-                <colspec colwidth="50*"/>
-                <tbody>
-                  <row>
-                    <entry><emphasis role="bold">Value</emphasis></entry>
-                    <entry><emphasis role="bold">Name</emphasis></entry>
-                  </row>
-                  <row>
-                    <entry>1</entry>
-                    <entry><literal>CTL_FILE</literal></entry>
-                  </row>
-                  <row>
-                    <entry>2</entry>
-                    <entry><literal>LOG_FILE</literal></entry>
-                  </row>
-                  <row>
-                    <entry>3</entry>
-                    <entry><literal>DATA_FILE</literal></entry>
-                  </row>
-                  <row>
-                    <entry>4</entry>
-                    <entry><literal>LCP_FILE</literal></entry>
-                  </row>
-                </tbody>
-              </tgroup>
-            </informaltable>
+        <para>
+          Types are shown in the following table:
+        </para>
 
-            Flags:
+        <informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="10*"/>
+            <colspec colwidth="50*"/>
+            <tbody>
+              <row>
+                <entry><emphasis role="bold">Value</emphasis></entry>
+                <entry><emphasis role="bold">Name</emphasis></entry>
+              </row>
+              <row>
+                <entry>1</entry>
+                <entry><literal>CTL_FILE</literal></entry>
+              </row>
+              <row>
+                <entry>2</entry>
+                <entry><literal>LOG_FILE</literal></entry>
+              </row>
+              <row>
+                <entry>3</entry>
+                <entry><literal>DATA_FILE</literal></entry>
+              </row>
+              <row>
+                <entry>4</entry>
+                <entry><literal>LCP_FILE</literal></entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable>
 
-            <informaltable>
-              <tgroup cols="2">
-                <colspec colwidth="20*"/>
-                <colspec colwidth="40*"/>
-                <tbody>
-                  <row>
-                    <entry><emphasis role="bold">Value</emphasis></entry>
-                    <entry><emphasis role="bold">Name</emphasis></entry>
-                  </row>
-                  <row>
-                    <entry><literal>0x01</literal></entry>
-                    <entry><literal>BF_OPEN</literal></entry>
-                  </row>
-                  <row>
-                    <entry><literal>0x02</literal></entry>
-                    <entry><literal>BF_OPENING</literal></entry>
-                  </row>
-                  <row>
-                    <entry><literal>0x04</literal></entry>
-                    <entry><literal>BF_CLOSING</literal></entry>
-                  </row>
-                  <row>
-                    <entry><literal>0x08</literal></entry>
-                    <entry><literal>BF_FILE_THREAD</literal></entry>
-                  </row>
-                  <row>
-                    <entry><literal>0x10</literal></entry>
-                    <entry><literal>BF_SCAN_THREAD</literal></entry>
-                  </row>
-                  <row>
-                    <entry><literal>0x20</literal></entry>
-                    <entry><literal>BF_LCP_META</literal></entry>
-                  </row>
-                </tbody>
-              </tgroup>
-            </informaltable>
-          </para>
+        <para>
+          Flags are shown in the following table:
+        </para>
 
-        </formalpara>
+        <informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="20*"/>
+            <colspec colwidth="40*"/>
+            <tbody>
+              <row>
+                <entry><emphasis role="bold">Value</emphasis></entry>
+                <entry><emphasis role="bold">Name</emphasis></entry>
+              </row>
+              <row>
+                <entry><literal>0x01</literal></entry>
+                <entry><literal>BF_OPEN</literal></entry>
+              </row>
+              <row>
+                <entry><literal>0x02</literal></entry>
+                <entry><literal>BF_OPENING</literal></entry>
+              </row>
+              <row>
+                <entry><literal>0x04</literal></entry>
+                <entry><literal>BF_CLOSING</literal></entry>
+              </row>
+              <row>
+                <entry><literal>0x08</literal></entry>
+                <entry><literal>BF_FILE_THREAD</literal></entry>
+              </row>
+              <row>
+                <entry><literal>0x10</literal></entry>
+                <entry><literal>BF_SCAN_THREAD</literal></entry>
+              </row>
+              <row>
+                <entry><literal>0x20</literal></entry>
+                <entry><literal>BF_LCP_META</literal></entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable>
 
       </section>
 

@@ -1658,7 +1668,7 @@
 
           <title>Description</title>
 
-          <para/>
+          <para></para>
 
         </formalpara>
 

@@ -2121,6 +2131,11 @@
 
       <title><literal>DUMP</literal> Codes 1000 to 1999</title>
 
+      <para>
+        This section contain information about <literal>DUMP</literal>
+        codes 1000 through 1999, inclusive.
+      </para>
+
       <section id="ndb-internals-dump-command-1000">
 
         <title><literal>DUMP 1000</literal></title>

@@ -2168,18 +2183,18 @@
 Node 2: Index usage is 1%(24 8K pages of total 1312)
 Node 2: Resource 0 min: 0 max: 639 curr: 0
         </programlisting>
-
-            <note>
-              <para>
-                When invoked as <literal>ALL DUMP 1000</literal>, this
-                command reports memory usage for each data node
-                separately, in turn.
-              </para>
-            </note>
           </para>
 
         </formalpara>
 
+        <note>
+          <para>
+            When invoked as <literal>ALL DUMP 1000</literal>, this
+            command reports memory usage for each data node separately,
+            in turn.
+          </para>
+        </note>
+
         <formalpara>
 
           <title>Additional Information</title>

@@ -2595,47 +2610,49 @@
           <para>
             The redo log buffer is measured in 32KB pages, so the sample
             output can be interpreted as follows:
+          </para>
 
-            <itemizedlist>
+        </formalpara>
 
-              <listitem>
-                <formalpara>
+        <itemizedlist>
 
-                  <title>Redo log buffer total</title>
+          <listitem>
+            <formalpara>
 
-                  <para/>
+              <title>Redo log buffer total</title>
 
-                </formalpara>
-              </listitem>
+              <para>
+                8,338KB = ~8.2MB
+              </para>
 
-              <listitem>
-                <formalpara>
+            </formalpara>
+          </listitem>
 
-                  <title>Redo log buffer free</title>
+          <listitem>
+            <formalpara>
 
-                  <para>
-                    7,808KB = ~7.6MB
-                  </para>
+              <title>Redo log buffer free</title>
 
-                </formalpara>
-              </listitem>
+              <para>
+                7,808KB = ~7.6MB
+              </para>
 
-              <listitem>
-                <formalpara>
+            </formalpara>
+          </listitem>
 
-                  <title>Redo log buffer used</title>
+          <listitem>
+            <formalpara>
 
-                  <para>
-                    384KB = ~0.4MB
-                  </para>
+              <title>Redo log buffer used</title>
 
-                </formalpara>
-              </listitem>
+              <para>
+                384KB = ~0.4MB
+              </para>
 
-            </itemizedlist>
-          </para>
+            </formalpara>
+          </listitem>
 
-        </formalpara>
+        </itemizedlist>
 
       </section>
 

@@ -2645,6 +2662,11 @@
 
       <title><literal>DUMP</literal> Codes 2000 to 2999</title>
 
+      <para>
+        This section contains information about <literal>DUMP</literal>
+        codes 2000 through 2999, inclusive.
+      </para>
+
       <section id="ndb-internals-dump-command-2300">
 
         <title><literal>DUMP 2300</literal></title>

@@ -2952,7 +2974,10 @@
             The following is taken from
             <filename>ndb_1_out.log</filename> for a cluster with 2 data
             nodes:
+          </para>
 
+        </formalpara>
+
 <programlisting>
 LP 2 state: 0 WW_Gci: 1 gcprec: -256 flq: -256 currfile: 32 tailFileNo: 0 logTailMbyte: 1
   file 0(32)  FileChangeState: 0  logFileStatus: 20  currentMbyte: 1  currentFilepage 55

@@ -2989,10 +3014,7 @@
   file 14(62)  FileChangeState: 0  logFileStatus: 1  currentMbyte: 0  currentFilepage 0
   file 15(63)  FileChangeState: 0  logFileStatus: 1  currentMbyte: 0  currentFilepage 0
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>

@@ -3079,8 +3101,8 @@
           <title>Additional Information</title>
 
           <para>
-            No error message written to cluster log when the node is
-            killed. Node failure is made evident only by subsequent
+            No error message is written to the cluster log when the node
+            is killed. Node failure is made evident only by subsequent
             heartbeat failure messages.
           </para>
 

@@ -3255,7 +3277,10 @@
 
           <para>
             Dump all operations on data node 2, from API node 5:
+          </para>
 
+        </formalpara>
+
 <programlisting>
 ndb_mgm&gt; <userinput>2 DUMP 2350 1 5</userinput>
 2006-10-09 13:16:49 [MgmSrvr] INFO     -- Node 2: Starting dump of operations

@@ -3263,279 +3288,204 @@
 Tab: 4 frag: 0 TC: 3 API: 5(0x8035)transid: 0x31c 0x3500500 op: SCAN state: InQueue
 2006-10-09 13:16:49 [MgmSrvr] INFO     -- Node 2: End of operation dump
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional information</title>
 
           <para>
-            <orderedlist>
+            Information about operation filter and operation state
+            values follows.
+          </para>
 
-              <listitem>
-                <formalpara>
+        </formalpara>
 
-                  <title>Operation filter values</title>
+        <formalpara>
 
-                  <para>
-                    The operation filter (or filters) can take on the
-                    following values:
+          <title>Operation filter values</title>
 
-                    <informaltable>
-                      <tgroup cols="2">
-                        <colspec colwidth="25*"/>
-                        <colspec colwidth="75*"/>
-                        <thead>
-                          <row>
-                            <entry>Value</entry>
-                            <entry>Filter</entry>
-                          </row>
-                        </thead>
-                        <tbody>
-                          <row>
-                            <entry>0</entry>
-                            <entry>table ID</entry>
-                          </row>
-                          <row>
-                            <entry>1</entry>
-                            <entry>API node ID</entry>
-                          </row>
-                          <row>
-                            <entry>2</entry>
-                            <entry>2 transaction IDs, defining a range of transactions</entry>
-                          </row>
-                          <row>
-                            <entry>3</entry>
-                            <entry>transaction coordinator node ID</entry>
-                          </row>
-                        </tbody>
-                      </tgroup>
-                    </informaltable>
+          <para>
+            The operation filter (or filters) can take on the following
+            values:
+          </para>
 
-                    In each case, the ID of the object specified follows
-                    the specifier. See the sample output for examples.
-                  </para>
+        </formalpara>
 
-                </formalpara>
-              </listitem>
+        <informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="25*"/>
+            <colspec colwidth="75*"/>
+            <thead>
+              <row>
+                <entry>Value</entry>
+                <entry>Filter</entry>
+              </row>
+            </thead>
+            <tbody>
+              <row>
+                <entry>0</entry>
+                <entry>table ID</entry>
+              </row>
+              <row>
+                <entry>1</entry>
+                <entry>API node ID</entry>
+              </row>
+              <row>
+                <entry>2</entry>
+                <entry>2 transaction IDs, defining a range of transactions</entry>
+              </row>
+              <row>
+                <entry>3</entry>
+                <entry>transaction coordinator node ID</entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable>
 
-              <listitem>
-                <formalpara>
+        <para>
+          In each case, the ID of the object specified follows the
+          specifier. See the sample output for examples.
+        </para>
 
-                  <title>Operation states</title>
+        <formalpara>
 
-                  <para>
-                    The <quote>normal</quote> states that may appear in
-                    the output from this command are listed here:
+          <title>Operation states</title>
 
-                    <itemizedlist>
+          <para>
+            The <quote>normal</quote> states that may appear in the
+            output from this command are listed here:
+          </para>
 
-                      <listitem>
-                        <formalpara>
+        </formalpara>
 
-                          <title>Transactions</title>
+        <itemizedlist>
 
-                          <para>
-                            <itemizedlist>
+          <listitem>
+            <para>
+              <emphasis>Transactions</emphasis>:
+            </para>
 
-                              <listitem>
-                                <formalpara>
+            <itemizedlist>
 
-                                  <title><literal>Prepared</literal></title>
+              <listitem>
+                <para>
+                  <literal>Prepared</literal>: The transaction
+                  coordinator is idle, waiting for the API to proceed
+                </para>
+              </listitem>
 
-                                  <para>
-                                    The transaction coordinator is idle,
-                                    waiting for the API to proceed
-                                  </para>
+              <listitem>
+                <para>
+                  <literal>Running</literal>: The transaction
+                  coordinator is currently preparing operations
+                </para>
+              </listitem>
 
-                                </formalpara>
-                              </listitem>
+              <listitem>
+                <para>
+                  <literal>Committing</literal>, <literal>Prepare to
+                  commit</literal>, <literal>Commit sent</literal>: The
+                  transaction coordinator is committing
+                </para>
+              </listitem>
 
-                              <listitem>
-                                <formalpara>
+              <listitem>
+                <para>
+                  <literal>Completing</literal>: The transaction
+                  coordinator is completing the commit (after commit,
+                  some cleanup is needed)
+                </para>
+              </listitem>
 
-                                  <title><literal>Running</literal></title>
+              <listitem>
+                <para>
+                  <literal>Aborting</literal>: The transaction
+                  coordinator is aborting the transaction
+                </para>
+              </listitem>
 
-                                  <para>
-                                    The transaction coordinator is
-                                    currently preparing operations
-                                  </para>
+              <listitem>
+                <para>
+                  <literal>Scanning</literal>: The transaction
+                  coordinator is scanning
+                </para>
+              </listitem>
 
-                                </formalpara>
-                              </listitem>
+            </itemizedlist>
+          </listitem>
 
-                              <listitem>
-                                <formalpara>
+          <listitem>
+            <para>
+              <emphasis>Scan operations</emphasis>:
+            </para>
 
-                                  <title><literal>Committing</literal>, <literal>Prepare to commit</literal>,
-                                    <literal>Commit sent</literal></title>
+            <itemizedlist>
 
-                                  <para>
-                                    The transaction coordinator is
-                                    committing
-                                  </para>
+              <listitem>
+                <para>
+                  <literal>WaitNextScan</literal>: The scan is idle,
+                  waiting for API
+                </para>
+              </listitem>
 
-                                </formalpara>
-                              </listitem>
+              <listitem>
+                <para>
+                  <literal>InQueue</literal>: The scan has not yet
+                  started, but rather is waiting in queue for other
+                  scans to complete
+                </para>
+              </listitem>
 
-                              <listitem>
-                                <formalpara>
+            </itemizedlist>
+          </listitem>
 
-                                  <title><literal>Completing</literal></title>
+          <listitem>
+            <para>
+              <emphasis>Primary key operations</emphasis>:
+            </para>
 
-                                  <para>
-                                    The transaction coordinator is
-                                    completing the commit (after commit,
-                                    some cleanup is needed)
-                                  </para>
+            <itemizedlist>
 
-                                </formalpara>
-                              </listitem>
+              <listitem>
+                <para>
+                  <literal>In lock queue</literal>: The operation is
+                  waiting on a lock
+                </para>
+              </listitem>
 
-                              <listitem>
-                                <formalpara>
+              <listitem>
+                <para>
+                  <literal>Running</literal>: The operation is being
+                  prepared
+                </para>
+              </listitem>
 
-                                  <title><literal>Aborting</literal></title>
+              <listitem>
+                <para>
+                  <literal>Prepared</literal>: The operation is
+                  prepared, holding an appropriate lock, and waiting for
+                  commit or rollback to complete
+                </para>
+              </listitem>
 
-                                  <para>
-                                    The transaction coordinator is
-                                    aborting the transaction
-                                  </para>
+            </itemizedlist>
+          </listitem>
 
-                                </formalpara>
-                              </listitem>
+        </itemizedlist>
 
-                              <listitem>
-                                <formalpara>
+        <formalpara>
 
-                                  <title><literal>Scanning</literal></title>
+          <title>Relation to NDB API</title>
 
-                                  <para>
-                                    The transaction coordinator is
-                                    scanning
-                                  </para>
+          <para>
+            It is possible to match the output of <literal>DUMP
+            2350</literal> to specific threads or <literal>Ndb</literal>
+            objects. First suppose that you dump all operations on data
+            node 2 from API node 5, using table 4 only, like this:
+          </para>
 
-                                </formalpara>
-                              </listitem>
+        </formalpara>
 
-                            </itemizedlist>
-                          </para>
-
-                        </formalpara>
-                      </listitem>
-
-                      <listitem>
-                        <formalpara>
-
-                          <title>Scan operations</title>
-
-                          <para>
-                            <itemizedlist>
-
-                              <listitem>
-                                <formalpara>
-
-                                  <title><literal>WaitNextScan</literal></title>
-
-                                  <para>
-                                    The scan is idle, waiting for API
-                                  </para>
-
-                                </formalpara>
-                              </listitem>
-
-                              <listitem>
-                                <formalpara>
-
-                                  <title><literal>InQueue</literal></title>
-
-                                  <para>
-                                    The scan has not yet started, but
-                                    rather is waiting in queue for other
-                                    scans to complete
-                                  </para>
-
-                                </formalpara>
-                              </listitem>
-
-                            </itemizedlist>
-                          </para>
-
-                        </formalpara>
-                      </listitem>
-
-                      <listitem>
-                        <formalpara>
-
-                          <title>Primary key operations</title>
-
-                          <para>
-                            <itemizedlist>
-
-                              <listitem>
-                                <formalpara>
-
-                                  <title><literal>In lock queue</literal></title>
-
-                                  <para>
-                                    The operation is waiting on a lock
-                                  </para>
-
-                                </formalpara>
-                              </listitem>
-
-                              <listitem>
-                                <formalpara>
-
-                                  <title><literal>Running</literal></title>
-
-                                  <para>
-                                    The operation is being prepared
-                                  </para>
-
-                                </formalpara>
-                              </listitem>
-
-                              <listitem>
-                                <formalpara>
-
-                                  <title><literal>Prepared</literal></title>
-
-                                  <para>
-                                    The operation is prepared, holding
-                                    an appropriate lock, and waiting for
-                                    commit or rollback to complete
-                                  </para>
-
-                                </formalpara>
-                              </listitem>
-
-                            </itemizedlist>
-                          </para>
-
-                        </formalpara>
-                      </listitem>
-
-                    </itemizedlist>
-                  </para>
-
-                </formalpara>
-              </listitem>
-
-              <listitem>
-                <formalpara>
-
-                  <title>Relation to NDB API</title>
-
-                  <para>
-                    It is possible to match the output of <literal>DUMP
-                    2350</literal> to specific threads or
-                    <literal>Ndb</literal> objects. First suppose that
-                    you dump all operations on data node 2 from API node
-                    5, using table 4 only, like this:
-
 <programlisting>
 ndb_mgm&gt; <userinput>2 DUMP 2350 1 5 0 4</userinput>
 2006-10-09 13:16:49 [MgmSrvr] INFO     -- Node 2: Starting dump of operations

@@ -3544,39 +3494,33 @@
 2006-10-09 13:16:49 [MgmSrvr] INFO     -- Node 2: End of operation dump
 </programlisting>
 
-                    Suppose you are working with an
-                    <literal>Ndb</literal> instance named
-                    <literal>MyNdb</literal>, to which this operation
-                    belongs. You can see that this is the case by
-                    calling the <literal>Ndb</literal> object's
-                    <literal>getReference()</literal> method, like this:
+        <para>
+          Suppose you are working with an <literal>Ndb</literal>
+          instance named <literal>MyNdb</literal>, to which this
+          operation belongs. You can see that this is the case by
+          calling the <literal>Ndb</literal> object's
+          <literal>getReference()</literal> method, like this:
+        </para>
 
 <programlisting>
   printf("MyNdb.getReference(): 0x%x\n", MyNdb.getReference());
 </programlisting>
 
-                    The output from the preceding line of code is:
+        <para>
+          The output from the preceding line of code is:
+        </para>
 
 <programlisting>
 MyNdb.getReference(): 0x80350005
 </programlisting>
 
-                    The high 16 bits of the value shown corresponds to
-                    the number in parentheses from the
-                    <literal>OP</literal> line in the
-                    <literal>DUMP</literal> command's output (8035). For
-                    more about this method, see
-                    <xref linkend="ndb-ndb-getreference"/>.
-                  </para>
+        <para>
+          The high 16 bits of the value shown corresponds to the number
+          in parentheses from the <literal>OP</literal> line in the
+          <literal>DUMP</literal> command's output (8035). For more
+          about this method, see <xref linkend="ndb-ndb-getreference"/>.
+        </para>
 
-                </formalpara>
-              </listitem>
-
-            </orderedlist>
-          </para>
-
-        </formalpara>
-
         <para>
           This command was added in MySQL Cluster NDB 6.1.12 and MySQL
           Cluster NDB 6.2.2.

@@ -3628,7 +3572,10 @@
             First, obtain a dump of operations. Here, we use
             <literal>DUMP 2350</literal> to get a dump of all operations
             on data node 2 from API node 5:
+          </para>
 
+        </formalpara>
+
 <programlisting>
 ndb_mgm&gt; <userinput>2 DUMP 2350 1 5</userinput>
 2006-10-11 13:31:25 [MgmSrvr] INFO     -- Node 2: Starting dump of operations

@@ -3637,20 +3584,18 @@
 2006-10-11 13:31:25 [MgmSrvr] INFO     -- Node 2: End of operation dump
 </programlisting>
 
-            In this case, there is a single operation reported on node
-            2, whose operation ID is <literal>3</literal>. To obtain the
-            transaction ID and primary key, we use the node ID and
-            operation ID with <literal>DUMP 2352</literal> as shown
-            here:
+        <para>
+          In this case, there is a single operation reported on node 2,
+          whose operation ID is <literal>3</literal>. To obtain the
+          transaction ID and primary key, we use the node ID and
+          operation ID with <literal>DUMP 2352</literal> as shown here:
+        </para>
 
 <programlisting>
 ndb_mgm&gt; <userinput>2 dump 2352 3</userinput>
 2006-10-11 13:31:31 [MgmSrvr] INFO     -- Node 2: OP[3]: transid: 0x3 0x200400 key: 0x2
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>

@@ -3711,7 +3656,10 @@
 
           <para>
             For <literal>2 DUMP 1</literal>:
+          </para>
 
+        </formalpara>
+
 <programlisting>
 Node 2: Dbacc::ScanRec[1]: state=1, transid(0x0, 0x0)
 Node 2:  timer=0, continueBCount=0, activeLocalFrag=0, nextBucketIndex=0

@@ -3719,10 +3667,7 @@
 Node 2:  scanUserP=0, startNoBuck=0, minBucketIndexToRescan=0, maxBucketIndexToRescan=0
 Node 2:  scanBucketState=0, scanLockHeld=0, userBlockRef=0, scanMask=0 scanLockMode=0
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>

@@ -3919,7 +3864,10 @@
 
           <para>
             (For <literal>2 DUMP 1</literal>:)
+          </para>
 
+        </formalpara>
+
 <programlisting>
 Node 2: Dbacc::operationrec[1]: transid(0x0, 0x7f1)
 Node 2: elementIsforward=1, elementPage=0, elementPointer=724

@@ -3931,10 +3879,7 @@
 Node 2: prevSerialQue=-256, scanRecPtr=-256
 Node 2: m_op_bits=0xffffffff, scanBits=0
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>

@@ -4048,7 +3993,10 @@
 
           <para>
             (For <literal>2 DUMP 2405 1</literal>:)
+          </para>
 
+        </formalpara>
+
 <programlisting>
 Time: Saturday 17 February 2007 - 18:33:54
 Status: Temporary error, restart node

@@ -4062,10 +4010,7 @@
 Trace: /usr/local/mysql-5.1/cluster/ndb_2_trace.log.1
 Version: Version 5.1.16 (beta)
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>

@@ -4120,7 +4065,10 @@
 
           <para>
             (For <literal>2 DUMP 2406 1</literal>:)
+          </para>
 
+        </formalpara>
+
 <programlisting>
 Time: Saturday 17 February 2007 - 18:39:16
 Status: Temporary error, restart node

@@ -4134,10 +4082,7 @@
 Trace: /usr/local/mysql-5.1/cluster/ndb_2_trace.log.1
 Version: Version 5.1.16 (beta)
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>

@@ -4260,7 +4205,10 @@
 
           <para>
             (For <literal>2 DUMP 2501 1</literal>:)
+          </para>
 
+        </formalpara>
+
 <programlisting>
 Time: Saturday 17 February 2007 - 18:41:41
 Status: Temporary error, restart node

@@ -4275,10 +4223,7 @@
 Trace: /usr/local/mysql-5.1/cluster/ndb_2_trace.log.1
 Version: Version 5.1.16 (beta)
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>

@@ -4477,17 +4422,17 @@
 
           <para>
             (For <literal>2 DUMP 2504 1</literal>:)
+          </para>
 
+        </formalpara>
+
 <programlisting>
 Node 2: Dbtc::ScanRecord[1]: state=0nextfrag=0, nofrag=0
 Node 2:  ailen=0, para=0, receivedop=0, noOprePperFrag=0
 Node 2:  schv=0, tab=0, sproc=0
 Node 2:  apiRec=-256, next=2
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>

@@ -4495,215 +4440,155 @@
           <para>
             The attributes in the output of this command are described
             as follows:
+          </para>
 
-            <itemizedlist>
+        </formalpara>
 
-              <listitem>
-                <formalpara>
+        <itemizedlist>
 
-                  <title><literal>ScanRecord</literal></title>
+          <listitem>
+            <formalpara>
 
-                  <para>
-                    The scan record slot number (same as
-                    <replaceable>record_id</replaceable>)
-                  </para>
+              <title><literal>ScanRecord</literal></title>
 
-                </formalpara>
-              </listitem>
+              <para>
+                The scan record slot number (same as
+                <replaceable>record_id</replaceable>)
+              </para>
 
-              <listitem>
-                <formalpara>
+            </formalpara>
+          </listitem>
 
-                  <title><literal>state</literal></title>
+          <listitem>
+            <formalpara>
 
-                  <para>
-                    One of the following values (found in as
-                    <literal>ScanState</literal> in
-                    <filename>Dbtc.hpp</filename>):
+              <title><literal>state</literal></title>
 
-                    <informaltable>
-                      <tgroup cols="2">
-                        <colspec colwidth="20*"/>
-                        <colspec colwidth="30*"/>
-                        <tbody>
-                          <row>
-                            <entry><emphasis role="bold">Value</emphasis></entry>
-                            <entry><emphasis role="bold">State</emphasis></entry>
-                          </row>
-                          <row>
-                            <entry>0</entry>
-                            <entry><literal>IDLE</literal></entry>
-                          </row>
-                          <row>
-                            <entry>1</entry>
-                            <entry><literal>WAIT_SCAN_TAB_INFO</literal></entry>
-                          </row>
-                          <row>
-                            <entry>2</entry>
-                            <entry><literal>WAIT_AI</literal></entry>
-                          </row>
-                          <row>
-                            <entry>3</entry>
-                            <entry><literal>WAIT_FRAGMENT_COUNT</literal></entry>
-                          </row>
-                          <row>
-                            <entry>4</entry>
-                            <entry><literal>RUNNING</literal></entry>
-                          </row>
-                          <row>
-                            <entry>5</entry>
-                            <entry><literal>CLOSING_SCAN</literal></entry>
-                          </row>
-                        </tbody>
-                      </tgroup>
-                    </informaltable>
-                  </para>
+              <para>
+                One of the following values (found in as
+                <literal>ScanState</literal> in
+                <filename>Dbtc.hpp</filename>):
 
-                </formalpara>
-              </listitem>
+                <informaltable>
+                  <tgroup cols="2">
+                    <colspec colwidth="20*"/>
+                    <colspec colwidth="30*"/>
+                    <tbody>
+                      <row>
+                        <entry><emphasis role="bold">Value</emphasis></entry>
+                        <entry><emphasis role="bold">State</emphasis></entry>
+                      </row>
+                      <row>
+                        <entry>0</entry>
+                        <entry><literal>IDLE</literal></entry>
+                      </row>
+                      <row>
+                        <entry>1</entry>
+                        <entry><literal>WAIT_SCAN_TAB_INFO</literal></entry>
+                      </row>
+                      <row>
+                        <entry>2</entry>
+                        <entry><literal>WAIT_AI</literal></entry>
+                      </row>
+                      <row>
+                        <entry>3</entry>
+                        <entry><literal>WAIT_FRAGMENT_COUNT</literal></entry>
+                      </row>
+                      <row>
+                        <entry>4</entry>
+                        <entry><literal>RUNNING</literal></entry>
+                      </row>
+                      <row>
+                        <entry>5</entry>
+                        <entry><literal>CLOSING_SCAN</literal></entry>
+                      </row>
+                    </tbody>
+                  </tgroup>
+                </informaltable>
+              </para>
 
-              <listitem>
-                <formalpara>
+            </formalpara>
+          </listitem>
 
-                  <title><literal>nextfrag</literal></title>
+          <listitem>
+            <para>
+              <literal>nextfrag</literal>: ID of the next fragment to be
+              scanned. Used by a scan fragment process when it is ready
+              for the next fragment.
+            </para>
+          </listitem>
 
-                  <para>
-                    ID of the next fragment to be scanned. Used by a
-                    scan fragment process when it is ready for the next
-                    fragment.
-                  </para>
+          <listitem>
+            <para>
+              <literal>nofrag</literal>: Total number of fragments in
+              the table being scanned.
+            </para>
+          </listitem>
 
-                </formalpara>
-              </listitem>
+          <listitem>
+            <para>
+              <literal>ailen</literal>: Length of the expected attribute
+              information.
+            </para>
+          </listitem>
 
-              <listitem>
-                <formalpara>
+          <listitem>
+            <para>
+              <literal>para</literal>: Number of scan frag processes
+              that belonging to this scan.
+            </para>
+          </listitem>
 
-                  <title><literal>nofrag</literal></title>
+          <listitem>
+            <para>
+              <literal>receivedop</literal>: Number of operations
+              received.
+            </para>
+          </listitem>
 
-                  <para>
-                    Total number of fragments in the table being
-                    scanned.
-                  </para>
+          <listitem>
+            <para>
+              <literal>noOprePperFrag</literal>: Maximum number of bytes
+              per batch.
+            </para>
+          </listitem>
 
-                </formalpara>
-              </listitem>
+          <listitem>
+            <para>
+              <literal>schv</literal>: Schema version used by this scan.
+            </para>
+          </listitem>
 
-              <listitem>
-                <formalpara>
+          <listitem>
+            <para>
+              <literal>tab</literal>: The index or table that is
+              scanned.
+            </para>
+          </listitem>
 
-                  <title><literal>ailen</literal></title>
+          <listitem>
+            <para>
+              <literal>sproc</literal>: Index of stored procedure
+              belonging to this scan.
+            </para>
+          </listitem>
 
-                  <para>
-                    Length of the expected attribute information.
-                  </para>
+          <listitem>
+            <para>
+              <literal>apiRec</literal>: Reference to
+              <literal>ApiConnectRecord</literal>
+            </para>
+          </listitem>
 
-                </formalpara>
-              </listitem>
+          <listitem>
+            <para>
+              <literal>next</literal>: Index of next
+              <literal>ScanRecord</literal> in free list
+            </para>
+          </listitem>
 
-              <listitem>
-                <formalpara>
+        </itemizedlist>
 
-                  <title><literal>para</literal></title>
-
-                  <para>
-                    Number of scan frag processes that belonging to this
-                    scan.
-                  </para>
-
-                </formalpara>
-              </listitem>
-
-              <listitem>
-                <formalpara>
-
-                  <title><literal>receivedop</literal></title>
-
-                  <para>
-                    Number of operations received.
-                  </para>
-
-                </formalpara>
-              </listitem>
-
-              <listitem>
-                <formalpara>
-
-                  <title><literal>noOprePperFrag</literal></title>
-
-                  <para>
-                    Maximum number of bytes per batch.
-                  </para>
-
-                </formalpara>
-              </listitem>
-
-              <listitem>
-                <formalpara>
-
-                  <title><literal>schv</literal></title>
-
-                  <para>
-                    Schema version used by this scan.
-                  </para>
-
-                </formalpara>
-              </listitem>
-
-              <listitem>
-                <formalpara>
-
-                  <title><literal>tab</literal></title>
-
-                  <para>
-                    The index or table that is scanned.
-                  </para>
-
-                </formalpara>
-              </listitem>
-
-              <listitem>
-                <formalpara>
-
-                  <title><literal>sproc</literal></title>
-
-                  <para>
-                    Index of stored procedure belonging to this scan.
-                  </para>
-
-                </formalpara>
-              </listitem>
-
-              <listitem>
-                <formalpara>
-
-                  <title><literal>apiRec</literal></title>
-
-                  <para>
-                    Reference to <literal>ApiConnectRecord</literal>
-                  </para>
-
-                </formalpara>
-              </listitem>
-
-              <listitem>
-                <formalpara>
-
-                  <title><literal>next</literal></title>
-
-                  <para>
-                    Index of next <literal>ScanRecord</literal> in free
-                    list
-                  </para>
-
-                </formalpara>
-              </listitem>
-
-            </itemizedlist>
-          </para>
-
-        </formalpara>
-
       </section>
 
       <section id="ndb-internals-dump-command-2505">

@@ -5189,14 +5074,14 @@
 
           <para>
             (Single report:)
+          </para>
 
+        </formalpara>
+
 <programlisting>
 Node 2: IndexOpCount: pool: 8192 free: 8192
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>

@@ -5380,7 +5265,10 @@
 
           <para>
             From the node for which the command is issued:
+          </para>
 
+        </formalpara>
+
 <programlisting>
 Time: Friday 16 February 2007 - 13:52:32
 Status: Temporary error, restart node

@@ -5395,7 +5283,9 @@
 Version: Version 5.1.16 (beta)
 </programlisting>
 
-            From the remaining data nodes:
+        <para>
+          From the remaining data nodes:
+        </para>
 
 <programlisting>
 Time: Friday 16 February 2007 - 13:52:31

@@ -5410,10 +5300,7 @@
 Trace: /usr/local/mysql-5.1/cluster/ndb_3_trace.log.1
 Version: Version 5.1.16 (beta)
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>

@@ -5471,17 +5358,17 @@
           <para>
             Dump all transactions on node 2 which have been inactive for
             30 seconds or longer:
+          </para>
 
+        </formalpara>
+
 <programlisting>
 ndb_mgm&gt; <userinput>2 DUMP 2550 4 30</userinput>
 2006-10-09 13:16:49 [MgmSrvr] INFO     -- Node 2: Starting dump of transactions
 2006-10-09 13:16:49 [MgmSrvr] INFO     -- Node 2: TRX[123]: API: 5(0x8035) transid: 0x31c 0x3500500 inactive: 42s state:
 2006-10-09 13:16:49 [MgmSrvr] INFO     -- Node 2: End of transaction dump
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>

@@ -5491,37 +5378,37 @@
             The filter value must be followed by one or more node IDs
             or, in the case of the last entry in the table, by the time
             in seconds that transactions have been inactive:
-
-            <informaltable>
-              <tgroup cols="2">
-                <colspec colwidth="25*"/>
-                <colspec colwidth="75*"/>
-                <thead>
-                  <row>
-                    <entry>Value</entry>
-                    <entry>Filter</entry>
-                  </row>
-                </thead>
-                <tbody>
-                  <row>
-                    <entry>1</entry>
-                    <entry>API node ID</entry>
-                  </row>
-                  <row>
-                    <entry>2</entry>
-                    <entry>2 transaction IDs, defining a range of transactions</entry>
-                  </row>
-                  <row>
-                    <entry>4</entry>
-                    <entry>time transactions inactive (seconds)</entry>
-                  </row>
-                </tbody>
-              </tgroup>
-            </informaltable>
           </para>
 
         </formalpara>
 
+        <informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="25*"/>
+            <colspec colwidth="75*"/>
+            <thead>
+              <row>
+                <entry>Value</entry>
+                <entry>Filter</entry>
+              </row>
+            </thead>
+            <tbody>
+              <row>
+                <entry>1</entry>
+                <entry>API node ID</entry>
+              </row>
+              <row>
+                <entry>2</entry>
+                <entry>2 transaction IDs, defining a range of transactions</entry>
+              </row>
+              <row>
+                <entry>4</entry>
+                <entry>time transactions inactive (seconds)</entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable>
+
         <para>
           This command was added in MySQL Cluster NDB 6.1.12 and MySQL
           Cluster NDB 6.2.2.

@@ -5862,84 +5749,56 @@
             subscription a header line and a list of categories with
             their current log levels is printed. The following
             information is included in the output:
+          </para>
 
-            <itemizedlist>
+        </formalpara>
 
-              <listitem>
-                <formalpara>
+        <itemizedlist>
 
-                  <title><literal>Subscription</literal></title>
+          <listitem>
+            <para>
+              <literal>Subscription</literal>: The event subscription's
+              internal ID
+            </para>
+          </listitem>
 
-                  <para>
-                    The event subscription's internal ID
-                  </para>
+          <listitem>
+            <para>
+              <literal>nodeID</literal>: Node ID of the subscribing node
+            </para>
+          </listitem>
 
-                </formalpara>
-              </listitem>
+          <listitem>
+            <para>
+              <literal>ref</literal>: A block reference, consisting of a
+              block ID from
+              <filename>storage/ndb/include/kernel/BlockNumbers.h</filename>
+              shifted to the left by 4 hexadecimal digits (16 bits)
+              followed by a 4-digit hexadecimal node number. Block id
+              <literal>0x8000</literal> appears to be a placeholder; it
+              is defined as <literal>MIN_API_BLOCK_NO</literal>, with
+              the node number part being 1 as expected
+            </para>
+          </listitem>
 
-              <listitem>
-                <formalpara>
+          <listitem>
+            <para>
+              <literal>Category</literal>: The cluster log category, as
+              listed in <xref linkend="mysql-cluster-event-reports"/>
+              (see also the file
+              <filename>storage/ndb/include/mgmapi/mgmapi_config_parameters.h</filename>).
+            </para>
+          </listitem>
 
-                  <title><literal>nodeID</literal></title>
+          <listitem>
+            <para>
+              <literal>Level</literal>: The event level setting (the
+              range being 0 to 15).
+            </para>
+          </listitem>
 
-                  <para>
-                    Node ID of the subscribing node
-                  </para>
+        </itemizedlist>
 
-                </formalpara>
-              </listitem>
-
-              <listitem>
-                <formalpara>
-
-                  <title><literal>ref</literal></title>
-
-                  <para>
-                    A block reference, consisting of a block ID from
-                    <filename>storage/ndb/include/kernel/BlockNumbers.h</filename>
-                    shifted to the left by 4 hexadecimal digits (16
-                    bits) followed by a 4-digit hexadecimal node number.
-                    Block id <literal>0x8000</literal> appears to be a
-                    placeholder; it is defined as
-                    <literal>MIN_API_BLOCK_NO</literal>, with the node
-                    number part being 1 as expected
-                  </para>
-
-                </formalpara>
-              </listitem>
-
-              <listitem>
-                <formalpara>
-
-                  <title><literal>Category</literal></title>
-
-                  <para>
-                    The cluster log category, as listed in
-                    <xref linkend="mysql-cluster-event-reports"/> (see
-                    also the file
-                    <filename>storage/ndb/include/mgmapi/mgmapi_config_parameters.h</filename>).
-                  </para>
-
-                </formalpara>
-              </listitem>
-
-              <listitem>
-                <formalpara>
-
-                  <title><literal>Level</literal></title>
-
-                  <para>
-                    The event level setting (the range being 0 to 15).
-                  </para>
-
-                </formalpara>
-              </listitem>
-
-            </itemizedlist>
-          </para>
-
-        </formalpara>
-
       </section>
 
     </section>

@@ -5949,7 +5808,8 @@
       <title><literal>DUMP</literal> Codes 3000 to 3999</title>
 
       <para>
-        Currently unused.
+        <literal>DUMP</literal> codes in this range are currently
+        unused.
       </para>
 
     </section>

@@ -5959,7 +5819,8 @@
       <title><literal>DUMP</literal> Codes 4000 to 4999</title>
 
       <para>
-        Currently unused.
+        <literal>DUMP</literal> codes in this range are currently
+        unused.
       </para>
 
     </section>

@@ -5968,6 +5829,11 @@
 
       <title><literal>DUMP</literal> Codes 5000 to 5999</title>
 
+      <para>
+        This section contains information about <literal>DUMP</literal>
+        codes 5000 through 5999, inclusive.
+      </para>
+
       <section id="ndb-internals-dump-command-5900">
 
         <title><literal>DUMP 5900</literal></title>

@@ -6033,7 +5899,8 @@
       <title><literal>DUMP</literal> Codes 6000 to 6999</title>
 
       <para>
-        Currently unused.
+        <literal>DUMP</literal> codes in this range are currently
+        unused.
       </para>
 
     </section>

@@ -6042,6 +5909,11 @@
 
       <title><literal>DUMP</literal> Codes 7000 to 7999</title>
 
+      <para>
+        This section contains information about <literal>DUMP</literal>
+        codes 7000 through 7999, inclusive.
+      </para>
+
       <section id="ndb-internals-dump-command-7000">
 
         <title><literal>DUMP 7000</literal></title>

@@ -7230,29 +7102,30 @@
           <para>
             This command provides general signal injection
             functionality. Two additional arguments are always required:
+          </para>
 
-            <orderedlist>
+        </formalpara>
 
-              <listitem>
-                <para>
-                  The number of the signal to be sent
-                </para>
-              </listitem>
+        <orderedlist>
 
-              <listitem>
-                <para>
-                  The number of the block to which the signal should be
-                  sent
-                </para>
-              </listitem>
+          <listitem>
+            <para>
+              The number of the signal to be sent
+            </para>
+          </listitem>
 
-            </orderedlist>
+          <listitem>
+            <para>
+              The number of the block to which the signal should be sent
+            </para>
+          </listitem>
 
-            In addition some signals permit or require extra data to be
-            sent.
-          </para>
+        </orderedlist>
 
-        </formalpara>
+        <para>
+          In addition some signals permit or require extra data to be
+          sent.
+        </para>
 
         <formalpara>
 

@@ -7494,33 +7367,33 @@
 
           <para>
             In this example, node 2 is the master node and controls
-            LCP/GCP synchronization for the cluster. regardless of the
+            LCP/GCP synchronization for the cluster. Regardless of the
             <replaceable>node_id</replaceable> specified, only the
-            master node responds.
+            master node responds:
+          </para>
 
+        </formalpara>
+
 <programlisting>
 Node 2: Local checkpoint 7 started. Keep GCI = 1003 oldest restorable GCI = 947
 Node 2: Local checkpoint 7 completed
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>
 
           <para>
             You may need to enable a higher logging level to have the
-            checkpoint's completion reported:
+            checkpoint's completion reported, as shown here:
+          </para>
 
+        </formalpara>
+
 <programlisting>
 ndb_mgmgt; <userinput>ALL CLUSTERLOG CHECKPOINT=8</userinput>
 </programlisting>
-          </para>
 
-        </formalpara>
-
       </section>
 
       <section id="ndb-internals-dump-command-7901">

@@ -7587,6 +7460,11 @@
 
       <title><literal>DUMP</literal> Codes 8000 to 8999</title>
 
+      <para>
+        This section contains information about <literal>DUMP</literal>
+        codes 8000 through 8999, inclusive.
+      </para>
+
       <section id="ndb-internals-dump-command-8004">
 
         <title><literal>DUMP 8004</literal></title>

@@ -7648,11 +7526,10 @@
             stays very low relative to <literal>subscriberPool ...
             size</literal>, it is often a good idea to increase the
             value of the
-            <link linkend="ndbparam-ndbd-maxnooftables"><literal>MaxNoOfTables</literal>
-            configuration parameter</link>
-            (<literal>subscriberPool</literal> = 2 *
-            <literal>MaxNoOfTables</literal>). However, there could also
-            be a problem with API nodes not releasing resources
+            <link linkend="ndbparam-ndbd-maxnooftables"><literal>MaxNoOfTables</literal></link>
+            configuration parameter (<literal>subscriberPool</literal> =
+            2 * <literal>MaxNoOfTables</literal>). However, there could
+            also be a problem with API nodes not releasing resources
             correctly when they are shut down. <literal>DUMP
             8004</literal> provides a way to monitor these values.
           </para>

@@ -7760,7 +7637,10 @@
 
           <para>
             (From cluster log:)
+          </para>
 
+        </formalpara>
+
 <programlisting>
 2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 1: -- Starting dump of subscribers --
 2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 1: Table: 2 ver: 4294967040 #n: 1 (ref,data,subscription)

@@ -7779,10 +7659,7 @@
 2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 2:  [ 80020004 24 2 ]
 2007-11-23 13:17:31 [MgmSrvr] INFO     -- Node 2: -- Ending dump of subscribers --
 </programlisting>
-          </para>
 
-        </formalpara>
-
         <formalpara>
 
           <title>Additional Information</title>

@@ -7801,6 +7678,11 @@
 
       <title><literal>DUMP</literal> Codes 9000 to 9999</title>
 
+      <para>
+        This section contains information about <literal>DUMP</literal>
+        codes 9000 through 9999, inclusive.
+      </para>
+
       <section id="ndb-internals-dump-command-9002">
 
         <title><literal>DUMP 9002</literal></title>

@@ -8137,6 +8019,11 @@
 
       <title><literal>DUMP</literal> Codes 10000 to 10999</title>
 
+      <para>
+        This section contains information about <literal>DUMP</literal>
+        codes 10000 through 10999, inclusive.
+      </para>
+
       <section id="ndb-internals-dump-command-10000">
 
         <title><literal>DUMP 10000</literal></title>

@@ -8201,6 +8088,11 @@
 
       <title><literal>DUMP</literal> Codes 11000 to 11999</title>
 
+      <para>
+        This section contains information about <literal>DUMP</literal>
+        codes 11000 through 11999, inclusive.
+      </para>
+
       <section id="ndb-internals-dump-command-11000">
 
         <title><literal>DUMP 11000</literal></title>

@@ -8265,6 +8157,11 @@
 
       <title><literal>DUMP</literal> Codes 12000 to 12999</title>
 
+      <para>
+        This section contains information about <literal>DUMP</literal>
+        codes 12000 through 12999, inclusive.
+      </para>
+
       <section id="ndb-internals-dump-command-12001">
 
         <title><literal>DUMP 12001</literal></title>

@@ -8453,6 +8350,8 @@
 
   </section>
 
+<!--  DEGUNKING THROUGH HERE  -->
+
   <section id="ndb-internals-ndb-protocol">
 
     <title>The NDB Protocol</title>


Thread
svn commit - mysqldoc@docsrva: r22979 - trunk/ndbapijon.stephens5 Oct