Oracle 5.0 Reference Manual page 1687

Event
Undo records executed
New REDO log started
New log started
Node has been refused for
inclusion in the cluster
data node neighbors
data node start phase
Node has been successfully
included into the cluster
data node start phases initiated
data node all start phases
completed
data node shutdown initiated
data node shutdown aborted
Events
NODERESTART
The following events are generated when restarting a node and relate to the success or failure of the
node restart process.
Event
Node failure phase completed
Node has failed, node state was
Report arbitrator results
Completed copying a fragment
Event Reports Generated in MySQL Cluster
Priority
15
10
10
8
8
completed 4
X
3
1
1
1
1
Priority
8
8
X
2
10
1667
Severity Description
Level
INFO
GCI keep X, newest restorable GCI
INFO
Log part X, start MB Y, stop MB
INFO
Node cannot be included in cluster due
INFO
to misconfiguration, inability to establish
communication, or other problem
Shows neighboring data nodes
INFO
A data node start phase has been completed
INFO
Displays the node, managing node, and
INFO
dynamic ID
NDB Cluster nodes starting
INFO
NDB Cluster nodes started
INFO
Shutdown of data node has commenced
INFO
Unable to shut down data node normally
INFO
Severity Description
Level
Reports completion of node failure phases
ALERT
Reports that a node has failed
ALERT
There are eight different possible results for
ALERT
arbitration attempts:
• Arbitration check failed—less than 1/2
nodes left
• Arbitration check succeeded—node group
majority
• Arbitration check failed—missing node
group
• Network partitioning—arbitration required
• Arbitration succeeded—affirmative
response from node
• Arbitration failed - negative response from
node
X
• Network partitioning - no arbitrator
available
• Network partitioning - no arbitrator
configured
INFO
Y
Z
X