Documentation Home
MySQL 5.6 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 31.0Mb
PDF (A4) - 31.1Mb
PDF (RPM) - 30.3Mb
EPUB - 7.8Mb
HTML Download (TGZ) - 7.6Mb
HTML Download (Zip) - 7.6Mb
HTML Download (RPM) - 6.5Mb
Eclipse Doc Plugin (TGZ) - 8.3Mb
Eclipse Doc Plugin (Zip) - 10.1Mb
Man Pages (TGZ) - 181.9Kb
Man Pages (Zip) - 293.2Kb
Info (Gzip) - 2.9Mb
Info (Zip) - 2.9Mb
Excerpts from this Manual

MySQL 5.6 Reference Manual  /  ...  /  ndbd_redo_log_reader — Check and Print Content of Cluster Redo Log

18.4.19 ndbd_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. 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.

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

Table 18.92 This table describes command-line options for the ndbd_redo_log_reader program

Format Description Added or Removed

-noprint

Do not print records

All MySQL 5.6 based releases

-nocheck

Do not check records for errors

All MySQL 5.6 based releases

--help

Print usage information

ADDED: NDB 7.3.4


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 ValuesTypeboolean
    DefaultFALSE

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

  • Command-Line Format-nocheck
    Permitted ValuesTypeboolean
    DefaultFALSE

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

  • Introduced5.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.


User Comments
Sign Up Login You must be logged in to post a comment.