89330

Event Reports Generated in MySQL Cluster

In this section, we discuss the types of event logs provided by MySQL Cluster, and the types of events that are logged.

MySQL Cluster provides two types of event log:

•    The cluster log, which includes events generated by all cluster nodes. The cluster log is the log

recommended for most uses because it provides logging information for an entire

cluster in a single

location.

By default, the cluster log is saved to a file named ndb_node_id_cluster. log, (where node_id

is the node ID of the management server) in the same directory where the ndb mgmbinary resides.

Cluster logging information can also be sent to stdoutor a syslog facility in addition to or

instead of being saved to a file, as determined by the values set for the DataDir[2199] and

LogDestination[2197] configuration parameters. See Section 17.3.2.5, “Defining a MySQL

Cluster Management Server", for morę information about these parameters.

•    Node logs are local to each node.

Output generated by node event logging is written to the file

ndb_node_id_out. log (where

node_idis the node's node ID) in the node‘s DataDir[2203], Node event logs are generated for

both management nodes and data nodes.

Node logs are intended to be used only during application development, or for

debugging application

codę.

Both types of event logs can be set to log different subsets of events.

Each reportable event can be distinguished according to three different criteria:

•    Category: This can be any one of the following values: STARTUP, SHUTDOWN, STATISTICS,

CHECKPOINT, NODERESTART, CONNECTION, ERROR, or INFO.

•    Priority. This is represented by one of the numbers from 1 to 15 inclusive, where 1 indicates “most

important” and 15 “least important."

•    Severity Level: This can be any one of the following values: ALERT, CRITICAL, ERROR, WARN ING,

INFO, orDEBUG.

Both the cluster log and the node log can be filtered on these properties.