MySQL 5.5 Reference Manual Including MySQL NDB Cluster 7.2 Reference Guide

18.4.20 ndb_redo_log_reader — Check and Print Content of Cluster Redo Log

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 18.4.27, “Options Common to NDB Cluster Programs — Options Common to NDB Cluster Programs”.

Table 18.269 Command-line options for the ndb_redo_log_reader program

Format Description Added, Deprecated, or Removed


Print dump info

All MySQL 5.5 based releases


Print file descriptors only

All MySQL 5.5 based releases


Print usage information

ADDED: NDB 7.2.15


Provide lap info, with max GCI started and completed

All MySQL 5.5 based releases

-mbyte #

Starting megabyte

All MySQL 5.5 based releases


Show only the first page header of every megabyte in the file

All MySQL 5.5 based releases


Do not check records for errors

All MySQL 5.5 based releases


Do not print records

All MySQL 5.5 based releases

-page #

Start with this page

All MySQL 5.5 based releases


Show page headers only

All MySQL 5.5 based releases

-pageindex #

Start with this page index

All MySQL 5.5 based releases


Bit-shifted dump

All MySQL 5.5 based releases


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#.FragLog. nodeid 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:

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.