Reads a redo log file, checking it for errors, printing its contents in a human-readable format, or both. ndbd_redo_log_reader is intended for use primarily by MySQL Cluster developers and Support personnel in debugging and diagnosing problems.
This utility was made available as part of default builds beginning with MySQL Cluster NDB 6.1.3. It remains under development, and its syntax and behavior are subject to change in future releases. For this reason, it should be considered experimental at this time.
The C++ source files for ndbd_redo_log_reader
can be found in the directory
The following table includes options that are specific to the MySQL Cluster program ndbd_redo_log_reader. Additional descriptions follow the table. For options common to most MySQL Cluster programs (including ndbd_redo_log_reader), see Section 17.4.26, “Options Common to MySQL Cluster Programs — Options Common to MySQL Cluster Programs”.
Table 17.81 This table describes command-line options for the ndbd_redo_log_reader program
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
In each case, the
# represents a
number (not necessarily the same number). For more information,
see MySQL 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:
Permitted Values Type
Permitted Values Type
Introduced 5.1.73-ndb-7.1.30 Command-Line Format
Added in MySQL Cluster NDB 6.3.53, MySQL Cluster NDB 7.0.41, and MySQL Cluster NDB 7.1.30. (Bug #11749591, Bug #36805)
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) ndbd_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