Metadata Log Overview

Log Description

Log path: The default paths of Metadata log files are /var/log/Bigdata/metadata/ (for storing run logs) and /var/log/Bigdata/audit/metadata/ (for storing audit logs).

Log archive rule: The automatic Metadata log compression function is enabled. By default, when the size of logs exceeds 10 MB, logs are automatically compressed into a log file named in the following format: <Original log file name>-<yyyy-mm-dd_hh-mm-ss>.[ID].log.zip. A maximum of 20 latest compressed files are reserved. The number of compressed files can be configured on FusionInsight Manager.

**Table 1** Metadata log list
Log Type	Log File Name	Description
Run log	metadata-server.log	Metadata system log file, which records most of the logs generated when the Metadata system is running
	catalina.out	Metadata container run log file
	metadata-postinstall.log	Log file that records subsequent operations after Metadata is installed
	metadata-prestart.log	Log file that records the preparations before the startup of the Metadata service
	metadata-startup.log	Metadata service startup log file
	metadata-shutdown.log	Metadata service shutdown log file
	cleanupDetail.log	Log file that records Metadata service uninstallation and clearance
	metadata-<SSH_USER>-<DATE>-<PID>-gc.log	Log file that records the garbage collection of the Metadata service
	threadDump-<DATE>.log	jstack log file to be printed when the NodeAgent delivers a service stop command
	catalina.<DATE>.log, host-manager.<DATE>.log, localhost.<DATE>.log, localhost_access_log.<DATE>.log, manager.<DATE>.log, metadata-roll.log	Tomcat run logs
	threadDumpAbnormal-<DATE>.log	jstack log file printed when the NodeAgent delivers a stop command due to a service exception
Audit log	metadata-audit.log	Metadata operation audit log

Log Levels

Table 2 describes the log levels provided by Metadata. The priorities of log levels are DEBUG, INFO, WARN, and ERROR, in ascending order. Logs whose levels are higher than or equal to the set level are printed. The number of printed logs decreases as the specified log level increases.

**Table 2** Log levels
Level	Description
DEBUG	Logs of this level record the system information and system debugging information.
INFO	Logs of this level record normal running status information about the system and events.
WARN	Logs of this level record exception information about the current event processing.
ERROR	Logs of this level record error information about the current event processing.

To modify log levels, perform the following operations:

Log in to Manager.
Choose Cluster > Name of the desired cluster > Services > Metadata > Configurations.
Select All Configurations.
On the menu bar on the left, select the log menu of the target role.
Select a desired log level.
Click Save. In the displayed dialog box, click OK to make the configurations take effect.

The configurations take effect immediately without the need to restart the service.

Log Formats

The following table lists the Metadata log formats.

**Table 3** Log formats
Log Type	Format	Example
Run log	<yyyy-MM-dd HH:mm:ss,SSS>\|<Log level>\|<Name of the thread that generates the log>\|<Message in the log>\|<Location where the log event occurs>	[2015-06-29 10:45:59,954] [INFO ] [localhost-startStop-1] [com.xxx.fusioninsight.metadata.webserver.util.dbpassdecoder.PropertiesEncryptFactoryBean 55] SSL:null
Audit log	<yyyy-MM-dd HH:mm:ss,SSS>\|<Log level>\|<Name of the thread that generates the log>\|<Message in the log>\|<Location where the log event occurs>	2015-01-26 18:44:42,607 \| INFO \| IPC Server handler 32 on 8020 \| allowed=true ugi=hbase (auth:SIMPLE) ip=/10.177.112.145 cmd=getfileinfo src=/hbase/WALs/hghoulaslx410,16020,1421743096083/hghoulaslx410%2C16020%2C1421743096083.1422268722795 dst=null perm=null \| org.apache.hadoop.hdfs.server