Oracle 5.0 Reference Manual page 1685

Note that events are reported per data node, and that the threshold can be set to different values on
different nodes.
Category
STARTUP
SHUTDOWN
STATISTICS
CHECKPOINT
NODERESTART
CONNECTION
ERROR
INFO
The category can provide a great deal of useful data. See
STATISTICS
CLUSTERLOG STATISTICS
Thresholds are used to filter events within each category. For example, a
of 3 is not logged unless the threshold for
lower are sent if the threshold is 3.
The following table shows the event severity levels.
Note
These correspond to Unix
LOG_NOTICE, which are not used or mapped.
Severity Level Severity
Value
1
ALERT
2
CRITICAL
3
ERROR
4
WARNING
5
INFO
6
DEBUG
Event severity levels can be turned on or off (using
level is turned on, then all events with a priority less than or equal to the category thresholds are
logged. If the severity level is turned off then no events belonging to that severity level are logged.
Important
Cluster log levels are set on a per ndb_mgmd, per subscriber basis. This
means that, in a MySQL Cluster with multiple management servers, using
a
CLUSTERLOG
management server affects only logs generated by that management server but
not by any of the others. This also means that, should one of the management
servers be restarted, only logs generated by that management server are
affected by the resetting of log levels caused by the restart.
Event Reports Generated in MySQL Cluster
Default threshold (All data nodes)
7
7
7
7
7
7
15
7
in the MySQL Cluster Management
STARTUP
syslog
Description
A condition that should be corrected immediately, such as a
corrupted system database
Critical conditions, such as device errors or insufficient
resources
Conditions that should be corrected, such as configuration
errors
Conditions that are not errors, but that might require special
handling
Informational messages
Debugging messages used for
command in an instance of
1665
Section 17.5.6.3, "Using
Client", for more information.
STARTUP
is set to 3 or higher. Only events with priority 3 or
levels, except for
LOG_EMERG
NDBCLUSTER
FILTER—see above). If a severity
CLUSTERLOG
connected to one
ndb_mgm
event with a priority
and
development