Oracle 5.0 Reference Manual page 1684

2007-01-26 19:35:55 [MgmSrvr] INFO
2007-01-26 19:35:55 [MgmSrvr] INFO
2007-01-26 19:35:55 [MgmSrvr] INFO
2007-01-26 19:35:55 [MgmSrvr] INFO
2007-01-26 19:35:55 [MgmSrvr] INFO
2007-01-26 19:35:55 [MgmSrvr] INFO
2007-01-26 19:35:55 [MgmSrvr] INFO
2007-01-26 19:35:55 [MgmSrvr] INFO
2007-01-26 19:35:55 [MgmSrvr] INFO
2007-01-26 19:35:55 [MgmSrvr] INFO
2007-01-26 19:35:55 [MgmSrvr] INFO
2007-01-26 19:39:42 [MgmSrvr] INFO
2007-01-26 19:39:42 [MgmSrvr] INFO
2007-01-26 19:39:42 [MgmSrvr] INFO
2007-01-26 19:39:42 [MgmSrvr] INFO
2007-01-26 19:39:42 [MgmSrvr] INFO
2007-01-26 19:39:42 [MgmSrvr] INFO
2007-01-26 19:39:42 [MgmSrvr] INFO
2007-01-26 19:39:42 [MgmSrvr] INFO
2007-01-26 19:59:22 [MgmSrvr] ALERT
2007-01-26 19:59:22 [MgmSrvr] ALERT
Each line in the cluster log contains the following information:
• A timestamp in
• The type of node which is performing the logging. In the cluster log, this is always [MgmSrvr].
• The severity of the event.
• The ID of the node reporting the event.
• A description of the event. The most common types of events to appear in the log are connections
and disconnections between different nodes in the cluster, and when checkpoints occur. In some
cases, the description may contain status information.
17.5.6.1. MySQL Cluster Logging Management Commands
supports a number of management commands related to the cluster log. In the listing that
ndb_mgm
follows,
node_id
command should be applied to all of the cluster's data nodes.
•
CLUSTERLOG ON
Turns the cluster log on.
•
CLUSTERLOG OFF
Turns the cluster log off.
•
CLUSTERLOG INFO
Provides information about cluster log settings.
•
node_id CLUSTERLOG category=threshold
Logs
category
•
CLUSTERLOG FILTER severity_level
Toggles cluster logging of events of the specified severity_level.
The following table describes the default setting (for all data nodes) of the cluster log category
threshold. If an event has a priority with a value lower than or equal to the priority threshold, it is
reported in the cluster log.
Event Reports Generated in MySQL Cluster
YYYY-MM-DD HH:MM:SS
denotes either a database node ID or the keyword ALL, which indicates that the
events with priority less than or equal to
-- Node 1: Index usage is 1%(24 8K pages of total 2336)
-- Node 1: Resource 0 min: 0 max: 639 curr: 0
-- Node 2: Data usage is 2%(76 32K pages of total 2560)
-- Node 2: Index usage is 1%(24 8K pages of total 2336)
-- Node 2: Resource 0 min: 0 max: 639 curr: 0
-- Node 3: Data usage is 2%(58 32K pages of total 2560)
-- Node 3: Index usage is 1%(25 8K pages of total 2336)
-- Node 3: Resource 0 min: 0 max: 639 curr: 0
-- Node 4: Data usage is 2%(74 32K pages of total 2560)
-- Node 4: Index usage is 1%(25 8K pages of total 2336)
-- Node 4: Resource 0 min: 0 max: 639 curr: 0
-- Node 4: Node 9 Connected
-- Node 1: Node 9 Connected
-- Node 1: Node 9: API version 5.1.15
-- Node 2: Node 9 Connected
-- Node 2: Node 9: API version 5.1.15
-- Node 3: Node 9 Connected
-- Node 3: Node 9: API version 5.1.15
-- Node 4: Node 9: API version 5.1.15
-- Node 2: Node 7 Disconnected
-- Node 2: Node 7 Disconnected
format.
threshold
1664
in the cluster log.