Author: jstephens
Date: 2008-07-22 12:21:18 +0200 (Tue, 22 Jul 2008)
New Revision: 11307
Log:
Deployed NDB Log Messages section (WL#3798).
Updated dependencies.
Removed:
trunk/refman-5.1/mysql-cluster-log-messages-tmp.xml
Modified:
trunk/refman-4.1/Makefile.depends
trunk/refman-4.1/mysql-cluster-management.xml
trunk/refman-5.0/Makefile.depends
trunk/refman-5.0/mysql-cluster-management.xml
trunk/refman-5.1/Makefile.depends
trunk/refman-5.1/mysql-cluster-management.xml
Modified: trunk/refman-4.1/Makefile.depends
===================================================================
--- trunk/refman-4.1/Makefile.depends 2008-07-22 08:33:38 UTC (rev 11306)
+++ trunk/refman-4.1/Makefile.depends 2008-07-22 10:21:18 UTC (rev 11307)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 0; 1275 bytes
@@ -1080,6 +1080,7 @@
../refman-common/images/published/rolling-restarts.png
manual_SOURCES = manual.xml $(manual_INCLUDES)
manual_IDMAPS = \
+ ../ndbapi/metadata/mgm-api.idmap \
../ndbapi/metadata/ndb-errors.idmap \
../ndbapi/metadata/ndb-internals.idmap \
../ndbapi/metadata/ndbapi.idmap \
@@ -1305,6 +1306,8 @@
mysql_cluster_management_IMAGES =
mysql_cluster_management_SOURCES = mysql-cluster-management.xml $(mysql_cluster_management_INCLUDES)
mysql_cluster_management_IDMAPS = \
+ ../ndbapi/metadata/mgm-api.idmap \
+ ../ndbapi/metadata/ndb-errors.idmap \
../ndbapi/metadata/ndb-internals.idmap \
../refman-4.1/metadata/dba-core.idmap \
../refman-4.1/metadata/mysql-cluster-backup.idmap \
@@ -1547,6 +1550,7 @@
../refman-common/images/published/rolling-restarts.png
mysql_cluster_SOURCES = mysql-cluster.xml $(mysql_cluster_INCLUDES)
mysql_cluster_IDMAPS = \
+ ../ndbapi/metadata/mgm-api.idmap \
../ndbapi/metadata/ndb-errors.idmap \
../ndbapi/metadata/ndb-internals.idmap \
../ndbapi/metadata/ndbapi.idmap \
Modified: trunk/refman-4.1/mysql-cluster-management.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster-management.xml 2008-07-22 08:33:38 UTC (rev 11306)
+++ trunk/refman-4.1/mysql-cluster-management.xml 2008-07-22 10:21:18 UTC (rev 11307)
Changed blocks: 1, Lines Added: 4192, Lines Deleted: 0; 115864 bytes
@@ -2234,6 +2234,4198 @@
</section>
+ <section id="mysql-cluster-logs-ndb-messages">
+
+ <title><literal>NDB</literal> Log Messages</title>
+
+ <para>
+ This section contains information about the messages written to
+ the cluster log in response to different cluster log events. It
+ provides additional, more specific information on
+ <literal>NDB</literal> transporter errors.
+ </para>
+
+ <section id="mysql-cluster-logs-cluster-log">
+
+ <title>Messages in the Cluster Log</title>
+
+ <para>
+ The following table lists the most common <literal>NDB</literal>
+ cluster log messages. For information about the cluster log, log
+ events, and event types, see
+ <xref linkend="mysql-cluster-event-reports"/>. These log
+ messages also correspond to log event types in the MGM API; see
+ <xref linkend="ndb-logevent-type"/>, for related information of
+ interest to Cluster API developers.
+ </para>
+
+ <informaltable>
+ <tgroup cols="2">
+ <colspec colwidth="60*"/>
+ <colspec colwidth="40*"/>
+ <tbody>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node
+ <replaceable>mgm_node_id</replaceable>: Node
+ <replaceable>data_node_id</replaceable>
+ Connected</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The data node having node ID
+ <replaceable>node_id</replaceable> has connected to
+ the management server (node
+ <replaceable>mgm_node_id</replaceable>).
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>Connected</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Connection</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node
+ <replaceable>mgm_node_id</replaceable>: Node
+ <replaceable>data_node_id</replaceable>
+ Disconnected</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The data node having node ID
+ <replaceable>data_node_id</replaceable> has
+ disconnected from the management server (node
+ <replaceable>mgm_node_id</replaceable>).
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>Disconnected</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Connection</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node
+ <replaceable>data_node_id</replaceable>:
+ Communication to Node
+ <replaceable>api_node_id</replaceable>
+ closed</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The API node or SQL node having node ID
+ <replaceable>api_node_id</replaceable> is no longer
+ communicating with data node
+ <replaceable>data_node_id</replaceable>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>CommunicationClosed</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Connection</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node
+ <replaceable>data_node_id</replaceable>:
+ Communication to Node
+ <replaceable>api_node_id</replaceable>
+ opened</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The API node or SQL node having node ID
+ <replaceable>api_node_id</replaceable> is now
+ communicating with data node
+ <replaceable>data_node_id</replaceable>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>CommunicationOpened</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Connection</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node
+ <replaceable>mgm_node_id</replaceable>: Node
+ <replaceable>api_node_id</replaceable>: API
+ <replaceable>version</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The API node having node ID
+ <replaceable>api_node_id</replaceable> has connected
+ to management node
+ <replaceable>mgm_node_id</replaceable> using
+ <literal>NDB</literal> API version
+ <replaceable>version</replaceable> (generally the
+ same as the MySQL version number).
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>ConnectedApiVersion</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Connection</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Global checkpoint <replaceable>gci</replaceable>
+ started</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A global checkpoint with the ID
+ <replaceable>gci</replaceable> has been started;
+ node <replaceable>node_id</replaceable> is the
+ master responsible for this global checkpoint.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>GlobalCheckpointStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 9
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Global checkpoint <replaceable>gci</replaceable>
+ completed</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The global checkpoint having the ID
+ <replaceable>gci</replaceable> has been completed;
+ node <replaceable>node_id</replaceable> was the
+ master responsible for this global checkpoint.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>GlobalCheckpointCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 10
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Local checkpoint <replaceable>lcp</replaceable>
+ started. Keep GCI =
+ <replaceable>current_gci</replaceable> oldest
+ restorable GCI =
+ <replaceable>old_gci</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The local checkpoint having sequence ID
+ <replaceable>lcp</replaceable> has been started on
+ node <replaceable>node_id</replaceable>. The most
+ recent GCI that can be used has the index
+ <replaceable>current_gci</replaceable>, and the
+ oldest GCI from which the cluster can be restored
+ has the index <replaceable>old_gci</replaceable>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>LocalCheckpointStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Local checkpoint <replaceable>lcp</replaceable>
+ completed</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The local checkpoint having sequence ID
+ <replaceable>lcp</replaceable> on node
+ <replaceable>node_id</replaceable> has been
+ completed.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>LocalCheckpointCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Local Checkpoint stopped in
+ CALCULATED_KEEP_GCI</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node was unable to determine the most recent
+ usable GCI.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>LCPStoppedInCalcKeepGci</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 0
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Table ID = <replaceable>table_id</replaceable>,
+ fragment <replaceable>ID = fragment_id</replaceable>
+ has completed LCP on Node
+ <replaceable>node_id</replaceable> maxGciStarted:
+ <replaceable>started_gci</replaceable>
+ maxGciCompleted:
+ <replaceable>completed_gci</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A table fragment has been checkpointed to disk on
+ node <replaceable>node_id</replaceable>. The GCI in
+ progress has the index
+ <replaceable>started_gci</replaceable>, and the most
+ recent GCI to have been completed has the index
+ <replaceable>completed_gci</replaceable>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>LCPFragmentCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 11
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ ACC Blocked <replaceable>num_1</replaceable> and TUP
+ Blocked <replaceable>num_2</replaceable> times last
+ second</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Undo logging is blocked because the log buffer is
+ close to overflowing.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>UndoLogBlocked</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Start initiated
+ <replaceable>version</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Data node <replaceable>node_id</replaceable>,
+ running <literal>NDB</literal> version
+ <replaceable>version</replaceable>, is beginning its
+ startup process.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NDBStartStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 1
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Started <replaceable>version</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Data node <replaceable>node_id</replaceable>,
+ running <literal>NDB</literal> version
+ <replaceable>version</replaceable>, has started
+ successfully.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NDBStartCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 1
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ STTORRY received after restart finished</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node has received a signal indicating that a
+ cluster restart has completed.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>STTORRYRecieved</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 15
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Start phase <replaceable>phase</replaceable>
+ completed
+ (<replaceable>type</replaceable>)</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node has completed start phase
+ <replaceable>phase</replaceable> of a
+ <replaceable>type</replaceable> start. For a listing
+ of start phases, see
+ <xref linkend="mysql-cluster-start-phases"/>.
+ (<replaceable>type</replaceable> is one of
+ <literal>initial</literal>,
+ <literal>system</literal>, <literal>node</literal>,
+ <literal>initial node</literal>, or
+ <literal><Unknown></literal>.)
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>StartPhaseCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 4
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ CM_REGCONF president =
+ <replaceable>president_id</replaceable>, own Node =
+ <replaceable>own_id</replaceable>, our dynamic id =
+ <replaceable>dynamic_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Node <replaceable>president_id</replaceable> has
+ been selected as <quote>president</quote>.
+ <replaceable>own_id</replaceable> and
+ <replaceable>dynamic_id</replaceable> should always
+ be the same as the ID
+ (<replaceable>node_id</replaceable>) of the
+ reporting node.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>CM_REGCONF</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 3
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ CM_REGREF from Node
+ <replaceable>president_id</replaceable> to our Node
+ <replaceable>node_id</replaceable>. Cause =
+ <replaceable>cause</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The reporting node (ID
+ <replaceable>node_id</replaceable>) was unable to
+ accept node <replaceable>president_id</replaceable>
+ as president. The <replaceable>cause</replaceable>
+ of the problem is given as one of
+ <literal>Busy</literal>, <literal>Election with wait
+ = false</literal>, <literal>Not president</literal>,
+ <literal>Election without selecting new
+ candidate</literal>, or <literal>No such
+ cause</literal>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>CM_REGREF</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>: We
+ are Node <replaceable>own_id</replaceable> with
+ dynamic ID <replaceable>dynamic_id</replaceable>,
+ our left neighbour is Node
+ <replaceable>id_1</replaceable>, our right is Node
+ <replaceable>id_2</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node has discovered its neighboring nodes in the
+ cluster (node <replaceable>id_1</replaceable> and
+ node <replaceable>id_2</replaceable>).
+ <replaceable>node_id</replaceable>,
+ <replaceable>own_id</replaceable>, and
+ <replaceable>dynamic_id</replaceable> should always
+ be the same; if they are not, this indicates a
+ serious misconfiguration of the cluster nodes.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>FIND_NEIGHBOURS</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ <replaceable>type</replaceable> shutdown
+ initiated</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node has received a shutdown signal. The
+ <replaceable>type</replaceable> of shutdown is
+ either <literal>Cluster</literal> or
+ <literal>Node</literal>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NDBStopStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 1
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Node shutdown completed </literal>[<literal>,
+ <replaceable>action</replaceable></literal>]
+ [<literal>Initiated by signal
+ <replaceable>signal</replaceable>.</literal>]
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node has been shut down. This report may include
+ an <replaceable>action</replaceable>, which if
+ present is one of <literal>restarting</literal>,
+ <literal>no start</literal>, or
+ <literal>initial</literal>. The report may also
+ include a reference to an <literal>NDB</literal>
+ Protocol <replaceable>signal</replaceable>; for
+ possible signals, refer to
+ <xref linkend="ndb-internals-ndb-protocol-operations-signals"/>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NDBStopCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 1
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Forced node shutdown completed </literal>[<literal>,
+ action</literal>]<literal>.</literal>
+ [<literal>Occured during startphase
+ <replaceable>start_phase</replaceable>.</literal>]
+ [<literal> Initiated by
+ <replaceable>signal</replaceable>.</literal>]
+ [<literal>Caused by error
+ <replaceable>error_code</replaceable>:
+ '<replaceable>error_message</replaceable>(<replaceable>error_classification</replaceable>).
+ <replaceable>error_status</replaceable>'.</literal>
+ [<literal>(extra info
+ <replaceable>extra_code</replaceable>)</literal>]]
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node has been forcibly shut down. The
+ <replaceable>action</replaceable> (one of
+ <literal>restarting</literal>, <literal>no
+ start</literal>, or <literal>initial</literal>)
+ subsequently being taken, if any, is also reported.
+ If the shutdown occurred while the node was
+ starting, the report includes the
+ <replaceable>start_phase</replaceable> during which
+ the node failed. If this was a result of a
+ <replaceable>signal</replaceable> sent to the node,
+ this information is also provided (see
+ <xref linkend="ndb-internals-ndb-protocol-operations-signals"/>,
+ for more information). If the error causing the
+ failure is known, this is also included; for more
+ information about <literal>NDB</literal> error
+ messages and classifications, see
+ <xref linkend="ndb-errors"/>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NDBStopForced</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 1
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Node shutdown aborted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node shutdown process was aborted by the user.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NDBStopAborted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 1
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ StartLog: [GCI Keep:
+ <replaceable>keep_pos</replaceable> LastCompleted:
+ <replaceable>last_pos</replaceable>
+ NewestRestorable:
+ <replaceable>restore_pos</replaceable>]</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This reports global checkpoints referenced during a
+ node start. The redo log prior to
+ <replaceable>keep_pos</replaceable> is dropped.
+ <replaceable>last_pos</replaceable> is the last
+ global checkpoint in which data node the
+ participated; <replaceable>restore_pos</replaceable>
+ is the global checkpoint which is actually used to
+ restore all data nodes.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>StartREDOLog</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 4
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <replaceable>startup_message</replaceable>
+ [<emphasis>Listed separately; see below.</emphasis>]
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ There are a number of possible startup messages that
+ can be logged under different circumstances.
+
+ <remark role="TODO">
+ [js] Uncomment the following when the referenced
+ section is published.
+ </remark>
+
+<!--
+ , which are listed separately; see
+ <xref linkend="mysql-cluster-log-startup-messages"/>
+ -->
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>StartReport</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 4
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Node restart completed copy of dictionary
+ information</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Copying of data dictionary information to the
+ restarted node has been completed.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NR_CopyDict</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Node restart completed copy of distribution
+ information</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Copying of data distribution information to the
+ restarted node has been completed.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NR_CopyDistr</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Node restart starting to copy the fragments to Node
+ <replaceable>node_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Copy of fragments to starting data node
+ <replaceable>node_id</replaceable> has begun
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NR_CopyFragsStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Table ID = <replaceable>table_id</replaceable>,
+ fragment ID = <replaceable>fragment_id</replaceable>
+ have been copied to Node
+ <replaceable>node_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Fragment <replaceable>fragment_id</replaceable> from
+ table <replaceable>table_id</replaceable> has been
+ copied to data node
+ <replaceable>node_id</replaceable>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NR_CopyFragDone</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 10
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Node restart completed copying the fragments to Node
+ <replaceable>node_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Copying of all table fragments to restarting data
+ node <replaceable>node_id</replaceable> has been
+ completed
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NR_CopyFragsCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ Any of the following:
+
+ <orderedlist>
+
+ <listitem>
+ <para>
+ <literal>Node
+ <replaceable>node_id</replaceable>: Node
+ <replaceable>node1_id</replaceable> completed
+ failure of Node
+ <replaceable>node2_id</replaceable></literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>All nodes completed failure of Node
+ <replaceable>node_id</replaceable></literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Node failure of
+ <replaceable>node_id</replaceable><replaceable>block</replaceable>
+ completed</literal>
+ </para>
+ </listitem>
+
+ </orderedlist>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ One of the following (each corresponding to the
+ same-numbered message listed above):
+
+ <orderedlist>
+
+ <listitem>
+ <para>
+ Data node <replaceable>node1_id</replaceable>
+ has detected the failure of data node
+ <replaceable>node2_id</replaceable>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ All (remaining) data nodes have detected the
+ failure of data node
+ <replaceable>node_id</replaceable>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The failure of data node
+ <replaceable>node_id</replaceable> has been
+ detected in the
+ <replaceable>block</replaceable><literal>NDB</literal>
+ kernel block, where block is 1 of
+ <literal>DBTC</literal>,
+ <literal>DBDICT</literal>,
+ <literal>DBDIH</literal>, or
+ <literal>DBLQH</literal>; for more
+ information, see
+ <xref linkend="ndb-internals-kernel-blocks"/>
+ </para>
+ </listitem>
+
+ </orderedlist>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NodeFailCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node
+ <replaceable>mgm_node_id</replaceable>: Node
+ <replaceable>data_node_id</replaceable> has failed.
+ The Node state at failure was
+ <replaceable>state_code</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A data node has failed. Its state at the time of
+ failure is described by an arbitration state code
+ <replaceable>state_code</replaceable>: possible
+ state code values can be found in the file
+ <filename>include/kernel/signaldata/ArbitSignalData.hpp</filename>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NODE_FAILREP</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>President restarts arbitration thread
+ [state=<replaceable>state_code</replaceable>]</literal>
+ or <literal>Prepare arbitrator node
+ <replaceable>node_id</replaceable>
+ [ticket=<replaceable>ticket_id</replaceable>]</literal>
+ or <literal>Receive arbitrator node
+ <replaceable>node_id</replaceable>
+ [ticket=<replaceable>ticket_id</replaceable>]</literal>
+ or <literal>Started arbitrator node
+ <replaceable>node_id</replaceable>
+ [ticket=<replaceable>ticket_id</replaceable>]</literal>
+ or <literal>Lost arbitrator node
+ <replaceable>node_id</replaceable> - process failure
+ [state=<replaceable>state_code</replaceable>]</literal>
+ or <literal>Lost arbitrator node
+ <replaceable>node_id</replaceable> - process exit
+ [state=<replaceable>state_code</replaceable>]</literal>
+ or <literal>Lost arbitrator node
+ <replaceable>node_id</replaceable> -
+ <replaceable>error_message</replaceable>
+ [state=<replaceable>state_code</replaceable>]</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This is a report on the current state and progress
+ of arbitration in the cluster.
+ <replaceable>node_id</replaceable> is the node ID of
+ the management node or SQL node selected as the
+ arbitrator. <replaceable>state_code</replaceable> is
+ an arbitration state code, as found in
+ <filename>include/kernel/signaldata/ArbitSignalData.hpp</filename>.
+ When an error has occurred, an
+ <replaceable>error_message</replaceable>, also
+ defined in <filename>ArbitSignalData.hpp</filename>,
+ is provided. <replaceable>ticket_id</replaceable> is
+ a unique identifier handed out by the arbitrator
+ when it is selected to all the nodes that
+ participated in its selection; this is used to
+ insure that each node requesting arbitration was one
+ of the nodes that took part in the selection
+ process.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>ArbitState</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 6
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Arbitration check lost - less than 1/2
+ nodes left</literal> or <literal>Arbitration check
+ won - all node groups and more than 1/2 nodes
+ left</literal> or <literal>Arbitration check won -
+ node group majority</literal> or
+ <literal>Arbitration check lost - missing node
+ group</literal> or <literal>Network partitioning -
+ arbitration required</literal> or
+ <literal>Arbitration won - positive reply from node
+ <replaceable>node_id</replaceable></literal> or
+ <literal>Arbitration lost - negative reply from node
+ <replaceable>node_id</replaceable></literal> or
+ <literal>Network partitioning - no arbitrator
+ available</literal> or <literal>Network partitioning
+ - no arbitrator configured</literal> or
+ <literal>Arbitration failure -
+ <replaceable>error_message</replaceable>
+ [state=<replaceable>state_code</replaceable>]</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This message reports on the result of arbitration.
+ In the event of arbitration failure, an
+ <replaceable>error_message</replaceable> and an
+ arbitration <replaceable>state_code</replaceable>
+ are provided; definitions for both of these are
+ found in
+ <filename>include/kernel/signaldata/ArbitSignalData.hpp</filename>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>ArbitResult</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 2
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ GCP Take over started</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node is attempting to assume responsibility for
+ the next global checkpoint (that is, it is becoming
+ the master node)
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>GCP_TakeoverStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ GCP Take over completed</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node has become the master, and has assumed
+ responsibility for the next global checkpoint
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>GCP_TakeoverCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ LCP Take over started</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node is attempting to assume responsibility for
+ the next set of local checkpoints (that is, it is
+ becoming the master node)
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>LCP_TakeoverStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ LCP Take over completed</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node has become the master, and has assumed
+ responsibility for the next set of local checkpoints
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>LCP_TakeoverCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Trans. Count =
+ <replaceable>transactions</replaceable>, Commit
+ Count = <replaceable>commits</replaceable>, Read
+ Count = <replaceable>reads</replaceable>, Simple
+ Read Count =
+ <replaceable>simple_reads</replaceable>, Write Count
+ = <replaceable>writes</replaceable>, AttrInfo Count
+ = <replaceable>AttrInfo_objects</replaceable>,
+ Concurrent Operations =
+ <replaceable>concurrent_operations</replaceable>,
+ Abort Count = <replaceable>aborts</replaceable>,
+ Scans = <replaceable>scans</replaceable>, Range
+ scans =
+ <replaceable>range_scans</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This report of transaction activity is given
+ approximately once every 10 seconds
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>TransReportCounters</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Operations=<replaceable>operations</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Number of operations performed by this node,
+ provided approximately once every 10 seconds
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>OperationReportCounters</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Table with ID = <replaceable>table_id</replaceable>
+ created</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A table having the table ID shown has been created
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>TableCreated</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Mean loop Counter in doJob last 8192 times =
+ <replaceable>count</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para></para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>JobStatistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 9
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Mean send size to Node =
+ <replaceable>node_id</replaceable> last 4096 sends =
+ <replaceable>bytes</replaceable> bytes</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node is sending an average of
+ <replaceable>bytes</replaceable> bytes per send to
+ node <replaceable>node_id</replaceable>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>SendBytesStatistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 9
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Mean receive size to Node =
+ <replaceable>node_id</replaceable> last 4096 sends =
+ <replaceable>bytes</replaceable> bytes</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node is receiving an average of
+ <replaceable>bytes</replaceable> of data each time
+ it receives data from node
+ <replaceable>node_id</replaceable>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>ReceiveBytesStatistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 9
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Data usage is
+ <replaceable>data_memory_percentage</replaceable>%
+ (<replaceable>data_pages_used</replaceable> 32K
+ pages of total
+ <replaceable>data_pages_total</replaceable>)</literal>
+ / <literal>Node <replaceable>node_id</replaceable>:
+ Index usage is
+ <replaceable>index_memory_percentage</replaceable>%
+ (<replaceable>index_pages_used</replaceable> 8K
+ pages of total
+ <replaceable>index_pages_total</replaceable>)
+ </literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This report is generated when a <literal>DUMP
+ 1000</literal> command is issued in the cluster
+ management client; for more information, see
+ <xref linkend="ndb-internals-dump-command-1000"/>,
+ in <xref linkend="ndb-internals"/>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>MemoryUsage</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 5
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node1_id</replaceable>:
+ Transporter to node
+ <replaceable>node2_id</replaceable> reported error
+ <replaceable>error_code</replaceable>:
+ <replaceable>error_message</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A transporter error occurred while communicating
+ with node <replaceable>node2_id</replaceable>; for a
+ listing of transporter error codes and messages, see
+ <xref linkend="ndb-transporter-errors"/>, in
+ <xref linkend="ndb-internals"/>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>TransporterError</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Error</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 2
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ERROR</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node1_id</replaceable>:
+ Transporter to node
+ <replaceable>node2_id</replaceable> reported error
+ <replaceable>error_code</replaceable>:
+ <replaceable>error_message</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A warning of a potential transporter problem while
+ communicating with node
+ <replaceable>node2_id</replaceable>; for a listing
+ of transporter error codes and messages, see
+ <xref linkend="ndb-transporter-errors"/>, for more
+ information
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>TransporterWarning</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Error</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>WARNING</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node1_id</replaceable>:
+ Node <replaceable>node2_id</replaceable> missed
+ heartbeat
+ <replaceable>heartbeat_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node missed a heartbeat from node
+ <replaceable>node2_id</replaceable>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>MissedHeartbeat</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Error</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>WARNING</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node1_id</replaceable>:
+ Node <replaceable>node2_id</replaceable> declared
+ dead due to missed heartbeat</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node has missed at least 3 heartbeats from node
+ <replaceable>node2_id</replaceable>, and so has
+ declared that node <quote>dead</quote>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>DeadDueToHeartbeat</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Error</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node1_id</replaceable>:
+ Node Sent Heartbeat to node =
+ <replaceable>node2_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node has sent a heartbeat to node
+ <replaceable>node2_id</replaceable>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>SentHeartbeat</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Info</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 12
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Event buffer status:
+ used=<replaceable>bytes_used</replaceable>
+ (<replaceable>percent_used</replaceable>%)
+ alloc=<replaceable>bytes_allocated</replaceable>
+ (<replaceable>percent_available</replaceable>%)
+ max=<replaceable>bytes_available</replaceable>
+ apply_gci=<replaceable>latest_restorable_GCI</replaceable>
+ latest_gci=<replaceable>latest_GCI</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This report is seen during heavy event buffer usage,
+ for example, when many updates are being applied in
+ a relatively short period of time; the report shows
+ the number of bytes and the percentage of event
+ buffer memory used, the bytes allocated and
+ percentage still available, and the latest and
+ latest restorable global checkpoints
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>EventBufferStatus</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Info</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Entering single user mode</literal>, <literal>Node
+ <replaceable>node_id</replaceable>: Entered single
+ user mode Node
+ <replaceable>API_node_id</replaceable> has exclusive
+ access</literal>, <literal>Node
+ <replaceable>node_id</replaceable>: Entering single
+ user mode</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ These reports are written to the cluster log when
+ entering and exiting single user mode;
+ <replaceable>API_node_id</replaceable> is the node
+ ID of the API or SQL having exclusive access to the
+ cluster (fro mroe information, see
+ <xref linkend="mysql-cluster-single-user-mode"/>);
+ the message <literal>Unknown single user report
+ <replaceable>API_node_id</replaceable></literal>
+ indicates an error has taken place and should never
+ be seen in normal operation
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>SingleUser</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Info</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Backup <replaceable>backup_id</replaceable> started
+ from node
+ <replaceable>mgm_node_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A backup has been started using the management node
+ having <replaceable>mgm_node_id</replaceable>; this
+ message is also displayed in the cluster management
+ client when the <literal>START BACKUP</literal>
+ command is issued; for more information, see
+ <xref linkend="mysql-cluster-backup-using-management-client"/>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>BackupStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Backup</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Backup <replaceable>backup_id</replaceable> started
+ from node <replaceable>mgm_node_id</replaceable>
+ completed. StartGCP:
+ <replaceable>start_gcp</replaceable> StopGCP:
+ <replaceable>stop_gcp</replaceable> #Records:
+ <replaceable>records</replaceable> #LogRecords:
+ <replaceable>log_records</replaceable> Data:
+ <replaceable>data_bytes</replaceable> bytes Log:
+ <replaceable>log_bytes</replaceable> bytes</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The backup having the ID
+ <replaceable>backup_id</replaceable> has been
+ completed; for more information, see
+ <xref linkend="mysql-cluster-backup-using-management-client"/>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>BackupCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Backup</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Backup request from
+ <replaceable>mgm_node_id</replaceable> failed to
+ start. Error:
+ <replaceable>error_code</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The backup failed to start; for error codes, see
+ <xref linkend="mgm-errors"/>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>BackupFailedToStart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Backup</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Backup <replaceable>backup_id</replaceable> started
+ from <replaceable>mgm_node_id</replaceable> has been
+ aborted. Error:
+ <replaceable>error_code</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The backup was terminated after starting, possibly
+ due to user intervention
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>BackupAborted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Backup</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+
+ </section>
+
+<!--
+ <remark role="TODO">
+ [js] Fill in missing parameters prior to deployment
+ </remark>
+
+ <section id="mysql-cluster-log-startup-messages">
+
+ <title>Cluster Log Startup Messages</title>
+
+ <para>
+ Possible startup messages with descriptions are provided in the
+ following list:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>Initial start, waiting for %s to connect, nodes [
+ all: %s connected: %s no-wait: %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Waiting until nodes: %s connects, nodes [ all: %s
+ connected: %s no-wait: %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Waiting %u sec for nodes %s to connect, nodes [
+ all: %s connected: %s no-wait: %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Waiting for non partitioned start, nodes [ all: %s
+ connected: %s missing: %s no-wait: %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Waiting %u sec for non partitioned start, nodes [
+ all: %s connected: %s missing: %s no-wait: %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Initial start with nodes %s [ missing: %s no-wait:
+ %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Start with all nodes %s</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Start with nodes %s [ missing: %s no-wait: %s
+ ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Start potentially partitioned with nodes %s [
+ missing: %s no-wait: %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Unknown startreport: 0x%x [ %s %s %s %s ]</literal>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ </section>
+-->
+
+ <section id="mysql-cluster-ndb-transporter-errors">
+
+ <title><literal>NDB</literal> Transporter Errors</title>
+
+ <para>
+ This section lists error codes, names, and messages that are
+ written to the cluster log in the event of transporter errors.
+ </para>
+
+ <informaltable>
+ <tgroup cols="3">
+ <colspec colwidth="10*"/>
+ <colspec colwidth="60*"/>
+ <colspec colwidth="30*"/>
+ <thead>
+ <row>
+ <entry>Error Code</entry>
+ <entry>Error Name</entry>
+ <entry>Error Text</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><errorcode>0x00</errorcode></entry>
+ <entry><errorname>TE_NO_ERROR</errorname></entry>
+ <entry><errortext>No error</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x01</errorcode></entry>
+ <entry><errorname>TE_ERROR_CLOSING_SOCKET</errorname></entry>
+ <entry><errortext>Error found during closing of socket</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x02</errorcode></entry>
+ <entry><errorname>TE_ERROR_IN_SELECT_BEFORE_ACCEPT</errorname></entry>
+ <entry><errortext>Error found before accept. The transporter will
+ retry</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x03</errorcode></entry>
+ <entry><errorname>TE_INVALID_MESSAGE_LENGTH</errorname></entry>
+ <entry><errortext>Error found in message (invalid message length)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x04</errorcode></entry>
+ <entry><errorname>TE_INVALID_CHECKSUM</errorname></entry>
+ <entry><errortext>Error found in message (checksum)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x05</errorcode></entry>
+ <entry><errorname>TE_COULD_NOT_CREATE_SOCKET</errorname></entry>
+ <entry><errortext>Error found while creating socket(can't create
+ socket)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x06</errorcode></entry>
+ <entry><errorname>TE_COULD_NOT_BIND_SOCKET</errorname></entry>
+ <entry><errortext>Error found while binding server socket</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x07</errorcode></entry>
+ <entry><errorname>TE_LISTEN_FAILED</errorname></entry>
+ <entry><errortext>Error found while listening to server socket</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x08</errorcode></entry>
+ <entry><errorname>TE_ACCEPT_RETURN_ERROR</errorname></entry>
+ <entry><errortext>Error found during accept(accept return error)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x0b</errorcode></entry>
+ <entry><errorname>TE_SHM_DISCONNECT</errorname></entry>
+ <entry><errortext>The remote node has disconnected</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x0c</errorcode></entry>
+ <entry><errorname>TE_SHM_IPC_STAT</errorname></entry>
+ <entry><errortext>Unable to check shm segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x0d</errorcode></entry>
+ <entry><errorname>TE_SHM_UNABLE_TO_CREATE_SEGMENT</errorname></entry>
+ <entry><errortext>Unable to create shm segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x0e</errorcode></entry>
+ <entry><errorname>TE_SHM_UNABLE_TO_ATTACH_SEGMENT</errorname></entry>
+ <entry><errortext>Unable to attach shm segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x0f</errorcode></entry>
+ <entry><errorname>TE_SHM_UNABLE_TO_REMOVE_SEGMENT</errorname></entry>
+ <entry><errortext>Unable to remove shm segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x10</errorcode></entry>
+ <entry><errorname>TE_TOO_SMALL_SIGID</errorname></entry>
+ <entry><errortext>Sig ID too small</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x11</errorcode></entry>
+ <entry><errorname>TE_TOO_LARGE_SIGID</errorname></entry>
+ <entry><errortext>Sig ID too large</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x12</errorcode></entry>
+ <entry><errorname>TE_WAIT_STACK_FULL</errorname></entry>
+ <entry><errortext>Wait stack was full</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x13</errorcode></entry>
+ <entry><errorname>TE_RECEIVE_BUFFER_FULL</errorname></entry>
+ <entry><errortext>Receive buffer was full</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x14</errorcode></entry>
+ <entry><errorname>TE_SIGNAL_LOST_SEND_BUFFER_FULL</errorname></entry>
+ <entry><errortext>Send buffer was full,and trying to force send
+ fails</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x15</errorcode></entry>
+ <entry><errorname>TE_SIGNAL_LOST</errorname></entry>
+ <entry><errortext>Send failed for unknown reason(signal lost)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x16</errorcode></entry>
+ <entry><errorname>TE_SEND_BUFFER_FULL</errorname></entry>
+ <entry><errortext>The send buffer was full, but sleeping for a while
+ solved</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x0017</errorcode></entry>
+ <entry><errorname>TE_SCI_LINK_ERROR</errorname></entry>
+ <entry><errortext>There is no link from this node to the switch</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x18</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_START_SEQUENCE</errorname></entry>
+ <entry><errortext>Could not start a sequence, because system resources are
+ exumed or no sequence has been created</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x19</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_REMOVE_SEQUENCE</errorname></entry>
+ <entry><errortext>Could not remove a sequence</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x1a</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_CREATE_SEQUENCE</errorname></entry>
+ <entry><errortext>Could not create a sequence, because system resources are
+ exempted. Must reboot</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x1b</errorcode></entry>
+ <entry><errorname>TE_SCI_UNRECOVERABLE_DATA_TFX_ERROR</errorname></entry>
+ <entry><errortext>Tried to send data on redundant link but failed</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x1c</errorcode></entry>
+ <entry><errorname>TE_SCI_CANNOT_INIT_LOCALSEGMENT</errorname></entry>
+ <entry><errortext>Cannot initialize local segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x1d</errorcode></entry>
+ <entry><errorname>TE_SCI_CANNOT_MAP_REMOTESEGMENT</errorname></entry>
+ <entry><errortext>Cannot map remote segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x1e</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_UNMAP_SEGMENT</errorname></entry>
+ <entry><errortext>Cannot free the resources used by this segment (step
+ 1)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x1f</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_REMOVE_SEGMENT</errorname></entry>
+ <entry><errortext>Cannot free the resources used by this segment (step
+ 2)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x20</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_DISCONNECT_SEGMENT</errorname></entry>
+ <entry><errortext>Cannot disconnect from a remote segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x21</errorcode></entry>
+ <entry><errorname>TE_SHM_IPC_PERMANENT</errorname></entry>
+ <entry><errortext>Shm ipc Permanent error</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x22</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_CLOSE_CHANNEL</errorname></entry>
+ <entry><errortext>Unable to close the sci channel and the resources
+ allocated</errortext></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+
+ </section>
+
+ </section>
+
<section id="mysql-cluster-single-user-mode">
<title>Single User Mode</title>
Modified: trunk/refman-5.0/Makefile.depends
===================================================================
--- trunk/refman-5.0/Makefile.depends 2008-07-22 08:33:38 UTC (rev 11306)
+++ trunk/refman-5.0/Makefile.depends 2008-07-22 10:21:18 UTC (rev 11307)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 0; 981 bytes
@@ -2104,6 +2104,8 @@
mysql_cluster_management_IMAGES =
mysql_cluster_management_SOURCES = mysql-cluster-management.xml $(mysql_cluster_management_INCLUDES)
mysql_cluster_management_IDMAPS = \
+ ../ndbapi/metadata/mgm-api.idmap \
+ ../ndbapi/metadata/ndb-errors.idmap \
../ndbapi/metadata/ndb-internals.idmap \
../refman-5.0/metadata/dba-core.idmap \
../refman-5.0/metadata/mysql-cluster-backup.idmap \
@@ -2366,6 +2368,7 @@
../refman-common/images/published/rolling-restarts.png
mysql_cluster_SOURCES = mysql-cluster.xml $(mysql_cluster_INCLUDES)
mysql_cluster_IDMAPS = \
+ ../ndbapi/metadata/mgm-api.idmap \
../ndbapi/metadata/ndb-errors.idmap \
../ndbapi/metadata/ndb-internals.idmap \
../ndbapi/metadata/ndbapi.idmap \
Modified: trunk/refman-5.0/mysql-cluster-management.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster-management.xml 2008-07-22 08:33:38 UTC (rev 11306)
+++ trunk/refman-5.0/mysql-cluster-management.xml 2008-07-22 10:21:18 UTC (rev 11307)
Changed blocks: 1, Lines Added: 4192, Lines Deleted: 0; 115864 bytes
@@ -2270,6 +2270,4198 @@
</section>
+ <section id="mysql-cluster-logs-ndb-messages">
+
+ <title><literal>NDB</literal> Log Messages</title>
+
+ <para>
+ This section contains information about the messages written to
+ the cluster log in response to different cluster log events. It
+ provides additional, more specific information on
+ <literal>NDB</literal> transporter errors.
+ </para>
+
+ <section id="mysql-cluster-logs-cluster-log">
+
+ <title>Messages in the Cluster Log</title>
+
+ <para>
+ The following table lists the most common <literal>NDB</literal>
+ cluster log messages. For information about the cluster log, log
+ events, and event types, see
+ <xref linkend="mysql-cluster-event-reports"/>. These log
+ messages also correspond to log event types in the MGM API; see
+ <xref linkend="ndb-logevent-type"/>, for related information of
+ interest to Cluster API developers.
+ </para>
+
+ <informaltable>
+ <tgroup cols="2">
+ <colspec colwidth="60*"/>
+ <colspec colwidth="40*"/>
+ <tbody>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node
+ <replaceable>mgm_node_id</replaceable>: Node
+ <replaceable>data_node_id</replaceable>
+ Connected</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The data node having node ID
+ <replaceable>node_id</replaceable> has connected to
+ the management server (node
+ <replaceable>mgm_node_id</replaceable>).
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>Connected</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Connection</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node
+ <replaceable>mgm_node_id</replaceable>: Node
+ <replaceable>data_node_id</replaceable>
+ Disconnected</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The data node having node ID
+ <replaceable>data_node_id</replaceable> has
+ disconnected from the management server (node
+ <replaceable>mgm_node_id</replaceable>).
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>Disconnected</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Connection</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node
+ <replaceable>data_node_id</replaceable>:
+ Communication to Node
+ <replaceable>api_node_id</replaceable>
+ closed</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The API node or SQL node having node ID
+ <replaceable>api_node_id</replaceable> is no longer
+ communicating with data node
+ <replaceable>data_node_id</replaceable>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>CommunicationClosed</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Connection</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node
+ <replaceable>data_node_id</replaceable>:
+ Communication to Node
+ <replaceable>api_node_id</replaceable>
+ opened</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The API node or SQL node having node ID
+ <replaceable>api_node_id</replaceable> is now
+ communicating with data node
+ <replaceable>data_node_id</replaceable>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>CommunicationOpened</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Connection</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node
+ <replaceable>mgm_node_id</replaceable>: Node
+ <replaceable>api_node_id</replaceable>: API
+ <replaceable>version</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The API node having node ID
+ <replaceable>api_node_id</replaceable> has connected
+ to management node
+ <replaceable>mgm_node_id</replaceable> using
+ <literal>NDB</literal> API version
+ <replaceable>version</replaceable> (generally the
+ same as the MySQL version number).
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>ConnectedApiVersion</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Connection</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Global checkpoint <replaceable>gci</replaceable>
+ started</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A global checkpoint with the ID
+ <replaceable>gci</replaceable> has been started;
+ node <replaceable>node_id</replaceable> is the
+ master responsible for this global checkpoint.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>GlobalCheckpointStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 9
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Global checkpoint <replaceable>gci</replaceable>
+ completed</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The global checkpoint having the ID
+ <replaceable>gci</replaceable> has been completed;
+ node <replaceable>node_id</replaceable> was the
+ master responsible for this global checkpoint.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>GlobalCheckpointCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 10
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Local checkpoint <replaceable>lcp</replaceable>
+ started. Keep GCI =
+ <replaceable>current_gci</replaceable> oldest
+ restorable GCI =
+ <replaceable>old_gci</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The local checkpoint having sequence ID
+ <replaceable>lcp</replaceable> has been started on
+ node <replaceable>node_id</replaceable>. The most
+ recent GCI that can be used has the index
+ <replaceable>current_gci</replaceable>, and the
+ oldest GCI from which the cluster can be restored
+ has the index <replaceable>old_gci</replaceable>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>LocalCheckpointStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Local checkpoint <replaceable>lcp</replaceable>
+ completed</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The local checkpoint having sequence ID
+ <replaceable>lcp</replaceable> on node
+ <replaceable>node_id</replaceable> has been
+ completed.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>LocalCheckpointCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Local Checkpoint stopped in
+ CALCULATED_KEEP_GCI</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node was unable to determine the most recent
+ usable GCI.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>LCPStoppedInCalcKeepGci</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 0
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Table ID = <replaceable>table_id</replaceable>,
+ fragment <replaceable>ID = fragment_id</replaceable>
+ has completed LCP on Node
+ <replaceable>node_id</replaceable> maxGciStarted:
+ <replaceable>started_gci</replaceable>
+ maxGciCompleted:
+ <replaceable>completed_gci</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A table fragment has been checkpointed to disk on
+ node <replaceable>node_id</replaceable>. The GCI in
+ progress has the index
+ <replaceable>started_gci</replaceable>, and the most
+ recent GCI to have been completed has the index
+ <replaceable>completed_gci</replaceable>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>LCPFragmentCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 11
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ ACC Blocked <replaceable>num_1</replaceable> and TUP
+ Blocked <replaceable>num_2</replaceable> times last
+ second</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Undo logging is blocked because the log buffer is
+ close to overflowing.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>UndoLogBlocked</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Checkpoint</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Start initiated
+ <replaceable>version</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Data node <replaceable>node_id</replaceable>,
+ running <literal>NDB</literal> version
+ <replaceable>version</replaceable>, is beginning its
+ startup process.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NDBStartStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 1
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Started <replaceable>version</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Data node <replaceable>node_id</replaceable>,
+ running <literal>NDB</literal> version
+ <replaceable>version</replaceable>, has started
+ successfully.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NDBStartCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 1
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ STTORRY received after restart finished</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node has received a signal indicating that a
+ cluster restart has completed.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>STTORRYRecieved</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 15
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Start phase <replaceable>phase</replaceable>
+ completed
+ (<replaceable>type</replaceable>)</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node has completed start phase
+ <replaceable>phase</replaceable> of a
+ <replaceable>type</replaceable> start. For a listing
+ of start phases, see
+ <xref linkend="mysql-cluster-start-phases"/>.
+ (<replaceable>type</replaceable> is one of
+ <literal>initial</literal>,
+ <literal>system</literal>, <literal>node</literal>,
+ <literal>initial node</literal>, or
+ <literal><Unknown></literal>.)
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>StartPhaseCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 4
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ CM_REGCONF president =
+ <replaceable>president_id</replaceable>, own Node =
+ <replaceable>own_id</replaceable>, our dynamic id =
+ <replaceable>dynamic_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Node <replaceable>president_id</replaceable> has
+ been selected as <quote>president</quote>.
+ <replaceable>own_id</replaceable> and
+ <replaceable>dynamic_id</replaceable> should always
+ be the same as the ID
+ (<replaceable>node_id</replaceable>) of the
+ reporting node.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>CM_REGCONF</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 3
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ CM_REGREF from Node
+ <replaceable>president_id</replaceable> to our Node
+ <replaceable>node_id</replaceable>. Cause =
+ <replaceable>cause</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The reporting node (ID
+ <replaceable>node_id</replaceable>) was unable to
+ accept node <replaceable>president_id</replaceable>
+ as president. The <replaceable>cause</replaceable>
+ of the problem is given as one of
+ <literal>Busy</literal>, <literal>Election with wait
+ = false</literal>, <literal>Not president</literal>,
+ <literal>Election without selecting new
+ candidate</literal>, or <literal>No such
+ cause</literal>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>CM_REGREF</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>: We
+ are Node <replaceable>own_id</replaceable> with
+ dynamic ID <replaceable>dynamic_id</replaceable>,
+ our left neighbour is Node
+ <replaceable>id_1</replaceable>, our right is Node
+ <replaceable>id_2</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node has discovered its neighboring nodes in the
+ cluster (node <replaceable>id_1</replaceable> and
+ node <replaceable>id_2</replaceable>).
+ <replaceable>node_id</replaceable>,
+ <replaceable>own_id</replaceable>, and
+ <replaceable>dynamic_id</replaceable> should always
+ be the same; if they are not, this indicates a
+ serious misconfiguration of the cluster nodes.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>FIND_NEIGHBOURS</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ <replaceable>type</replaceable> shutdown
+ initiated</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node has received a shutdown signal. The
+ <replaceable>type</replaceable> of shutdown is
+ either <literal>Cluster</literal> or
+ <literal>Node</literal>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NDBStopStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 1
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Node shutdown completed </literal>[<literal>,
+ <replaceable>action</replaceable></literal>]
+ [<literal>Initiated by signal
+ <replaceable>signal</replaceable>.</literal>]
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node has been shut down. This report may include
+ an <replaceable>action</replaceable>, which if
+ present is one of <literal>restarting</literal>,
+ <literal>no start</literal>, or
+ <literal>initial</literal>. The report may also
+ include a reference to an <literal>NDB</literal>
+ Protocol <replaceable>signal</replaceable>; for
+ possible signals, refer to
+ <xref linkend="ndb-internals-ndb-protocol-operations-signals"/>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NDBStopCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 1
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Forced node shutdown completed </literal>[<literal>,
+ action</literal>]<literal>.</literal>
+ [<literal>Occured during startphase
+ <replaceable>start_phase</replaceable>.</literal>]
+ [<literal> Initiated by
+ <replaceable>signal</replaceable>.</literal>]
+ [<literal>Caused by error
+ <replaceable>error_code</replaceable>:
+ '<replaceable>error_message</replaceable>(<replaceable>error_classification</replaceable>).
+ <replaceable>error_status</replaceable>'.</literal>
+ [<literal>(extra info
+ <replaceable>extra_code</replaceable>)</literal>]]
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node has been forcibly shut down. The
+ <replaceable>action</replaceable> (one of
+ <literal>restarting</literal>, <literal>no
+ start</literal>, or <literal>initial</literal>)
+ subsequently being taken, if any, is also reported.
+ If the shutdown occurred while the node was
+ starting, the report includes the
+ <replaceable>start_phase</replaceable> during which
+ the node failed. If this was a result of a
+ <replaceable>signal</replaceable> sent to the node,
+ this information is also provided (see
+ <xref linkend="ndb-internals-ndb-protocol-operations-signals"/>,
+ for more information). If the error causing the
+ failure is known, this is also included; for more
+ information about <literal>NDB</literal> error
+ messages and classifications, see
+ <xref linkend="ndb-errors"/>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NDBStopForced</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 1
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Node shutdown aborted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The node shutdown process was aborted by the user.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NDBStopAborted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 1
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ StartLog: [GCI Keep:
+ <replaceable>keep_pos</replaceable> LastCompleted:
+ <replaceable>last_pos</replaceable>
+ NewestRestorable:
+ <replaceable>restore_pos</replaceable>]</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This reports global checkpoints referenced during a
+ node start. The redo log prior to
+ <replaceable>keep_pos</replaceable> is dropped.
+ <replaceable>last_pos</replaceable> is the last
+ global checkpoint in which data node the
+ participated; <replaceable>restore_pos</replaceable>
+ is the global checkpoint which is actually used to
+ restore all data nodes.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>StartREDOLog</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 4
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <replaceable>startup_message</replaceable>
+ [<emphasis>Listed separately; see below.</emphasis>]
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ There are a number of possible startup messages that
+ can be logged under different circumstances.
+
+ <remark role="TODO">
+ [js] Uncomment the following when the referenced
+ section is published.
+ </remark>
+
+<!--
+ , which are listed separately; see
+ <xref linkend="mysql-cluster-log-startup-messages"/>
+ -->
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>StartReport</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>StartUp</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 4
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Node restart completed copy of dictionary
+ information</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Copying of data dictionary information to the
+ restarted node has been completed.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NR_CopyDict</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Node restart completed copy of distribution
+ information</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Copying of data distribution information to the
+ restarted node has been completed.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NR_CopyDistr</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Node restart starting to copy the fragments to Node
+ <replaceable>node_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Copy of fragments to starting data node
+ <replaceable>node_id</replaceable> has begun
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NR_CopyFragsStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Table ID = <replaceable>table_id</replaceable>,
+ fragment ID = <replaceable>fragment_id</replaceable>
+ have been copied to Node
+ <replaceable>node_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Fragment <replaceable>fragment_id</replaceable> from
+ table <replaceable>table_id</replaceable> has been
+ copied to data node
+ <replaceable>node_id</replaceable>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NR_CopyFragDone</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 10
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Node restart completed copying the fragments to Node
+ <replaceable>node_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Copying of all table fragments to restarting data
+ node <replaceable>node_id</replaceable> has been
+ completed
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NR_CopyFragsCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ Any of the following:
+
+ <orderedlist>
+
+ <listitem>
+ <para>
+ <literal>Node
+ <replaceable>node_id</replaceable>: Node
+ <replaceable>node1_id</replaceable> completed
+ failure of Node
+ <replaceable>node2_id</replaceable></literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>All nodes completed failure of Node
+ <replaceable>node_id</replaceable></literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Node failure of
+ <replaceable>node_id</replaceable><replaceable>block</replaceable>
+ completed</literal>
+ </para>
+ </listitem>
+
+ </orderedlist>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ One of the following (each corresponding to the
+ same-numbered message listed above):
+
+ <orderedlist>
+
+ <listitem>
+ <para>
+ Data node <replaceable>node1_id</replaceable>
+ has detected the failure of data node
+ <replaceable>node2_id</replaceable>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ All (remaining) data nodes have detected the
+ failure of data node
+ <replaceable>node_id</replaceable>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The failure of data node
+ <replaceable>node_id</replaceable> has been
+ detected in the
+ <replaceable>block</replaceable><literal>NDB</literal>
+ kernel block, where block is 1 of
+ <literal>DBTC</literal>,
+ <literal>DBDICT</literal>,
+ <literal>DBDIH</literal>, or
+ <literal>DBLQH</literal>; for more
+ information, see
+ <xref linkend="ndb-internals-kernel-blocks"/>
+ </para>
+ </listitem>
+
+ </orderedlist>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NodeFailCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node
+ <replaceable>mgm_node_id</replaceable>: Node
+ <replaceable>data_node_id</replaceable> has failed.
+ The Node state at failure was
+ <replaceable>state_code</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A data node has failed. Its state at the time of
+ failure is described by an arbitration state code
+ <replaceable>state_code</replaceable>: possible
+ state code values can be found in the file
+ <filename>include/kernel/signaldata/ArbitSignalData.hpp</filename>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>NODE_FAILREP</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>President restarts arbitration thread
+ [state=<replaceable>state_code</replaceable>]</literal>
+ or <literal>Prepare arbitrator node
+ <replaceable>node_id</replaceable>
+ [ticket=<replaceable>ticket_id</replaceable>]</literal>
+ or <literal>Receive arbitrator node
+ <replaceable>node_id</replaceable>
+ [ticket=<replaceable>ticket_id</replaceable>]</literal>
+ or <literal>Started arbitrator node
+ <replaceable>node_id</replaceable>
+ [ticket=<replaceable>ticket_id</replaceable>]</literal>
+ or <literal>Lost arbitrator node
+ <replaceable>node_id</replaceable> - process failure
+ [state=<replaceable>state_code</replaceable>]</literal>
+ or <literal>Lost arbitrator node
+ <replaceable>node_id</replaceable> - process exit
+ [state=<replaceable>state_code</replaceable>]</literal>
+ or <literal>Lost arbitrator node
+ <replaceable>node_id</replaceable> -
+ <replaceable>error_message</replaceable>
+ [state=<replaceable>state_code</replaceable>]</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This is a report on the current state and progress
+ of arbitration in the cluster.
+ <replaceable>node_id</replaceable> is the node ID of
+ the management node or SQL node selected as the
+ arbitrator. <replaceable>state_code</replaceable> is
+ an arbitration state code, as found in
+ <filename>include/kernel/signaldata/ArbitSignalData.hpp</filename>.
+ When an error has occurred, an
+ <replaceable>error_message</replaceable>, also
+ defined in <filename>ArbitSignalData.hpp</filename>,
+ is provided. <replaceable>ticket_id</replaceable> is
+ a unique identifier handed out by the arbitrator
+ when it is selected to all the nodes that
+ participated in its selection; this is used to
+ insure that each node requesting arbitration was one
+ of the nodes that took part in the selection
+ process.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>ArbitState</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 6
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Arbitration check lost - less than 1/2
+ nodes left</literal> or <literal>Arbitration check
+ won - all node groups and more than 1/2 nodes
+ left</literal> or <literal>Arbitration check won -
+ node group majority</literal> or
+ <literal>Arbitration check lost - missing node
+ group</literal> or <literal>Network partitioning -
+ arbitration required</literal> or
+ <literal>Arbitration won - positive reply from node
+ <replaceable>node_id</replaceable></literal> or
+ <literal>Arbitration lost - negative reply from node
+ <replaceable>node_id</replaceable></literal> or
+ <literal>Network partitioning - no arbitrator
+ available</literal> or <literal>Network partitioning
+ - no arbitrator configured</literal> or
+ <literal>Arbitration failure -
+ <replaceable>error_message</replaceable>
+ [state=<replaceable>state_code</replaceable>]</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This message reports on the result of arbitration.
+ In the event of arbitration failure, an
+ <replaceable>error_message</replaceable> and an
+ arbitration <replaceable>state_code</replaceable>
+ are provided; definitions for both of these are
+ found in
+ <filename>include/kernel/signaldata/ArbitSignalData.hpp</filename>.
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>ArbitResult</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 2
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ GCP Take over started</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node is attempting to assume responsibility for
+ the next global checkpoint (that is, it is becoming
+ the master node)
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>GCP_TakeoverStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ GCP Take over completed</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node has become the master, and has assumed
+ responsibility for the next global checkpoint
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>GCP_TakeoverCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ LCP Take over started</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node is attempting to assume responsibility for
+ the next set of local checkpoints (that is, it is
+ becoming the master node)
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>LCP_TakeoverStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ LCP Take over completed</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node has become the master, and has assumed
+ responsibility for the next set of local checkpoints
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>LCP_TakeoverCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>NodeRestart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Trans. Count =
+ <replaceable>transactions</replaceable>, Commit
+ Count = <replaceable>commits</replaceable>, Read
+ Count = <replaceable>reads</replaceable>, Simple
+ Read Count =
+ <replaceable>simple_reads</replaceable>, Write Count
+ = <replaceable>writes</replaceable>, AttrInfo Count
+ = <replaceable>AttrInfo_objects</replaceable>,
+ Concurrent Operations =
+ <replaceable>concurrent_operations</replaceable>,
+ Abort Count = <replaceable>aborts</replaceable>,
+ Scans = <replaceable>scans</replaceable>, Range
+ scans =
+ <replaceable>range_scans</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This report of transaction activity is given
+ approximately once every 10 seconds
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>TransReportCounters</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Operations=<replaceable>operations</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ Number of operations performed by this node,
+ provided approximately once every 10 seconds
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>OperationReportCounters</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Table with ID = <replaceable>table_id</replaceable>
+ created</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A table having the table ID shown has been created
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>TableCreated</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Mean loop Counter in doJob last 8192 times =
+ <replaceable>count</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para></para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>JobStatistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 9
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Mean send size to Node =
+ <replaceable>node_id</replaceable> last 4096 sends =
+ <replaceable>bytes</replaceable> bytes</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node is sending an average of
+ <replaceable>bytes</replaceable> bytes per send to
+ node <replaceable>node_id</replaceable>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>SendBytesStatistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 9
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Mean receive size to Node =
+ <replaceable>node_id</replaceable> last 4096 sends =
+ <replaceable>bytes</replaceable> bytes</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node is receiving an average of
+ <replaceable>bytes</replaceable> of data each time
+ it receives data from node
+ <replaceable>node_id</replaceable>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>ReceiveBytesStatistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 9
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Data usage is
+ <replaceable>data_memory_percentage</replaceable>%
+ (<replaceable>data_pages_used</replaceable> 32K
+ pages of total
+ <replaceable>data_pages_total</replaceable>)</literal>
+ / <literal>Node <replaceable>node_id</replaceable>:
+ Index usage is
+ <replaceable>index_memory_percentage</replaceable>%
+ (<replaceable>index_pages_used</replaceable> 8K
+ pages of total
+ <replaceable>index_pages_total</replaceable>)
+ </literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This report is generated when a <literal>DUMP
+ 1000</literal> command is issued in the cluster
+ management client; for more information, see
+ <xref linkend="ndb-internals-dump-command-1000"/>,
+ in <xref linkend="ndb-internals"/>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>MemoryUsage</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Statistic</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 5
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node1_id</replaceable>:
+ Transporter to node
+ <replaceable>node2_id</replaceable> reported error
+ <replaceable>error_code</replaceable>:
+ <replaceable>error_message</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A transporter error occurred while communicating
+ with node <replaceable>node2_id</replaceable>; for a
+ listing of transporter error codes and messages, see
+ <xref linkend="ndb-transporter-errors"/>, in
+ <xref linkend="ndb-internals"/>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>TransporterError</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Error</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 2
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ERROR</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node1_id</replaceable>:
+ Transporter to node
+ <replaceable>node2_id</replaceable> reported error
+ <replaceable>error_code</replaceable>:
+ <replaceable>error_message</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A warning of a potential transporter problem while
+ communicating with node
+ <replaceable>node2_id</replaceable>; for a listing
+ of transporter error codes and messages, see
+ <xref linkend="ndb-transporter-errors"/>, for more
+ information
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>TransporterWarning</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Error</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>WARNING</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node1_id</replaceable>:
+ Node <replaceable>node2_id</replaceable> missed
+ heartbeat
+ <replaceable>heartbeat_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node missed a heartbeat from node
+ <replaceable>node2_id</replaceable>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>MissedHeartbeat</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Error</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>WARNING</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node1_id</replaceable>:
+ Node <replaceable>node2_id</replaceable> declared
+ dead due to missed heartbeat</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node has missed at least 3 heartbeats from node
+ <replaceable>node2_id</replaceable>, and so has
+ declared that node <quote>dead</quote>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>DeadDueToHeartbeat</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Error</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 8
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node1_id</replaceable>:
+ Node Sent Heartbeat to node =
+ <replaceable>node2_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This node has sent a heartbeat to node
+ <replaceable>node2_id</replaceable>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>SentHeartbeat</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Info</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 12
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Event buffer status:
+ used=<replaceable>bytes_used</replaceable>
+ (<replaceable>percent_used</replaceable>%)
+ alloc=<replaceable>bytes_allocated</replaceable>
+ (<replaceable>percent_available</replaceable>%)
+ max=<replaceable>bytes_available</replaceable>
+ apply_gci=<replaceable>latest_restorable_GCI</replaceable>
+ latest_gci=<replaceable>latest_GCI</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ This report is seen during heavy event buffer usage,
+ for example, when many updates are being applied in
+ a relatively short period of time; the report shows
+ the number of bytes and the percentage of event
+ buffer memory used, the bytes allocated and
+ percentage still available, and the latest and
+ latest restorable global checkpoints
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>EventBufferStatus</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Info</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Entering single user mode</literal>, <literal>Node
+ <replaceable>node_id</replaceable>: Entered single
+ user mode Node
+ <replaceable>API_node_id</replaceable> has exclusive
+ access</literal>, <literal>Node
+ <replaceable>node_id</replaceable>: Entering single
+ user mode</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ These reports are written to the cluster log when
+ entering and exiting single user mode;
+ <replaceable>API_node_id</replaceable> is the node
+ ID of the API or SQL having exclusive access to the
+ cluster (fro mroe information, see
+ <xref linkend="mysql-cluster-single-user-mode"/>);
+ the message <literal>Unknown single user report
+ <replaceable>API_node_id</replaceable></literal>
+ indicates an error has taken place and should never
+ be seen in normal operation
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>SingleUser</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Info</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Backup <replaceable>backup_id</replaceable> started
+ from node
+ <replaceable>mgm_node_id</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ A backup has been started using the management node
+ having <replaceable>mgm_node_id</replaceable>; this
+ message is also displayed in the cluster management
+ client when the <literal>START BACKUP</literal>
+ command is issued; for more information, see
+ <xref linkend="mysql-cluster-backup-using-management-client"/>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>BackupStarted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Backup</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Backup <replaceable>backup_id</replaceable> started
+ from node <replaceable>mgm_node_id</replaceable>
+ completed. StartGCP:
+ <replaceable>start_gcp</replaceable> StopGCP:
+ <replaceable>stop_gcp</replaceable> #Records:
+ <replaceable>records</replaceable> #LogRecords:
+ <replaceable>log_records</replaceable> Data:
+ <replaceable>data_bytes</replaceable> bytes Log:
+ <replaceable>log_bytes</replaceable> bytes</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The backup having the ID
+ <replaceable>backup_id</replaceable> has been
+ completed; for more information, see
+ <xref linkend="mysql-cluster-backup-using-management-client"/>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>BackupCompleted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Backup</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>INFO</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Backup request from
+ <replaceable>mgm_node_id</replaceable> failed to
+ start. Error:
+ <replaceable>error_code</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The backup failed to start; for error codes, see
+ <xref linkend="mgm-errors"/>
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>BackupFailedToStart</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Backup</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ <row>
+ <entry><formalpara>
+
+ <title>Log Message</title>
+
+ <para>
+ <literal>Node <replaceable>node_id</replaceable>:
+ Backup <replaceable>backup_id</replaceable> started
+ from <replaceable>mgm_node_id</replaceable> has been
+ aborted. Error:
+ <replaceable>error_code</replaceable></literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Description</title>
+
+ <para>
+ The backup was terminated after starting, possibly
+ due to user intervention
+ </para>
+
+ </formalpara></entry>
+ <entry><formalpara>
+
+ <title>Event Name</title>
+
+ <para>
+ <literal>BackupAborted</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Event Type</title>
+
+ <para>
+ <literal>Backup</literal>
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Priority</title>
+
+ <para>
+ 7
+ </para>
+
+ </formalpara>
+
+ <formalpara>
+
+ <title>Severity</title>
+
+ <para>
+ <literal>ALERT</literal>
+ </para>
+
+ </formalpara></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+
+ </section>
+
+<!--
+ <remark role="TODO">
+ [js] Fill in missing parameters prior to deployment
+ </remark>
+
+ <section id="mysql-cluster-log-startup-messages">
+
+ <title>Cluster Log Startup Messages</title>
+
+ <para>
+ Possible startup messages with descriptions are provided in the
+ following list:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>Initial start, waiting for %s to connect, nodes [
+ all: %s connected: %s no-wait: %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Waiting until nodes: %s connects, nodes [ all: %s
+ connected: %s no-wait: %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Waiting %u sec for nodes %s to connect, nodes [
+ all: %s connected: %s no-wait: %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Waiting for non partitioned start, nodes [ all: %s
+ connected: %s missing: %s no-wait: %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Waiting %u sec for non partitioned start, nodes [
+ all: %s connected: %s missing: %s no-wait: %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Initial start with nodes %s [ missing: %s no-wait:
+ %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Start with all nodes %s</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Start with nodes %s [ missing: %s no-wait: %s
+ ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Start potentially partitioned with nodes %s [
+ missing: %s no-wait: %s ]</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>Unknown startreport: 0x%x [ %s %s %s %s ]</literal>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ </section>
+-->
+
+ <section id="mysql-cluster-ndb-transporter-errors">
+
+ <title><literal>NDB</literal> Transporter Errors</title>
+
+ <para>
+ This section lists error codes, names, and messages that are
+ written to the cluster log in the event of transporter errors.
+ </para>
+
+ <informaltable>
+ <tgroup cols="3">
+ <colspec colwidth="10*"/>
+ <colspec colwidth="60*"/>
+ <colspec colwidth="30*"/>
+ <thead>
+ <row>
+ <entry>Error Code</entry>
+ <entry>Error Name</entry>
+ <entry>Error Text</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><errorcode>0x00</errorcode></entry>
+ <entry><errorname>TE_NO_ERROR</errorname></entry>
+ <entry><errortext>No error</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x01</errorcode></entry>
+ <entry><errorname>TE_ERROR_CLOSING_SOCKET</errorname></entry>
+ <entry><errortext>Error found during closing of socket</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x02</errorcode></entry>
+ <entry><errorname>TE_ERROR_IN_SELECT_BEFORE_ACCEPT</errorname></entry>
+ <entry><errortext>Error found before accept. The transporter will
+ retry</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x03</errorcode></entry>
+ <entry><errorname>TE_INVALID_MESSAGE_LENGTH</errorname></entry>
+ <entry><errortext>Error found in message (invalid message length)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x04</errorcode></entry>
+ <entry><errorname>TE_INVALID_CHECKSUM</errorname></entry>
+ <entry><errortext>Error found in message (checksum)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x05</errorcode></entry>
+ <entry><errorname>TE_COULD_NOT_CREATE_SOCKET</errorname></entry>
+ <entry><errortext>Error found while creating socket(can't create
+ socket)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x06</errorcode></entry>
+ <entry><errorname>TE_COULD_NOT_BIND_SOCKET</errorname></entry>
+ <entry><errortext>Error found while binding server socket</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x07</errorcode></entry>
+ <entry><errorname>TE_LISTEN_FAILED</errorname></entry>
+ <entry><errortext>Error found while listening to server socket</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x08</errorcode></entry>
+ <entry><errorname>TE_ACCEPT_RETURN_ERROR</errorname></entry>
+ <entry><errortext>Error found during accept(accept return error)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x0b</errorcode></entry>
+ <entry><errorname>TE_SHM_DISCONNECT</errorname></entry>
+ <entry><errortext>The remote node has disconnected</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x0c</errorcode></entry>
+ <entry><errorname>TE_SHM_IPC_STAT</errorname></entry>
+ <entry><errortext>Unable to check shm segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x0d</errorcode></entry>
+ <entry><errorname>TE_SHM_UNABLE_TO_CREATE_SEGMENT</errorname></entry>
+ <entry><errortext>Unable to create shm segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x0e</errorcode></entry>
+ <entry><errorname>TE_SHM_UNABLE_TO_ATTACH_SEGMENT</errorname></entry>
+ <entry><errortext>Unable to attach shm segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x0f</errorcode></entry>
+ <entry><errorname>TE_SHM_UNABLE_TO_REMOVE_SEGMENT</errorname></entry>
+ <entry><errortext>Unable to remove shm segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x10</errorcode></entry>
+ <entry><errorname>TE_TOO_SMALL_SIGID</errorname></entry>
+ <entry><errortext>Sig ID too small</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x11</errorcode></entry>
+ <entry><errorname>TE_TOO_LARGE_SIGID</errorname></entry>
+ <entry><errortext>Sig ID too large</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x12</errorcode></entry>
+ <entry><errorname>TE_WAIT_STACK_FULL</errorname></entry>
+ <entry><errortext>Wait stack was full</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x13</errorcode></entry>
+ <entry><errorname>TE_RECEIVE_BUFFER_FULL</errorname></entry>
+ <entry><errortext>Receive buffer was full</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x14</errorcode></entry>
+ <entry><errorname>TE_SIGNAL_LOST_SEND_BUFFER_FULL</errorname></entry>
+ <entry><errortext>Send buffer was full,and trying to force send
+ fails</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x15</errorcode></entry>
+ <entry><errorname>TE_SIGNAL_LOST</errorname></entry>
+ <entry><errortext>Send failed for unknown reason(signal lost)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x16</errorcode></entry>
+ <entry><errorname>TE_SEND_BUFFER_FULL</errorname></entry>
+ <entry><errortext>The send buffer was full, but sleeping for a while
+ solved</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x0017</errorcode></entry>
+ <entry><errorname>TE_SCI_LINK_ERROR</errorname></entry>
+ <entry><errortext>There is no link from this node to the switch</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x18</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_START_SEQUENCE</errorname></entry>
+ <entry><errortext>Could not start a sequence, because system resources are
+ exumed or no sequence has been created</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x19</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_REMOVE_SEQUENCE</errorname></entry>
+ <entry><errortext>Could not remove a sequence</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x1a</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_CREATE_SEQUENCE</errorname></entry>
+ <entry><errortext>Could not create a sequence, because system resources are
+ exempted. Must reboot</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x1b</errorcode></entry>
+ <entry><errorname>TE_SCI_UNRECOVERABLE_DATA_TFX_ERROR</errorname></entry>
+ <entry><errortext>Tried to send data on redundant link but failed</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x1c</errorcode></entry>
+ <entry><errorname>TE_SCI_CANNOT_INIT_LOCALSEGMENT</errorname></entry>
+ <entry><errortext>Cannot initialize local segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x1d</errorcode></entry>
+ <entry><errorname>TE_SCI_CANNOT_MAP_REMOTESEGMENT</errorname></entry>
+ <entry><errortext>Cannot map remote segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x1e</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_UNMAP_SEGMENT</errorname></entry>
+ <entry><errortext>Cannot free the resources used by this segment (step
+ 1)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x1f</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_REMOVE_SEGMENT</errorname></entry>
+ <entry><errortext>Cannot free the resources used by this segment (step
+ 2)</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x20</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_DISCONNECT_SEGMENT</errorname></entry>
+ <entry><errortext>Cannot disconnect from a remote segment</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x21</errorcode></entry>
+ <entry><errorname>TE_SHM_IPC_PERMANENT</errorname></entry>
+ <entry><errortext>Shm ipc Permanent error</errortext></entry>
+ </row>
+ <row>
+ <entry><errorcode>0x22</errorcode></entry>
+ <entry><errorname>TE_SCI_UNABLE_TO_CLOSE_CHANNEL</errorname></entry>
+ <entry><errortext>Unable to close the sci channel and the resources
+ allocated</errortext></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+
+ </section>
+
+ </section>
+
<section id="mysql-cluster-single-user-mode">
<title>Single User Mode</title>
Modified: trunk/refman-5.1/Makefile.depends
===================================================================
--- trunk/refman-5.1/Makefile.depends 2008-07-22 08:33:38 UTC (rev 11306)
+++ trunk/refman-5.1/Makefile.depends 2008-07-22 10:21:18 UTC (rev 11307)
Changed blocks: 7, Lines Added: 14, Lines Deleted: 0; 4139 bytes
@@ -1482,6 +1482,8 @@
../refman-common/images/published/cluster-circular-replication-2.png \
../refman-common/images/published/cluster-components-1.png \
../refman-common/images/published/cluster-replication-binlog-injector.png \
+ ../refman-common/images/published/cluster-replication-log-slave-updates.png \
+ ../refman-common/images/published/cluster-replication-multi-master.png \
../refman-common/images/published/cluster-replication-overview.png \
../refman-common/images/published/cluster-security-network-1.png \
../refman-common/images/published/cluster-security-network-2.png \
@@ -1686,6 +1688,8 @@
../refman-common/images/published/cluster-circular-replication-2.png \
../refman-common/images/published/cluster-components-1.png \
../refman-common/images/published/cluster-replication-binlog-injector.png \
+ ../refman-common/images/published/cluster-replication-log-slave-updates.png \
+ ../refman-common/images/published/cluster-replication-multi-master.png \
../refman-common/images/published/cluster-replication-overview.png \
../refman-common/images/published/cluster-security-network-1.png \
../refman-common/images/published/cluster-security-network-2.png \
@@ -2026,6 +2030,8 @@
mysql_cluster_management_IMAGES =
mysql_cluster_management_SOURCES = mysql-cluster-management.xml $(mysql_cluster_management_INCLUDES)
mysql_cluster_management_IDMAPS = \
+ ../ndbapi/metadata/mgm-api.idmap \
+ ../ndbapi/metadata/ndb-errors.idmap \
../
