Rechercher dans le manuel MySQL
Reads a redo log file, checking it for errors, printing its contents in a human-readable format, or both. ndb_redo_log_reader is intended for use primarily by NDB Cluster developers and Support personnel in debugging and diagnosing problems.
This utility remains under development, and its syntax and behavior are subject to change in future NDB Cluster releases.
Prior to NDB 7.2, this utility was named ndbd_redo_log_reader.
The C++ source files for ndb_redo_log_reader
can be found in the directory
/storage/ndb/src/kernel/blocks/dblqh/redoLogReader
.
The following table includes options that are specific to the NDB Cluster program ndb_redo_log_reader. Additional descriptions follow the table. For options common to most NDB Cluster programs (including ndb_redo_log_reader), see Section 22.4.31, “Options Common to NDB Cluster Programs — Options Common to NDB Cluster Programs”.
Table 22.349 Command-line options for the ndb_redo_log_reader program
Format | Description | Added, Deprecated, or Removed |
---|---|---|
Print dump info | All NDB 8.0 releases |
|
Print file descriptors only | All NDB 8.0 releases |
|
Print usage information | All NDB 8.0 releases |
|
Provide lap info, with max GCI started and completed | All NDB 8.0 releases |
|
Starting megabyte | All NDB 8.0 releases |
|
Show only the first page header of every megabyte in the file | All NDB 8.0 releases |
|
Do not check records for errors | All NDB 8.0 releases |
|
Do not print records | All NDB 8.0 releases |
|
Start with this page | All NDB 8.0 releases |
|
Show page headers only | All NDB 8.0 releases |
|
Start with this page index | All NDB 8.0 releases |
|
Bit-shifted dump | All NDB 8.0 releases |
Usage
ndb_redo_log_reader file_name [options]
file_name
is the name of a cluster
redo log file. redo log files are located in the numbered
directories under the data node's data directory
(DataDir
); the path
under this directory to the redo log files matches the pattern
ndb_
.
nodeid
_fs/D#
/DBLQH/S#
.FragLognodeid
is the data node's node
ID. The two instances of #
each
represent a number (not necessarily the same number); the number
following D
is in the range 8-39 inclusive;
the range of the number following S
varies
according to the value of the
NoOfFragmentLogFiles
configuration parameter, whose default value is 16; thus, the
default range of the number in the file name is 0-15 inclusive.
For more information, see
NDB Cluster Data Node File System Directory Files.
The name of the file to be read may be followed by one or more of the options listed here:
-
Property Value Command-Line Format -dump
Type Boolean Default Value FALSE
Print dump info.
-
Property Value Command-Line Format -filedescriptors
Type Boolean Default Value FALSE
-filedescriptors
: Print file descriptors only. -
Property Value Command-Line Format --help
--help
: Print usage information. -
Property Value Command-Line Format -lap
Type Boolean Default Value FALSE
Provide lap info, with max GCI started and completed.
-
Property Value Command-Line Format -mbyte #
Type Numeric Default Value 0
Minimum Value 0
Maximum Value 15
-mbyte
: Starting megabyte.#
#
is an integer in the range 0 to 15, inclusive. -
Property Value Command-Line Format -mbyteheaders
Type Boolean Default Value FALSE
-mbyteheaders
: Show only the first page header of every megabyte in the file. -
Property Value Command-Line Format -noprint
Type Boolean Default Value FALSE
-noprint
: Do not print the contents of the log file. -
Property Value Command-Line Format -nocheck
Type Boolean Default Value FALSE
-nocheck
: Do not check the log file for errors. -
Property Value Command-Line Format -page #
Type Integer Default Value 0
Minimum Value 0
Maximum Value 31
-page
: Start at this page.#
#
is an integer in the range 0 to 31, inclusive. -
Property Value Command-Line Format -pageheaders
Type Boolean Default Value FALSE
-pageheaders
: Show page headers only. -
Property Value Command-Line Format -pageindex #
Type Integer Default Value 12
Minimum Value 12
Maximum Value 8191
-pageindex
: Start at this page index.#
#
is an integer between 12 and 8191, inclusive. -
Property Value Command-Line Format -twiddle
Type Boolean Default Value FALSE
Bit-shifted dump.
Like ndb_print_backup_file and
ndb_print_schema_file (and unlike most of the
NDB
utilities that are intended to
be run on a management server host or to connect to a management
server) ndb_redo_log_reader must be run on a
cluster data node, since it accesses the data node file system
directly. Because it does not make use of the management server,
this utility can be used when the management server is not
running, and even when the cluster has been completely shut
down.
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-mysql-cluster-programs-ndb-redo-log-reader.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.