Never use these commands on a production MySQL Cluster except under the express direction of MySQL Technical Support. Oracle will not be held responsible for adverse results arising from their use under any other circumstances!
DUMP commands can be used in the Cluster
management client (ndb_mgm) to dump debugging
information to the Cluster log. They are documented here, rather
than in the MySQL Manual, for the following
They are intended only for use in troubleshooting, debugging, and similar activities by MySQL developers, QA, and support personnel.
Due to the way in which
interact with memory, they can cause a running MySQL Cluster
to malfunction or even to fail completely when used.
The formats, arguments, and even availability of these commands are not guaranteed to be stable. All of this information is subject to change at any time without prior notice.
For the preceding reasons,
are neither intended nor warranted for use in a production
environment by end-users.
This causes the contents of one or more
registers on the node with ID
to be dumped to the Cluster log. The registers affected are
determined by the value of
(but not all)
DUMP commands accept additional
arguments; these are noted and
described where applicable.
DUMP commands are listed by their
code values in the sections that
follow. For convenience in locating a given
DUMP code, they are divided by thousands.
Each listing includes the following information:
NDB kernel block or blocks
(see Section 8.4, “NDB Kernel Blocks”, for
information about these)
DUMP code symbol where defined; if
undefined, this is indicated using a triple dash:
Sample output; unless otherwise stated, it is assumed that
DUMP command is invoked as shown here:
Generally, this is from the cluster log; in some cases, where the output may be generated in the node log instead, this is indicated. Where the DUMP command produces errors, the output is generally taken from the error log.
Where applicable, additional information such as possible
arguments, warnings, state or
other values returned in the
output, and so on. Otherwise its absence is indicated with
DUMP command codes are not necessarily
defined sequentially. For example, codes
12 are currently undefined, and so
are not listed. However, individual
values are subject to change, and there is no guarantee that a
given code value will continue to be defined for the same
purpose (or defined at all, or undefined) over time.
There is also no guarantee that a given
code—even if currently undefined—will not have
serious consequences when used on a running MySQL Cluster.