HAWQ Administrative Log Files
Log files are files that include messages and other information about your HAWQ deployment, including the database and utilities. HAWQ administrative log files reside in pre-defined or configured locations on the local file system of the HAWQ node. These log files are distinctly located, formatted, configured, and managed.
Every database instance in HAWQ (master, standby, and segments) runs a PostgreSQL database server with its own server log file. You generate log files when you invoke HAWQ management utilities directly, or indirectly via Ambari management operations. Additionally, other components in your HAWQ cluster (PXF, HDFS) generate log files of their own.
Configurable logging parameters may affect what, when, and where messages are logged. You configure HAWQ administrative logging options via HAWQ server configuration parameters or command line options.
Log files may be created and/or rotated at pre-defined or configured intervals. Note that administrative log files are not automatically truncated or deleted. The administrator must implement and periodically run scripts to clean up these log files.
Each HAWQ master, standby, and segment database instance has its own server log file. Daily log files are created in the
pg_log subdirectory of the master and segment data directory on the respective HAWQ node. You can obtain the master data directory location from the
hawq_master_directory property value set in the
hawq-site.xml configuration file. Similarly, you can obtain the segment data directory location from the
hawq_segment_directory property value from
The naming convention for HAWQ database server log files is
hawq-<date>_<time>.[csv|log]. For example,
hawq-2017-01-03_001704.log. The number and size of log files present for a given <date> is dependent upon the values of certain HAWQ server configuration parameters (discussed later in this document).
The HAWQ server log files are written in text or comma-separated values (CSV) format.
HAWQ log entries may include the following fields:
|#||Field Name||Data Type||Description|
|1||event_time||timestamp with time zone||Th time that the log entry was written to the log|
|2||user_name||varchar(100)||The database user name|
|3||database_name||varchar(100)||The database name|
|4||process_id||varchar(10)||The system process ID (prefixed with “p”)|
|5||thread_id||varchar(50)||The thread count (prefixed with “th-”)|
|6||remote_host||varchar(100)||The hostname/address of the client machine (if on master node). The hostname/address of the master (if on segment node).|
|7||remote_port||varchar(10)||The segment or master port number|
|8||session_start_time||timestamp with time zone||The time the session connection was opened|
|9||transaction_id||int||The top-level transaction ID on the master; this ID is the parent of any subtransactions.|
|10||gp_session_id||text||The session identifier number (prefixed with “con”)|
|11||gp_command_count||text||The command number within a session (prefixed with “cmd”)|
|12||gp_segment||text||The segment content identifier. The master always has a content ID of -1.|
|13||slice_id||text||The slice ID (portion of the query plan being executed)|
|14||distr_tranx_id||text||The distributed transaction identifier|
|15||local_tranx_id||text||The local transaction identifier|
|16||sub_tranx_id||text||The subtransaction identifier|
|17||event_severity||varchar(10)||The event severity; values include: LOG, ERROR, FATAL, PANIC, DEBUG1, DEBUG2|
|18||sql_state_code||varchar(10)||The SQL state code associated with the log message|
|19||event_message||text||The log or error message text|
|20||event_detail||text||The detail message text associated with an error or warning message|
|21||event_hint||text||The hint message text associated with an error or warning message|
|22||internal_query||text||The internally-generated query text|
|23||internal_query_pos||int||The cursor index into the internally-generated query text|
|24||event_context||text||The context in which this message is generated|
|25||debug_query_string||text||User-supplied query string with full detail for debugging. This string can be modified for internal use.|
|26||error_cursor_pos||int||The cursor index into the query string|
|27||func_name||text||The function in which this message is generated|
|28||file_name||text||The name of the source file in which the message originated|
|29||file_line||int||The line number of the source file in which the message originated|
|30||stack_trace||text||The stack trace text associated with this message|
Note: Log entries may not include values for all log fields. For example, the
slice_id field is populated only for log entries associated with a query worker process.
Example HAWQ server log file entries in a
2017-01-02 01:19:55.293050 PST,"gpadmin","testdb",p381034,th-1259067104,"[local]",,2017-01-02 01:19:21 PST,28083,con3595,cmd7,seg-1,,,x28083,sx1,"LOG","00000","ConnID 207. Acquired resource from resource manager, (256 MB, 0.062500 CORE) x 1.",,,,,,"INSERT INTO extblwstrings VALUES ('my string');",0,,"rmcomm_QD2RM.c",868, 2017-01-02 06:16:06.383827 PST,,,p360256,th-1259067104,,,,0,,,seg-10000,,,,,"LOG","00000","database system is shut down",,,,,,,0,,"xlog.c",7882,
Example HAWQ server log file entries in a
2017-01-03 00:17:04.848268 PST|||706424|startup||:-LOG: database system was shut down at 2017-01-03 00:16:58 PST 2017-01-03 00:17:04.988778 PST|gpadmin|template1|706437|cmd1|x31410|:-LOG: statement: SELECT oid,rolname,rolsuper,rolresqueue FROM pg_authid 2017-01-03 00:17:04.990520 PST|||706432|master resource manager||:-LOG: Resource manager successfully loaded role specifications.
You will examine the HAWQ log files to obtain information about your HAWQ deployment, as well as diagnose problems.
Identify log entries of related transactions using the
transaction_id. You can identify related log entries of a particular query by the query’s session identifier (
gp_session_id) and command identifier (
For example, the following
hawq_toolkit query displays the time and message for all
ERROR logs related to the database named
=# SELECT logtime, logmessage FROM hawq_toolkit.hawq_log_master_concise WHERE logdatabase='testdb' AND logseverity='ERROR';
gplogfilter HAWQ utility to search through a HAWQ log file for entries matching specific criteria. By default, this utility searches through the HAWQ master log file in the default location.
For example, to display the entries logged to the master log file after 2:00pm on January 18, 2016:
$ gplogfilter -b '2016-01-18 14:00'
gplogfilter using the
hawq ssh utility to search through all segment log files simultaneously. For example, create a <seg_hosts> file that includes all segment hosts of interest, then invoke
gplogfilter to display the last three lines of each segment log file on each segment host. (Note: enter the commands after the
=> prompt, do not include the
$ hawq ssh -f <seg_hosts> => source /usr/local/hawq/greenplum_path.sh => gplogfilter -n 3 /data/hawq/segment/pg_log/hawq*.csv
You can configure the logging characteristics of HAWQ server operations using HAWQ server configuration Logging Parameters. These configuration parameters work in conjunction with each other to determine what information is logged to the HAWQ server log file, and when.
HAWQ server logging-related configuration parameters include:
|Server Configuration Parameter||Description|
||Identify log level for client messages|
||Indent/format debug output to make it more readable|
||Identify format of server log files|
||Set the maximum line length of csv-formatted file|
||Log information about automatic statistics generation|
||Log each client connection|
||Log each client connection termination|
||Log information related to statement dispatch|
||Log the duration of completed statements satisfying
||Govern how much detail is written to the log|
||Log the hostname of the connecting host|
||Configure runtime duration at which a statement should be logged|
||Write sql statement causing the error condition|
||Identify log level for writing to log file|
||Control which SQL statements are logged|
||Set the timezone used in log file timestamps|
When log file rotation is enabled, you can control the rotation options with these HAWQ server configuration parameters:
|Server Configuration Parameter||Description|
||Configure the lifetime of log file|
||Configure the maximum size of log file|
||Identify whether to truncate or append to the log file|
HAWQ exposes a set of server configuration parameters dealing exclusively with GPORCA query executor and optimizer logging. These include:
|Server Configuration Parameter||Description|
||Log the query parse tree|
||Log the query plan|
||Log the preliminary query plan|
||Log the query rewriter output|
||Log the query slice plan|
||Log query executor performance statistics|
||Log query parser performance statistics|
||Log the performance statistics of the legacy query optimizer (planner)|
||Log the total performance statistics of the query parser, planner, and executor|
Query Minidump Log Files identifies configuration options and additional information related to generating query optimizer minidump log files.
HAWQ log output tends to be voluminous, especially at higher debug levels. You should not need to save this information indefinitely. HAWQ administrators typically configure HAWQ to rotate the log files periodically so new log files are created.
Daily log files are created in the
pg_log subdirectory of the master and each segment data directory. Although log files are rolled over daily, they are not automatically truncated or deleted. Administrators must implement and run scripts to periodically clean up old log files in the
pg_log directory of the master, standby, and every segment instance.
You invoke HAWQ management utilities both from the command line and when you perform cluster management activities using the Ambari user interface. Regardless of source, these utilities log information about command execution status and results. The messages are logged to both
stdout and a log file.
Each management utility, when invoked, creates/manages a daily log file. The logs for a particular execution of a utility are added or appended to its daily log file each time that utility is run that day.
Note: Some management utilities are aliases for invoking one or more other management utilities. For example,
hawq restart invokes
hawq stop and
hawq start. Logs are written to the daily log files associated with the two invoked utilities.
The default location of HAWQ management utility log files is
/home/gpadmin/hawqAdminLogs/. You may choose to specify an alternate log file directory.
The naming convention for HAWQ management utility log files is
<cmdname>_<date>.log. For example,
HAWQ management utility log files are written in text format.
Management utility commands’ log entries are formed as follows:
Log entry fields are described in the table below.
|Log Entry Field||Description|
|date||The date (month, day, year) the entry was logged|
|time||The time the entry was logged|
|pid||The process id associated with the command invocation|
|cmdname||The name of the HAWQ management utility command|
|host||The name of the host on which the command was executed|
|user||The name of the user invoking the command|
|loglevel||The log level, one of
|message||The log message|
Example management utility log entries:
20170102:06:16:06:451225 hawq_stop:hmast1:gpadmin-[INFO]:-Master host=hmast1
20170102:06:16:15:451826 hawq_start:hmast1:gpadmin-[INFO]:-Start hawq with args: ['start', 'segment']
Note: The log files for certain management utility commands, for example
hawq init, diverge from these conventions.
You will examine the HAWQ management utility log files to get more detailed information about the execution of the command. Additionally, the most recent log file for a particular command provides date/time and status information about the last time you invoked the command.
Most management utilities support options for verbose logging and identifying alternate log file directories.
Management utility logging-related configuration command options include:
|-l | --logdir <dir>||Use alternate log file directory <dir> for this command invocation.|
|-v | --verbose||Include
Invoke the management utility command with the
--help option to determine support for changing the log directory and/or enabling verbose output.
Although Management Utility log files are rolled over daily, they are not automatically truncated or deleted. Administrators should implement and run scripts or programs to periodically clean up old Management Utility log files.
You can configure the HAWQ GPORCA query optimizer to generate output minidump files describing the optimization context for a given query. (The information in a minidump file is not in a format that you can easily understand. Rather, you would generate and provide the minidump file to the HAWQ development team or support.)
GPORCA minidump files include the following query-related information:
- Catalog objects including data types, tables, operators, and statistics required by GPORCA.
- An internal representation (DXL) of the query.
- An internal representation (DXL) of the query plan produced by GPORCA.
- System configuration information passed to GPORCA, including server configuration parameters, cost and statistics configuration, and number of segments.
- A stack trace of errors generated while optimizing the query.
Query minidump files are generated in a
minidumps/ subdirectory in the HAWQ master data directory. The minidump file naming convention is
Minidump_<date>_<time>_<gp_session_id>_<gp_command_count>.mdp, for example
Use the optimizer_minidump HAWQ server configuration parameter to configure minidump generation. The default setting generates minidump files only on error.
PXF provides both service- and database-level logging. Refer to PXF Logging for specific PXF logging configuration and management information.
Ambari log files may be useful in helping diagnose general cluster problems. The Ambari server log files are located in the
/var/log/ambari-server/ directory. Ambari agent log files are located in
/var/log/ambari-agent/. Refer to Reviewing Ambari Log Files for additional information.
Hadoop log files are managed by your Hadoop distribution. If you built Hadoop from source, your log file locations and configuration may be governed by the build and/or install options you specified during the build process.