content_image/804626.jpg
2007-01-26 19:35:55 [MgmSrvr] INFO -- Node 4: Data usage is 2%(74 32K pages of total 2560) 2007-01-26 19:35:55 [MgmSrvr] INFO -- Node 4: Index usage is 1%(25 8K pages of total 2336) 2007-01-26 19:35:55 [MgmSrvr] INFO -- Node 4: Resource 0 min: 0 max: 639 curr: 0 2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 4: Node 9 Connected 2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 1: Node 9 Connected 2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 1: Node 9: API 8.0.26-ndb-8.0.26 2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 2: Node 9 Connected 2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 2: Node 9: API 8.0.26-ndb-8.0.26 2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 3: Node 9 Connected 2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 3: Node 9: API 8.0.26-ndb-8.0.26 2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 4: Node 9: API 8.0.26-ndb-8.0.26 2007-01-26 19:59:22 [MgmSrvr] ALERT -- Node 2: Node 7 Disconnected 2007-01-26 19:59:22 [MgmSrvr] ALERT -- Node 2: Node 7 Disconnected 

Each line in the cluster log contains the following information: 

•A timestamp in YYYY - MM - DD HH : MM : SS  format. 

•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. 

## 23.5.3.1 NDB Cluster Logging Management Commands 

ndb_mgm  supports a number of management commands related to the cluster log and node logs. In the listing that follows, node_id  denotes either a storage node ID or the keyword ALL , which indicates that the 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  events with priority less than or equal to threshold  in the cluster log. 

• 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. 

<img src='content_image/804626.jpg'>

## Note 

Events are reported per data node, and that the threshold can be set to different values on different nodes. 

