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 remains under development, and its syntax and
behavior are subject to change in future MySQL Cluster releases.

The C++ source files for ndbd_redo_log_reader
can be found in the directory
/storage/ndb/src/kernel/blocks/dblqh/redoLogReader.

Usage

ndbd_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_#_fs/D#/LCP/#/T#F#.Data.
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:

Command-Line Format

-noprint

Permitted Values

Type

boolean

Default

FALSE

-noprint: Do not print the contents of the
log file.

Command-Line Format

-nocheck

Permitted Values

Type

boolean

Default

FALSE

-nocheck: Do not check the log file for
errors.

Introduced

5.6.15-ndb-7.3.4

Command-Line Format

--help

--help: Print usage information.

Added in MySQL Cluster NDB 7.3.4. (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
down.