svn commit - mysqldoc@docsrva: r4669 - branches/telcos/refman-5.1 trunk/refman-4.1 trunk/refman-5.0 trunk/refman-5.1

[jon]

Author: jstephens
Date: 2007-01-27 03:49:02 +0100 (Sat, 27 Jan 2007)
New Revision: 4669

Log:

Updated and added more info about cluster logging.



Modified:
   branches/telcos/refman-5.1/mysql-cluster.xml
   trunk/refman-4.1/mysql-cluster.xml
   trunk/refman-5.0/mysql-cluster.xml
   trunk/refman-5.1/mysql-cluster.xml


Modified: branches/telcos/refman-5.1/mysql-cluster.xml
===================================================================
--- branches/telcos/refman-5.1/mysql-cluster.xml	2007-01-27 00:51:18 UTC (rev 4668)
+++ branches/telcos/refman-5.1/mysql-cluster.xml	2007-01-27 02:49:02 UTC (rev 4669)
Changed blocks: 2, Lines Added: 129, Lines Deleted: 20; 7390 bytes

@@ -10810,33 +10810,66 @@
       </para>
 
       <para>
-        MySQL Cluster provides two types of event log. These are the
-        <firstterm>cluster log</firstterm>, which includes events
-        generated by all cluster nodes, and the <firstterm>node
-        logs</firstterm>, which are local to each data node.
+        MySQL Cluster provides two types of event log:
       </para>
+      
+      <itemizedlist>
+        <listitem>
+          <para>
+            The <firstterm>cluster log</firstterm>, which includes
+            events generated by all cluster nodes. The cluster log is
+            the log recommended for most uses because it provides
+            logging information for an entire cluster in a single
+            location.
+          </para>
+          
+          <para>
+            By default, the cluster log is saved to a file named
+           
<filename>ndb_<replaceable>node_id</replaceable>_cluster.log</filename>,
+            (where <replaceable>node_id</replaceable> is the node ID of
+            the management server) in the same directory where the
+            <command>ndb_mgm</command> binary resides.
+          </para>
+          
+          <para>
+            Cluster logging information can also be sent to
+            <literal>stdout</literal> or a
<literal>syslog</literal>
+            facility in addition to or instead of being saved to a file,
+            as determined by the values set for the
+            <literal>DataDir</literal> and
+            <literal>LogDestination</literal> configuration parameters. 
+            See <xref linkend="mysql-cluster-mgm-definition"/>, for
+            more information about these parameters.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            <firstterm>Node logs</firstterm> are local to each node.
+          </para>
+          
+          <para>
+            Output generated by node event logging is written to the
+            file
+           
<filename>ndb_<replaceable>node_id</replaceable>_out.log</filename>
+            (where <replaceable>node_id</replaceable> is the node's node
+            ID) in the node's <literal>DataDir</literal>. Node event
+            logs are generated for both management nodes and data nodes. 
+          </para>
+          
+          <para>
+            Node logs are intended to be used only during application
+            development, or for debugging application code.
+          </para>
+        </listitem>
+      </itemizedlist>
 
       <para>
-        Output generated by cluster event logging can have multiple
-        destinations including a file, the management server console
-        window, or <literal>syslog</literal>. Output generated by node
-        event logging is written to the data node's console window.
-      </para>
-
-      <para>
         Both types of event logs can be set to log different subsets of
         events.
       </para>
 
       <para>
-        <emphasis role="bold">Note</emphasis>: The cluster log is the
-        log recommended for most uses because it provides logging
-        information for an entire cluster in a single file. Node logs
-        are intended to be used only during application development, or
-        for debugging application code.
-      </para>
-
-      <para>
         Each reportable event can be distinguished according to three
         different criteria:
       </para>

@@ -10889,7 +10922,83 @@
         Both the cluster log and the node log can be filtered on these
         properties.
       </para>
