The local checkpoint having sequence ID lcp
has been started on node
node_id. The most recent GCI
that can be used has the index
current_gci, and the oldest GCI
from which the cluster can be restored has the index
old_gci.

LocalCheckpointStarted

Checkpoint

7

INFO

Node node_id: Local checkpoint
lcp completed

The local checkpoint having sequence ID lcp
on node node_id has been
completed.

The reporting node (ID node_id) was unable to
accept node president_id as
president. The cause of the
problem is given as one of Busy,
Election with wait = false,
Not president, Election
without selecting new candidate, or No
such cause.

CM_REGREF

StartUp

8

INFO

Node node_id: We are Node
own_id with dynamic ID
dynamic_id, our left neighbor
is Node id_1, our right is Node
id_2

The node has discovered its neighboring nodes in the cluster (node
id_1 and node
id_2).
node_id,
own_id, and
dynamic_id should always be the
same; if they are not, this indicates a serious
misconfiguration of the cluster nodes.

FIND_NEIGHBOURS

StartUp

8

INFO

Node node_id:
type shutdown
initiated

The node has received a shutdown signal. The
type of shutdown is either
Cluster or Node.

The node has been shut down. This report may include an
action, which if present is one
of restarting, no
start, or initial. The report
may also include a reference to an
NDB Protocol
signal; for possible signals,
refer to
Operations and Signals.

The node has been forcibly shut down. The
action (one of
restarting, no
start, or initial)
subsequently being taken, if any, is also reported. If the
shutdown occurred while the node was starting, the report
includes the start_phase during
which the node failed. If this was a result of a
signal sent to the node, this
information is also provided (see
Operations and Signals,
for more information). If the error causing the failure is
known, this is also included; for more information about
NDB error messages and
classifications, see NDB Cluster API Errors.

This reports global checkpoints referenced during a node start. The redo
log prior to keep_pos is
dropped. last_pos is the last
global checkpoint in which data node the participated;
restore_pos is the global
checkpoint which is actually used to restore all data
nodes.

Copying of all table fragments to restarting data node
node_id has been completed

NR_CopyFragsCompleted

NodeRestart

8

INFO

Node node_id: Node
node1_id completed failure of
Node node2_id

Data node node1_id has detected the failure
of data node node2_id

NodeFailCompleted

NodeRestart

8

ALERT

All nodes completed failure of Node
node_id

All (remaining) data nodes have detected the failure of data node
node_id

NodeFailCompleted

NodeRestart

8

ALERT

Node failure of
node_idblock
completed

The failure of data node node_id has been
detected in the
blockNDB
kernel block, where block is 1 of DBTC,
DBDICT, DBDIH, or
DBLQH; for more information, see
NDB Kernel Blocks

NodeFailCompleted

NodeRestart

8

ALERT

Node mgm_node_id: Node
data_node_id has failed. The
Node state at failure was
state_code

A data node has failed. Its state at the time of failure is described by
an arbitration state code
state_code: possible state code
values can be found in the file
include/kernel/signaldata/ArbitSignalData.hpp.

This is a report on the current state and progress of arbitration in the
cluster. node_id is the node ID
of the management node or SQL node selected as the
arbitrator. state_code is an
arbitration state code, as found in
include/kernel/signaldata/ArbitSignalData.hpp.
When an error has occurred, an
error_message, also defined in
ArbitSignalData.hpp, is provided.
ticket_id is a unique
identifier handed out by the arbitrator when it is
selected to all the nodes that participated in its
selection; this is used to ensure that each node
requesting arbitration was one of the nodes that took part
in the selection process.

ArbitState

NodeRestart

6

INFO

Arbitration check lost - less than 1/2 nodes left or
Arbitration check won - all node groups and more
than 1/2 nodes left or Arbitration
check won - node group majority or
Arbitration check lost - missing node
group or Network partitioning -
arbitration required or Arbitration won
- positive reply from node
node_id or
Arbitration lost - negative reply from node
node_id or
Network partitioning - no arbitrator
available or Network partitioning - no
arbitrator configured or Arbitration
failure - error_message
[state=state_code]

This message reports on the result of arbitration. In the event of
arbitration failure, an
error_message and an
arbitration state_code are
provided; definitions for both of these are found in
include/kernel/signaldata/ArbitSignalData.hpp.

ArbitResult

NodeRestart

2

ALERT

Node node_id: GCP Take over
started

This node is attempting to assume responsibility for the next global
checkpoint (that is, it is becoming the master node)

GCP_TakeoverStarted

NodeRestart

7

INFO

Node node_id: GCP Take over
completed

This node has become the master, and has assumed responsibility for the
next global checkpoint

GCP_TakeoverCompleted

NodeRestart

7

INFO

Node node_id: LCP Take over
started

This node is attempting to assume responsibility for the next set of
local checkpoints (that is, it is becoming the master
node)

LCP_TakeoverStarted

NodeRestart

7

INFO

Node node_id: LCP Take over
completed

This node has become the master, and has assumed responsibility for the
next set of local checkpoints

This report is seen during heavy event buffer usage, for example, when
many updates are being applied in a relatively short
period of time; the report shows the number of bytes and
the percentage of event buffer memory used, the bytes
allocated and percentage still available, and the latest
and latest restorable epochs

These reports are written to the cluster log when entering and exiting
single user mode; API_node_id
is the node ID of the API or SQL having exclusive access
to the cluster (for more information, see
Section 18.5.8, “NDB Cluster Single User Mode”); the
message Unknown single user report
API_node_id indicates
an error has taken place and should never be seen in
normal operation