Solr Log Overview
Log Description
Log path: The default storage path of Solr log files is /var/log/Bigdata/solr/Role name.
- SolrServerAdmin:
- /var/log/Bigdata/solr/SolrServerAdmin (run logs)
- /var/log/Bigdata/solr/SolrHAServer (run logs)
- /var/log/Bigdata/audit/solr/SolrServerAdmin (audit logs)
- SolrServer1:
- /var/log/Bigdata/solr/SolrServer1 (run logs)
- /var/log/Bigdata/audit/solr/SolrServer1 (audit logs)
- SolrServer2:
- /var/log/Bigdata/solr/SolrServer2 (run logs)
- /var/log/Bigdata/audit/solr/SolrServer2 (audit logs)
- SolrServer3:
- /var/log/Bigdata/solr/SolrServer3 (run logs)
- /var/log/Bigdata/audit/solr/SolrServer3 (audit logs)
- SolrServer4:
- /var/log/Bigdata/solr/SolrServer4 (run logs)
- /var/log/Bigdata/audit/solr/SolrServer4 (audit logs)
- SolrServer5:
- /var/log/Bigdata/solr/SolrServer5 (run logs)
- /var/log/Bigdata/audit/solr/SolrServer5 (audit logs)
- HbaseIndexer:
- /var/log/Bigdata/solr/HBaseIndexer (run logs)
Log archive rule: The automatic Solr log compression function is enabled. By default, when the size of logs exceeds 5 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 the Manager portal.
Log Type |
Name |
Description |
---|---|---|
Run logs |
solr-<hostname>.log |
Solr system log file, which records most logs generated when the Solr system is running |
SolrServer1~5/solr-process-check.log SolrServerAdmin/solr-process-check.log |
Solr process check log file |
|
solr-service-check.log |
Solr service check log file |
|
SolrServer1~5/solr-startup.log SolrServeAdmin/solr-startup.log |
Solr startup log file |
|
SolrServer1~5/solr-stop.log SolrServerAdmin/solr-stop.log |
Solr stop log file |
|
SolrServer1~5/solr-<date>_gc.log.<index> SolrServerAdmin/solr-<date>_gc.log.<index> |
GC log file of the SolrServer instance |
|
solrhaserverDetail.log |
Log file that records the startup and stop status check of Solr HA |
|
SolrServer1~5/postinstallDetail.log SolrServerAdmin/postinstallDetail.log |
Work log file generated after the Solr service installation and before the Solr service startup |
|
SolrServer1~5/prestartDetail.log SolrServerAdmin~5/prestartDetail.log |
Log file that records the preparation before the startup of the Solr service |
|
SolrServer1~5/solr-catalina-<hostname>.log SolrServerAdmin/solr-catalina-<hostname>.log |
Catalina engine startup log file |
|
SolrServer1~5/solr-catalina-<hostname>.out SolrServerAdmin/solr-catalina-<hostname>.out |
Log that records the environment information required for Catalina engine startup |
|
SolrServer1~5/solr-threadDump-<date>.log SolrServerAdmin/solr-threadDump-<date>.log |
Solr instance stack log |
|
ha.log |
HA run log |
|
rs-floatip.log |
Log file that records the floating IP address configuration |
|
rs-sendAlarm.log |
Log file that records HA alarms |
|
ha_monitor.log |
HA monitoring log file |
|
hbaseindexer.out |
Log that records the running environment information of the HBaseIndexer service |
|
hbaseindexer-service-check.log |
HBaseIndexer service check log |
|
HBaseIndexer-threadDump-<date>.log |
HBaseIndexer stack log |
|
hbaseindexer-omm-<hostname>.log |
HBaseIndexer system log file that records most of the logs generated when HBaseIndexer is running |
|
hbaseindexer-omm-<date>-gc.log.<index> |
GC log file of the HBaseIndexers instance |
|
HBaseIndexer/postinstallDetail.log |
Work log file generated after the HBaseIndexer service installation and before the HBaseIndexer service startup |
|
HBaseIndexer/prestartDetail.log |
Log file that records the preparation before the startup of the HBaseIndexer service |
|
HBaseIndexer/startDetail.log |
HBaseIndexer startup log file |
|
HBaseIndexer/stopDetail.log |
HBaseIndexer stop log file |
|
Audit log |
solr-audit-<hostname>.log |
Audit log file that records the Solr operations (such as creating, deleting, modifying, and querying files) |
Log levels
Table 2 describes the log levels provided by Solr.
The priorities of log levels are FATAL, ERROR, WARN, INFO, and DEBUG in descending order. Logs whose levels are higher than or equal to the set level are printed. The number of printed logs decreases as the configured log level increases.
Level |
Description |
---|---|
FATAL |
Logs of this level record all log information about the current event processing. |
ERROR |
Error information about the current event processing |
WARN |
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. |
To modify log levels, perform the following operations:
- Log in to Manager.
- Choose Cluster > Name of the desired cluster > Service > Solr > Configuration.
- 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 configuration take effect.
Log Format
The Solr log formats are as follows:
Log Type |
Format |
Example |
---|---|---|
Run logs |
<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> |
2016-02-18 21:31:24,227 | INFO | http-bio-192.168.0.227-21101-exec-9 | [admin] webapp=null path=/admin/cores params={wt=json&_=1432906471360} status=0 QTime=3 | org.apache.solr.servlet.SolrDispatchFilter.handleAdminRequest(SolrDispatchFilter.java:757) |
Audit logs |
<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> |
2016-02-18 09:45:00,093 | INFO | http-nio-21101-exec-5 | RemoteAddr=192.168.0.221:37976 UserName=admin ResourceType=Core Detail=wt=json&_=1458612365349 Result=Success | com.*.solr.security.audit.AuditLogAppender.auditLogInfo(AuditLogAppender.java:20) |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot