Description.
Like ndb_mgm_restart2(), this function
can be used to cause an initial restart, waiting restart,
and immediate (forced) restart on one or more Cluster data
nodes. However, ndb_mgm_restart3()
provides additional the additional options of checking
whether disconnection is required prior to the restart.
Signature.
int ndb_mgm_restart3
(
NdbMgmHandle handle,
int number,
const int* list,
int initial
int nostart,
int abort,
int* disconnect
)
Parameters. ndb_mgm_restart() takes 7 parameters:
An NdbMgmHandle.
The number of nodes to be
stopped. Use 0 to stop all of the
data nodes in the cluster.
A list of the node IDs of
the nodes to be stopped.
If initial is true
(1), then each node undergoes an
initial restart — that is, its file system is
removed.
If nostart is true, then the nodes
are not actually started, but instead are left ready
for a start command.
If abort is true, then the
nodes are forced to restart immediately without
performing a graceful restart.
If disconnect returns
1 (true), this
means the you must disconnect before you can apply the
command to restart. For example, disconnecting is
required when stopping the management server to which
the handle is connected.
Return value.
The number of nodes actually restarted;
-1 on failure.
