In QMGR
the president starts
an arbitrator (unless this feature has been disabled by setting
the value of the ArbitrationRank
configuration parameter to 0 for all nodes—see
Defining an NDB Cluster Management Server, and
Defining SQL and Other API Nodes in an NDB Cluster, for more
information. In addition, checking of API nodes through
heartbeats is activated.
Also during this phase, the
BACKUP
block sets the disk
write speed to the value used following the completion of the
restart. The master node during initial start also inserts the
record keeping track of which backup ID is to be used next. The
SUMA
and
DBTUX
blocks set variables
indicating start phase 7 has been completed, and that requests
to DBTUX
that occurs when running the redo
log should no longer be ignored.