MySQL 8.4 Release Notes
25.5.12 ndb_error_reporter — NDB 错误报告实用程序
ndb_error_reporter creates an archive from data node and management node log files that can be used to help diagnose bugs or other problems with a cluster. It is highly recommended that you make use of this utility when filing reports of bugs in NDB Cluster.
Options that can be used with ndb_error_reporter are shown in the following table. Additional descriptions follow the table.
ndb_error_reporter path/to/config-file [username] [options]This utility is intended for use on a management node host, and requires the path to the management host configuration file (usually named config.ini). Optionally, you can supply the name of a user that is able to access the cluster's data nodes using SSH, to copy the data node log files. ndb_error_reporter then includes all of these files in archive that is created in the same directory in which it is run. The archive is named ndb_error_report_, where YYYYMMDDhhmmss.tar.bz2YYYYMMDDhhmmss is a datetime string.
ndb_error_reporter also accepts the options listed here:
-
Command-Line Format --connection-timeout=#Type Integer Default Value 0Wait this many seconds when trying to connect to nodes before timing out.
-
Command-Line Format --dry-scpRun ndb_error_reporter without using scp from remote hosts. Used for testing only.
-
Command-Line Format --helpDisplay help text and exit.
-
Command-Line Format --fsCopy the data node file systems to the management host and include them in the archive.
Because data node file systems can be extremely large, even after being compressed, we ask that you please do not send archives created using this option to Oracle unless you are specifically requested to do so.
-
Command-Line Format --connection-timeout=#Type Integer Default Value 0Skip all nodes belong to the node group having the supplied node group ID.