Skip navigation links
6.2.1 DUMP Codes 1 to 999 »
Section Navigation      [Toggle]

6.2. DUMP Commands

[+/-]

6.2.1. DUMP Codes 1 to 999
6.2.2. DUMP Codes 1000 to 1999
6.2.3. DUMP Codes 2000 to 2999
6.2.4. DUMP Codes 3000 to 3999
6.2.5. DUMP Codes 4000 to 4999
6.2.6. DUMP Codes 5000 to 5999
6.2.7. DUMP Codes 6000 to 6999
6.2.8. DUMP Codes 7000 to 7999
6.2.9. DUMP Codes 8000 to 8999
6.2.10. DUMP Codes 9000 to 9999
6.2.11. DUMP Codes 10000 to 10999
6.2.12. DUMP Codes 11000 to 11999
6.2.13. DUMP Codes 12000 to 12999

Warning

Never use these commands on a production MySQL Cluster except under the express direction of MySQL Technical Support. MySQL AB 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 because:

  • 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 DUMP commands 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, DUMP commands are neither intended nor warranted for use in a production environment by end-users.

General syntax: 

ndb_mgm> node_id DUMP code [arguments]

This causes the contents of one or more NDB registers on the node with ID node_id to be dumped to the Cluster log. The registers affected are determined by the value of code. Some (but not all) DUMP commands accept additional arguments; these are noted and described where applicable.

Individual 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 this information:

  • The code value

  • The relevant NDB kernel block or blocks (see Section 6.4, “NDB Kernel Blocks”, for information about these)

  • The DUMP code symbol where defined; if undefined, this is indicated using a triple dash: ---.

  • Sample output; unless otherwise stated, it is assumed that each DUMP command is invoked as shown here: 

    ndb_mgm> 2 DUMP code

    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 extra arguments, warnings, state or other values returned in the DUMP command's output, and so on. Otherwise its absence is indicated with “[N/A]”.

Note

DUMP command codes are not necessarily defined sequentially. For example, codes 2 through 12 are currently undefined, and so are not listed. However, individual DUMP code 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 DUMP code — even if currently undefined — will not have serious consequences when used on a running MySQL Cluster.

For information concerning other ndb_mgm client commands, see Commands in the MySQL Cluster Management Client.