LakeSearch Logs

Log paths:

SearchServer log path: /var/log/Bigdata/lakesearch/searchserver
SearchFactory log path: /var/log/Bigdata/lakesearch/searchfactory

Log archiving rules:

By default, service logs are stored every 50 MB or every day, and 20 log files are retained for 30 days and compressed in GZIP format.

**Table 1** LakeSearch logs
Log Type	Log File	Description
SearchServer logs	cleanup.log	Cleanup log file for instance installation and uninstallation
	prestart.log	Startup log
	scc.log	Run log of the encryption and decryption framework
	searchserver-*.log.gz	Archive package of SearchServer run log
	searchserver-gc.log	GC log
	searchserver.log	Run log
	searchserver-process-check.log	Health check log
	searchserver-shutdown.log	Stop log
	searchserver-start.log	Startup log
	tomcat_access.log	Log file that records information about all requests for accessing SearchServer
SearchFactory Logs	cleanup.log	Cleanup log file for instance installation and uninstallation
	postinstall.log	Pre-preparation log after instance installation
	prestart.log	Startup log
	searchfactory-*.log.gz	Archive package of SearchFactory run log
	searchfactory-gc.log	GC log
	searchfactory.log	Run log
	searchfactory-process-check.log	Health check log
	searchfactory-shutdown.log	Stop log
	searchfactory-start.log	Startup log
	tomcat_access.log	Log file that records information about all requests for accessing SearchFactory

Log Level

Table 2 describes the log levels of LakeSearch. The priorities of log levels are ERROR, WARN, INFO, DEBUG, and TRACE in the descending order. Logs of a specified level or higher can be printed. If you specify a higher log level, fewer logs will be printed.

**Table 2** Log levels
Level	Description
OFF	Logs of this level indicate that the log output is disabled.
ERROR	Logs of this level record errors about event processing.
WARN	Logs of this level record exception information about the current event processing
INFO	Logs of this level record normal running status information about the system and events
DEBUG	Logs of this level record the system information and system debugging information
TRACE	Logs of this level indicate information whose granularity is lower than that of DEBUG.

To modify log levels, perform the following operations:

Log in to FusionInsight Manager and choose Cluster > Services > LakeSearch. Click Configurations and click All Configurations.
On the menu bar on the left, select the log menu of the target role.
Select a desired log level.
Save the configuration. In the displayed dialog box, click OK to apply the change.

Log Format

**Table 3** Log formats
Type	Format	Example
Run log	<yyyy-MM-dd HH:mm:ss,SSS>\|<Log Level>\|<Name of the thread that generates the log>\|<Name of the class that output the log>\|<Host name>\|<Tag>\|<Message in the log>\|<newline>	[2024-01-24T18:57:45,116][WARN ][main][c.h.s.s.w.u.OmSwitch ][hostname][WSF-OM] Can't find the om properties file.