In NDB Cluster 7.4 and later, thisDUMP code prints a set of scan fragment records to the cluster log.
- Code
2500
- Symbol
TcDumpSetOfScanFragRec- Kernel Block
Description. ThisDUMP code uses the syntax shown here:
DUMP 2500recordnonumrecordsdbtcinst [activeonly] This printsnumrecords records fromDBTC instancedbtcinst, starting with the record having record numberrecno. The last argument is optional; all of the others shown are required.activeonly is a boolean that determines whether or not to print only active records. If set to 1 (actually, any nonzero value), only active records are printed and ignore any free records not in use for the moment. 0 means all records are included. The default is 1.
Sample Output.
。。。Additional Information. [N/A]
Prior to NDB Cluster 7.4, thisDUMP code had a different symbol and function, as described in this table and the notes that follow.
- Code
2500
- Symbol
TcDumpAllScanFragRec- Kernel Block
Description. Kills the data node.
Sample Output.
Time: Sunday 01 November 2015 - 13:37:11Status: Temporary error, restart nodeMessage: Assertion (Internal error, programming error or missing errormessage, please report a bug)Error: 2301Error data: ArrayPool<T>::getPtrError object: ../../../../../storage/ndb/src/kernel/vm/ArrayPool.hpp line: 345(block: CMVMI)Program: ./libexec/ndbdPid: 13237Trace: /usr/local/mysql/cluster/ndb_2_trace.log.1Version: Version 5.6.21-ndb-7.3.7