-
+      
+      <para>
+        The format used in the cluster log is as shown here:
+      </para>
+      
+<programlisting>
[phone]:35:55 [MgmSrvr] INFO     -- Node 1: Data usage is 2%(60 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 1: Index usage is 1%(24 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 1: Resource 0 min: 0 max: 639 curr: 0
[phone]:35:55 [MgmSrvr] INFO     -- Node 2: Data usage is 2%(76 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 2: Index usage is 1%(24 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 2: Resource 0 min: 0 max: 639 curr: 0
[phone]:35:55 [MgmSrvr] INFO     -- Node 3: Data usage is 2%(58 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 3: Index usage is 1%(25 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 3: Resource 0 min: 0 max: 639 curr: 0
[phone]:35:55 [MgmSrvr] INFO     -- Node 4: Data usage is 2%(74 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 4: Index usage is 1%(25 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 4: Resource 0 min: 0 max: 639 curr: 0
[phone]:39:42 [MgmSrvr] INFO     -- Node 4: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 1: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 1: Node 9: API version 5.1.15
[phone]:39:42 [MgmSrvr] INFO     -- Node 2: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 2: Node 9: API version 5.1.15
[phone]:39:42 [MgmSrvr] INFO     -- Node 3: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 3: Node 9: API version 5.1.15
[phone]:39:42 [MgmSrvr] INFO     -- Node 4: Node 9: API version 5.1.15
[phone]:59:22 [MgmSrvr] ALERT    -- Node 2: Node 7 Disconnected
[phone]:59:22 [MgmSrvr] ALERT    -- Node 2: Node 7 Disconnected
+</programlisting>
+      
+      <para>
+        Each line in the cluster log contains the following information:
+      </para>
+      
+      <itemizedlist>
+        <listitem>
+          <para>
+            A timestamp in
+           
<literal><replaceable>YYYY</replaceable>-<replaceable>MM</replaceable>-<replaceable>DD</replaceable>
+             
<replaceable>HH</replaceable>:<replaceable>MM</replaceable>:<replaceable>SS</replaceable></literal>
+            format. 
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The type of node which is performing the logging. In the
+            cluster log, this is always <literal>[MgmSrvr]</literal>. 
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The severity of the event.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The ID of the node reporting the event.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            A description of the event. The most common types of events
+            to appear in the log are connections and disconnections 
+            between different nodes in the cluster, and when checkpoints
+            occur. In some cases, the description may contain status
+            information, such as that generated when the
+            <literal>CLUSTERLOG STATISTICS</literal> command is issued 
+            in the management client.
+          </para>
+        </listitem>
+      </itemizedlist>
+      
+      
       <section id="mysql-cluster-logging-management-commands">
 
         <title>Logging Management Commands</title>


Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml	2007-01-27 00:51:18 UTC (rev 4668)
+++ trunk/refman-4.1/mysql-cluster.xml	2007-01-27 02:49:02 UTC (rev 4669)
Changed blocks: 3, Lines Added: 140, Lines Deleted: 32; 8651 bytes

@@ -10581,55 +10581,88 @@
         <primary>MySQL Cluster</primary>
         <secondary>node logs</secondary>
       </indexterm>
-
+      
       <para>
         In this section, we discuss the types of event logs provided by
         MySQL Cluster, and the types of events that are logged.
       </para>
-
+      
       <para>
-        MySQL Cluster provides two types of event log. These are the
-        <firstterm>cluster log</firstterm>, which includes events
-        generated by all cluster nodes, and the <firstterm>node
-        logs</firstterm>, which are local to each data node.
+        MySQL Cluster provides two types of event log:
       </para>
-
+      
+      <itemizedlist>
+        <listitem>
+          <para>
+            The <firstterm>cluster log</firstterm>, which includes
+            events generated by all cluster nodes. The cluster log is
+            the log recommended for most uses because it provides
+            logging information for an entire cluster in a single
+            location.
+          </para>
+          
+          <para>
+            By default, the cluster log is saved to a file named
+           
<filename>ndb_<replaceable>node_id</replaceable>_cluster.log</filename>,
+            (where <replaceable>node_id</replaceable> is the node ID of
+            the management server) in the same directory where the
+            <command>ndb_mgm</command> binary resides.
+          </para>
+          
+          <para>
+            Cluster logging information can also be sent to
+            <literal>stdout</literal> or a
<literal>syslog</literal>
+            facility in addition to or instead of being saved to a file,
+            as determined by the values set for the
+            <literal>DataDir</literal> and
+            <literal>LogDestination</literal> configuration parameters. 
+            See <xref linkend="mysql-cluster-mgm-definition"/>, for
+            more information about these parameters.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            <firstterm>Node logs</firstterm> are local to each node.
+          </para>
+          
+          <para>
+            Output generated by node event logging is written to the
+            file
+           
<filename>ndb_<replaceable>node_id</replaceable>_out.log</filename>
+            (where <replaceable>node_id</replaceable> is the node's node
+            ID) in the node's <literal>DataDir</literal>. Node event
+            logs are generated for both management nodes and data nodes. 
+          </para>
+          
+          <para>
+            Node logs are intended to be used only during application
+            development, or for debugging application code.
+          </para>
+        </listitem>
+      </itemizedlist>
+      
       <para>
-        Output generated by cluster event logging can have multiple
-        destinations including a file, the management server console
-        window, or <literal>syslog</literal>. Output generated by node
-        event logging is written to the data node's console window.
-      </para>
-
-      <para>
         Both types of event logs can be set to log different subsets of
         events.
       </para>
-
+      
       <para>
-        <emphasis role="bold">Note</emphasis>: The cluster log is the
-        log recommended for most uses because it provides logging
-        information for an entire cluster in a single file. Node logs
-        are intended to be used only during application development, or
-        for debugging application code.
-      </para>
-
-      <para>
         Each reportable event can be distinguished according to three
         different criteria:
       </para>
-
+      
       <indexterm>
         <primary>MySQL Cluster</primary>
         <secondary>event types</secondary>
       </indexterm>
-
+      
       <indexterm>
         <primary>event types (MySQL Cluster)</primary>
       </indexterm>
-
+      
       <itemizedlist>
-
+        
         <listitem>
           <para>
             <emphasis>Category</emphasis>: This can be any one of the

@@ -10641,16 +10674,16 @@
             <literal>INFO</literal>.
           </para>
         </listitem>
-
+        
         <listitem>
           <para>
             <emphasis>Priority</emphasis>: This is represented by one of
             the numbers from 1 to 15 inclusive, where 1 indicates
             <quote>most important</quote> and 15 <quote>least
-            important.</quote>
+              important.</quote>
           </para>
         </listitem>
-
+        
         <listitem>
           <para>
             <emphasis>Severity Level</emphasis>: This can be any one of

@@ -10660,13 +10693,88 @@
             <literal>DEBUG</literal>.
           </para>
         </listitem>
-
+        
       </itemizedlist>
-
+      
       <para>
         Both the cluster log and the node log can be filtered on these
         properties.
       </para>
+      
+      <para>
+        The format used in the cluster log is as shown here:
+      </para>
+      
+      <programlisting>
[phone]:35:55 [MgmSrvr] INFO     -- Node 1: Data usage is 2%(60 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 1: Index usage is 1%(24 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 1: Resource 0 min: 0 max: 639 curr: 0
[phone]:35:55 [MgmSrvr] INFO     -- Node 2: Data usage is 2%(76 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 2: Index usage is 1%(24 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 2: Resource 0 min: 0 max: 639 curr: 0
[phone]:35:55 [MgmSrvr] INFO     -- Node 3: Data usage is 2%(58 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 3: Index usage is 1%(25 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 3: Resource 0 min: 0 max: 639 curr: 0
[phone]:35:55 [MgmSrvr] INFO     -- Node 4: Data usage is 2%(74 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 4: Index usage is 1%(25 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 4: Resource 0 min: 0 max: 639 curr: 0
[phone]:39:42 [MgmSrvr] INFO     -- Node 4: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 1: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 1: Node 9: API version 5.1.15
[phone]:39:42 [MgmSrvr] INFO     -- Node 2: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 2: Node 9: API version 5.1.15
[phone]:39:42 [MgmSrvr] INFO     -- Node 3: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 3: Node 9: API version 5.1.15
[phone]:39:42 [MgmSrvr] INFO     -- Node 4: Node 9: API version 5.1.15
[phone]:59:22 [MgmSrvr] ALERT    -- Node 2: Node 7 Disconnected
[phone]:59:22 [MgmSrvr] ALERT    -- Node 2: Node 7 Disconnected
+</programlisting>
+      
+      <para>
+        Each line in the cluster log contains the following information:
+      </para>
+      
+      <itemizedlist>
+        <listitem>
+          <para>
+            A timestamp in
+           
<literal><replaceable>YYYY</replaceable>-<replaceable>MM</replaceable>-<replaceable>DD</replaceable>
+             
<replaceable>HH</replaceable>:<replaceable>MM</replaceable>:<replaceable>SS</replaceable></literal>
+            format. 
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The type of node which is performing the logging. In the
+            cluster log, this is always <literal>[MgmSrvr]</literal>. 
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The severity of the event.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The ID of the node reporting the event.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            A description of the event. The most common types of events
+            to appear in the log are connections and disconnections 
+            between different nodes in the cluster, and when checkpoints
+            occur. In some cases, the description may contain status
+            information, such as that generated when the
+            <literal>CLUSTERLOG STATISTICS</literal> command is issued 
+            in the management client.
+          </para>
+        </listitem>
+      </itemizedlist>
 
       <section id="mysql-cluster-logging-management-commands">
 


Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml	2007-01-27 00:51:18 UTC (rev 4668)
+++ trunk/refman-5.0/mysql-cluster.xml	2007-01-27 02:49:02 UTC (rev 4669)
Changed blocks: 3, Lines Added: 140, Lines Deleted: 32; 8651 bytes

@@ -10694,55 +10694,88 @@
         <primary>MySQL Cluster</primary>
         <secondary>node logs</secondary>
       </indexterm>
-
+      
       <para>
         In this section, we discuss the types of event logs provided by
         MySQL Cluster, and the types of events that are logged.
       </para>
-
+      
       <para>
-        MySQL Cluster provides two types of event log. These are the
-        <firstterm>cluster log</firstterm>, which includes events
-        generated by all cluster nodes, and the <firstterm>node
-        logs</firstterm>, which are local to each data node.
+        MySQL Cluster provides two types of event log:
       </para>
-
+      
+      <itemizedlist>
+        <listitem>
+          <para>
+            The <firstterm>cluster log</firstterm>, which includes
+            events generated by all cluster nodes. The cluster log is
+            the log recommended for most uses because it provides
+            logging information for an entire cluster in a single
+            location.
+          </para>
+          
+          <para>
+            By default, the cluster log is saved to a file named
+           
<filename>ndb_<replaceable>node_id</replaceable>_cluster.log</filename>,
+            (where <replaceable>node_id</replaceable> is the node ID of
+            the management server) in the same directory where the
+            <command>ndb_mgm</command> binary resides.
+          </para>
+          
+          <para>
+            Cluster logging information can also be sent to
+            <literal>stdout</literal> or a
<literal>syslog</literal>
+            facility in addition to or instead of being saved to a file,
+            as determined by the values set for the
+            <literal>DataDir</literal> and
+            <literal>LogDestination</literal> configuration parameters. 
+            See <xref linkend="mysql-cluster-mgm-definition"/>, for
+            more information about these parameters.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            <firstterm>Node logs</firstterm> are local to each node.
+          </para>
+          
+          <para>
+            Output generated by node event logging is written to the
+            file
+           
<filename>ndb_<replaceable>node_id</replaceable>_out.log</filename>
+            (where <replaceable>node_id</replaceable> is the node's node
+            ID) in the node's <literal>DataDir</literal>. Node event
+            logs are generated for both management nodes and data nodes. 
+          </para>
+          
+          <para>
+            Node logs are intended to be used only during application
+            development, or for debugging application code.
+          </para>
+        </listitem>
+      </itemizedlist>
+      
       <para>
-        Output generated by cluster event logging can have multiple
-        destinations including a file, the management server console
-        window, or <literal>syslog</literal>. Output generated by node
-        event logging is written to the data node's console window.
-      </para>
-
-      <para>
         Both types of event logs can be set to log different subsets of
         events.
       </para>
-
+      
       <para>
-        <emphasis role="bold">Note</emphasis>: The cluster log is the
-        log recommended for most uses because it provides logging
-        information for an entire cluster in a single file. Node logs
-        are intended to be used only during application development, or
-        for debugging application code.
-      </para>
-
-      <para>
         Each reportable event can be distinguished according to three
         different criteria:
       </para>
-
+      
       <indexterm>
         <primary>MySQL Cluster</primary>
         <secondary>event types</secondary>
       </indexterm>
-
+      
       <indexterm>
         <primary>event types (MySQL Cluster)</primary>
       </indexterm>
-
+      
       <itemizedlist>
-
+        
         <listitem>
           <para>
             <emphasis>Category</emphasis>: This can be any one of the

@@ -10754,16 +10787,16 @@
             <literal>INFO</literal>.
           </para>
         </listitem>
-
+        
         <listitem>
           <para>
             <emphasis>Priority</emphasis>: This is represented by one of
             the numbers from 1 to 15 inclusive, where 1 indicates
             <quote>most important</quote> and 15 <quote>least
-            important.</quote>
+              important.</quote>
           </para>
         </listitem>
-
+        
         <listitem>
           <para>
             <emphasis>Severity Level</emphasis>: This can be any one of

@@ -10773,13 +10806,88 @@
             <literal>DEBUG</literal>.
           </para>
         </listitem>
-
+        
       </itemizedlist>
-
+      
       <para>
         Both the cluster log and the node log can be filtered on these
         properties.
       </para>
+      
+      <para>
+        The format used in the cluster log is as shown here:
+      </para>
+      
+      <programlisting>
[phone]:35:55 [MgmSrvr] INFO     -- Node 1: Data usage is 2%(60 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 1: Index usage is 1%(24 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 1: Resource 0 min: 0 max: 639 curr: 0
[phone]:35:55 [MgmSrvr] INFO     -- Node 2: Data usage is 2%(76 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 2: Index usage is 1%(24 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 2: Resource 0 min: 0 max: 639 curr: 0
[phone]:35:55 [MgmSrvr] INFO     -- Node 3: Data usage is 2%(58 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 3: Index usage is 1%(25 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 3: Resource 0 min: 0 max: 639 curr: 0
[phone]:35:55 [MgmSrvr] INFO     -- Node 4: Data usage is 2%(74 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 4: Index usage is 1%(25 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 4: Resource 0 min: 0 max: 639 curr: 0
[phone]:39:42 [MgmSrvr] INFO     -- Node 4: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 1: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 1: Node 9: API version 5.1.15
[phone]:39:42 [MgmSrvr] INFO     -- Node 2: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 2: Node 9: API version 5.1.15
[phone]:39:42 [MgmSrvr] INFO     -- Node 3: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 3: Node 9: API version 5.1.15
[phone]:39:42 [MgmSrvr] INFO     -- Node 4: Node 9: API version 5.1.15
[phone]:59:22 [MgmSrvr] ALERT    -- Node 2: Node 7 Disconnected
[phone]:59:22 [MgmSrvr] ALERT    -- Node 2: Node 7 Disconnected
+</programlisting>
+      
+      <para>
+        Each line in the cluster log contains the following information:
+      </para>
+      
+      <itemizedlist>
+        <listitem>
+          <para>
+            A timestamp in
+           
<literal><replaceable>YYYY</replaceable>-<replaceable>MM</replaceable>-<replaceable>DD</replaceable>
+             
<replaceable>HH</replaceable>:<replaceable>MM</replaceable>:<replaceable>SS</replaceable></literal>
+            format. 
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The type of node which is performing the logging. In the
+            cluster log, this is always <literal>[MgmSrvr]</literal>. 
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The severity of the event.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The ID of the node reporting the event.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            A description of the event. The most common types of events
+            to appear in the log are connections and disconnections 
+            between different nodes in the cluster, and when checkpoints
+            occur. In some cases, the description may contain status
+            information, such as that generated when the
+            <literal>CLUSTERLOG STATISTICS</literal> command is issued 
+            in the management client.
+          </para>
+        </listitem>
+      </itemizedlist>
 
       <section id="mysql-cluster-logging-management-commands">
 


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2007-01-27 00:51:18 UTC (rev 4668)
+++ trunk/refman-5.1/mysql-cluster.xml	2007-01-27 02:49:02 UTC (rev 4669)
Changed blocks: 3, Lines Added: 140, Lines Deleted: 32; 8651 bytes

@@ -10747,55 +10747,88 @@
         <primary>MySQL Cluster</primary>
         <secondary>node logs</secondary>
       </indexterm>
-
+      
       <para>
         In this section, we discuss the types of event logs provided by
         MySQL Cluster, and the types of events that are logged.
       </para>
-
+      
       <para>
-        MySQL Cluster provides two types of event log. These are the
-        <firstterm>cluster log</firstterm>, which includes events
-        generated by all cluster nodes, and the <firstterm>node
-        logs</firstterm>, which are local to each data node.
+        MySQL Cluster provides two types of event log:
       </para>
-
+      
+      <itemizedlist>
+        <listitem>
+          <para>
+            The <firstterm>cluster log</firstterm>, which includes
+            events generated by all cluster nodes. The cluster log is
+            the log recommended for most uses because it provides
+            logging information for an entire cluster in a single
+            location.
+          </para>
+          
+          <para>
+            By default, the cluster log is saved to a file named
+           
<filename>ndb_<replaceable>node_id</replaceable>_cluster.log</filename>,
+            (where <replaceable>node_id</replaceable> is the node ID of
+            the management server) in the same directory where the
+            <command>ndb_mgm</command> binary resides.
+          </para>
+          
+          <para>
+            Cluster logging information can also be sent to
+            <literal>stdout</literal> or a
<literal>syslog</literal>
+            facility in addition to or instead of being saved to a file,
+            as determined by the values set for the
+            <literal>DataDir</literal> and
+            <literal>LogDestination</literal> configuration parameters. 
+            See <xref linkend="mysql-cluster-mgm-definition"/>, for
+            more information about these parameters.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            <firstterm>Node logs</firstterm> are local to each node.
+          </para>
+          
+          <para>
+            Output generated by node event logging is written to the
+            file
+           
<filename>ndb_<replaceable>node_id</replaceable>_out.log</filename>
+            (where <replaceable>node_id</replaceable> is the node's node
+            ID) in the node's <literal>DataDir</literal>. Node event
+            logs are generated for both management nodes and data nodes. 
+          </para>
+          
+          <para>
+            Node logs are intended to be used only during application
+            development, or for debugging application code.
+          </para>
+        </listitem>
+      </itemizedlist>
+      
       <para>
-        Output generated by cluster event logging can have multiple
-        destinations including a file, the management server console
-        window, or <literal>syslog</literal>. Output generated by node
-        event logging is written to the data node's console window.
-      </para>
-
-      <para>
         Both types of event logs can be set to log different subsets of
         events.
       </para>
-
+      
       <para>
-        <emphasis role="bold">Note</emphasis>: The cluster log is the
-        log recommended for most uses because it provides logging
-        information for an entire cluster in a single file. Node logs
-        are intended to be used only during application development, or
-        for debugging application code.
-      </para>
-
-      <para>
         Each reportable event can be distinguished according to three
         different criteria:
       </para>
-
+      
       <indexterm>
         <primary>MySQL Cluster</primary>
         <secondary>event types</secondary>
       </indexterm>
-
+      
       <indexterm>
         <primary>event types (MySQL Cluster)</primary>
       </indexterm>
-
+      
       <itemizedlist>
-
+        
         <listitem>
           <para>
             <emphasis>Category</emphasis>: This can be any one of the

@@ -10807,16 +10840,16 @@
             <literal>INFO</literal>.
           </para>
         </listitem>
-
+        
         <listitem>
           <para>
             <emphasis>Priority</emphasis>: This is represented by one of
             the numbers from 1 to 15 inclusive, where 1 indicates
             <quote>most important</quote> and 15 <quote>least
-            important.</quote>
+              important.</quote>
           </para>
         </listitem>
-
+        
         <listitem>
           <para>
             <emphasis>Severity Level</emphasis>: This can be any one of

@@ -10826,13 +10859,88 @@
             <literal>DEBUG</literal>.
           </para>
         </listitem>
-
+        
       </itemizedlist>
-
+      
       <para>
         Both the cluster log and the node log can be filtered on these
         properties.
       </para>
+      
+      <para>
+        The format used in the cluster log is as shown here:
+      </para>
+      
+      <programlisting>
[phone]:35:55 [MgmSrvr] INFO     -- Node 1: Data usage is 2%(60 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 1: Index usage is 1%(24 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 1: Resource 0 min: 0 max: 639 curr: 0
[phone]:35:55 [MgmSrvr] INFO     -- Node 2: Data usage is 2%(76 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 2: Index usage is 1%(24 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 2: Resource 0 min: 0 max: 639 curr: 0
[phone]:35:55 [MgmSrvr] INFO     -- Node 3: Data usage is 2%(58 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 3: Index usage is 1%(25 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 3: Resource 0 min: 0 max: 639 curr: 0
[phone]:35:55 [MgmSrvr] INFO     -- Node 4: Data usage is 2%(74 32K pages of total
2560)
[phone]:35:55 [MgmSrvr] INFO     -- Node 4: Index usage is 1%(25 8K pages of total
2336)
[phone]:35:55 [MgmSrvr] INFO     -- Node 4: Resource 0 min: 0 max: 639 curr: 0
[phone]:39:42 [MgmSrvr] INFO     -- Node 4: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 1: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 1: Node 9: API version 5.1.15
[phone]:39:42 [MgmSrvr] INFO     -- Node 2: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 2: Node 9: API version 5.1.15
[phone]:39:42 [MgmSrvr] INFO     -- Node 3: Node 9 Connected
[phone]:39:42 [MgmSrvr] INFO     -- Node 3: Node 9: API version 5.1.15
[phone]:39:42 [MgmSrvr] INFO     -- Node 4: Node 9: API version 5.1.15
[phone]:59:22 [MgmSrvr] ALERT    -- Node 2: Node 7 Disconnected
[phone]:59:22 [MgmSrvr] ALERT    -- Node 2: Node 7 Disconnected
+</programlisting>
+      
+      <para>
+        Each line in the cluster log contains the following information:
+      </para>
+      
+      <itemizedlist>
+        <listitem>
+          <para>
+            A timestamp in
+           
<literal><replaceable>YYYY</replaceable>-<replaceable>MM</replaceable>-<replaceable>DD</replaceable>
+             
<replaceable>HH</replaceable>:<replaceable>MM</replaceable>:<replaceable>SS</replaceable></literal>
+            format. 
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The type of node which is performing the logging. In the
+            cluster log, this is always <literal>[MgmSrvr]</literal>. 
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The severity of the event.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            The ID of the node reporting the event.
+          </para>
+        </listitem>
+        
+        <listitem>
+          <para>
+            A description of the event. The most common types of events
+            to appear in the log are connections and disconnections 
+            between different nodes in the cluster, and when checkpoints
+            occur. In some cases, the description may contain status
+            information, such as that generated when the
+            <literal>CLUSTERLOG STATISTICS</literal> command is issued 
+            in the management client.
+          </para>
+        </listitem>
+      </itemizedlist>
 
       <section id="mysql-cluster-logging-management-commands">