Documentation Home
MySQL Cluster API Developer Guide
Download this Manual
PDF (US Ltr) - 5.2Mb
PDF (A4) - 5.2Mb
EPUB - 2.2Mb
HTML Download (TGZ) - 2.1Mb
HTML Download (Zip) - 2.2Mb


MySQL Cluster API Developer Guide  /  MySQL Cluster Internals  /  MySQL Cluster Management Client DUMP Commands

8.2 MySQL Cluster Management Client DUMP Commands

[+/-]

8.2.1 DUMP 1
8.2.2 DUMP 13
8.2.3 DUMP 14
8.2.4 DUMP 15
8.2.5 DUMP 16
8.2.6 DUMP 17
8.2.7 DUMP 18
8.2.8 DUMP 20
8.2.9 DUMP 21
8.2.10 DUMP 22
8.2.11 DUMP 23
8.2.12 DUMP 24
8.2.13 DUMP 25
8.2.14 DUMP 70
8.2.15 DUMP 400
8.2.16 DUMP 401
8.2.17 DUMP 402
8.2.18 DUMP 403
8.2.19 DUMP 404 (OBSOLETE)
8.2.20 DUMP 908
8.2.21 DUMP 1000
8.2.22 DUMP 1223
8.2.23 DUMP 1224
8.2.24 DUMP 1225
8.2.25 DUMP 1226
8.2.26 DUMP 1228
8.2.27 DUMP 1229
8.2.28 DUMP 1332
8.2.29 DUMP 1333
8.2.30 DUMP 2300
8.2.31 DUMP 2301
8.2.32 DUMP 2302
8.2.33 DUMP 2303
8.2.34 DUMP 2304
8.2.35 DUMP 2305
8.2.36 DUMP 2308
8.2.37 DUMP 2315
8.2.38 DUMP 2350
8.2.39 DUMP 2352
8.2.40 DUMP 2354
8.2.41 DUMP 2398
8.2.42 DUMP 2399
8.2.43 DUMP 2400
8.2.44 DUMP 2401
8.2.45 DUMP 2402
8.2.46 DUMP 2403
8.2.47 DUMP 2404
8.2.48 DUMP 2405
8.2.49 DUMP 2406
8.2.50 DUMP 2500
8.2.51 DUMP 2501
8.2.52 DUMP 2502
8.2.53 DUMP 2503 (OBSOLETE)
8.2.54 DUMP 2504
8.2.55 DUMP 2505
8.2.56 DUMP 2506 (OBSOLETE)
8.2.57 DUMP 2507
8.2.58 DUMP 2508
8.2.59 DUMP 2509
8.2.60 DUMP 2510
8.2.61 DUMP 2511
8.2.62 DUMP 2512
8.2.63 DUMP 2513
8.2.64 DUMP 2514
8.2.65 DUMP 2515
8.2.66 DUMP 2516
8.2.67 DUMP 2517
8.2.68 DUMP 2550
8.2.69 DUMP 2555
8.2.70 DUMP 2600
8.2.71 DUMP 2601
8.2.72 DUMP 2602
8.2.73 DUMP 2603
8.2.74 DUMP 2604
8.2.75 DUMP 5900
8.2.76 DUMP 7000
8.2.77 DUMP 7001
8.2.78 DUMP 7002
8.2.79 DUMP 7003
8.2.80 DUMP 7004
8.2.81 DUMP 7005
8.2.82 DUMP 7006
8.2.83 DUMP 7007
8.2.84 DUMP 7008
8.2.85 DUMP 7009
8.2.86 DUMP 7010
8.2.87 DUMP 7011
8.2.88 DUMP 7012
8.2.89 DUMP 7013
8.2.90 DUMP 7014
8.2.91 DUMP 7015
8.2.92 DUMP 7016
8.2.93 DUMP 7017
8.2.94 DUMP 7018
8.2.95 DUMP 7019
8.2.96 DUMP 7020
8.2.97 DUMP 7021
8.2.98 DUMP 7024
8.2.99 DUMP 7033
8.2.100 DUMP 7080
8.2.101 DUMP 7090
8.2.102 DUMP 7098
8.2.103 DUMP 7099
8.2.104 DUMP 7901
8.2.105 DUMP 8004
8.2.106 DUMP 8005
8.2.107 DUMP 8010
8.2.108 DUMP 8011
8.2.109 DUMP 8013
8.2.110 DUMP 9002
8.2.111 DUMP 9800
8.2.112 DUMP 9801
8.2.113 DUMP 9802
8.2.114 DUMP 9803
8.2.115 DUMP 10000
8.2.116 DUMP 11000
8.2.117 DUMP 12001
8.2.118 DUMP 12002
8.2.119 DUMP 12009
Warning

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 reasons:

  • 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 the following information:

  • The code value

  • The relevant NDB kernel block or blocks (see Section 8.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.

Note

DUMP codes in the following ranges are currently unused and thus unsupported:

  • 3000 to 5000

  • 6000 to 7000

  • 13000 and higher


User Comments
Sign Up Login You must be logged in to post a comment.