Event Reports Generated in MySQL Cluster
1665
Note that events are reported per data node, and that the threshold can be set to different values on
different nodes.
Category
Default threshold (All data nodes)
STARTUP
7
SHUTDOWN
7
STATISTICS
7
CHECKPOINT
7
NODERESTART
7
CONNECTION
7
ERROR
15
INFO
7
The
STATISTICS
category can provide a great deal of useful data. See
Section 17.5.6.3, “Using
CLUSTERLOG STATISTICS
in the MySQL Cluster Management Client”
, for more information.
Thresholds are used to filter events within each category. For example, a
STARTUP
event with a priority
of 3 is not logged unless the threshold for
STARTUP
is set to 3 or higher. Only events with priority 3 or
lower are sent if the threshold is 3.
The following table shows the event severity levels.
Note
These correspond to Unix
syslog
levels, except for
LOG_EMERG
and
LOG_NOTICE
, which are not used or mapped.
Severity Level
Value
Severity
Description
1
ALERT
A condition that should be corrected immediately, such as a
corrupted system database
2
CRITICAL
Critical conditions, such as device errors or insufficient
resources
3
ERROR
Conditions that should be corrected, such as configuration
errors
4
WARNING
Conditions that are not errors, but that might require special
handling
5
INFO
Informational messages
6
DEBUG
Debugging messages used for
NDBCLUSTER
development
Event severity levels can be turned on or off (using
CLUSTERLOG FILTER
—see above). If a severity
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
command in an instance of
ndb_mgm
connected to one
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.
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...