- Documentation Library
- Table of Contents
- MySQL 6.0 Reference Manual
- MySQL 5.1 Reference Manual
- MySQL 5.0 Reference Manual
- MySQL 3.23/4.0/4.1 Manual
- Table of Contents
- 20.10 Cluster Utility Programs
- 20.10.1 ndb_config — Extract NDB Configuration Information
- 20.10.2 ndb_cpcd — Automate Testing for NDB Development
- 20.10.3 ndb_delete_all — Delete All Rows from NDB Table
- 20.10.4 ndb_desc — Describe NDB Tables
- 20.10.5 ndb_drop_index — Drop Index from NDB Table
- 20.10.6 ndb_drop_table — Drop NDB Table
- 20.10.7 ndb_error_reporter — NDB Error-Reporting Utility
- 20.10.8 ndb_print_backup_file — Print NDB Backup File Contents
- 20.10.9 ndb_print_schema_file — Print NDB Schema File Contents
- 20.10.10 ndb_print_sys_file — Print NDB System File Contents
- 20.10.11 ndbd_redo_log_reader — Check and Print Content of Cluster Redo Log
- 20.10.12 ndb_select_all — Print Rows from NDB Table
- 20.10.13 ndb_select_count — Print Row Counts for NDB Tables
- 20.10.14 ndb_show_tables — Display List of NDB Tables
- 20.10.15 ndb_size.pl — NDBCLUSTER Size Requirement Estimator
- 20.10.16 ndb_waiter — Wait for Cluster to Reach a Given Status
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 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
/storage/ndb/src/kernel/blocks/dblqh/redoLogReader.
Usage:
ndbd_redo_log_readerfile_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_.
In each case, the #_fs/D#/LCP/#/T#F#.Data# represents a
number (not necessarily the same number). For more
information, see
Cluster Data Node FileSystemDir Files.
Additional Options:
The name of the file to be read may be followed by one or more of the options listed here:
-noprint: Do not print the contents of the log file.-nocheck: Do not check the log filre for errors.
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
filesystem 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
Add your own comment.