In case of Solr index maintenance errors or executions, the following guideline will help you to collect important log information from Solr maintenance operations logged in ICM AS and Solr Cloud server logs.
This article mainly focuses on custom appender which does collect Solr index related db statements, classes, pipelines, pipelet execution from search index maintenance operation triggered by schedule job or back office GUI interaction.
Further you can see the queries, which are triggered to the Solr Server. Additional you will know which log files are important to analyze Solr index issues.
To set up the special logging, you need to perform the following steps.
As result SolrAdapter.log is written below \eserver\share\system\log for further analysis.
The log appender does generate dedicated log output from Solr index maintenance operation or index queries.
The only thing to adjust is the index name mentioned in your Intershop Commerce Management, because it can be specific.
In the following example, the log appender will collect index maintenance information from ICM back office search index with name product-search-idx-en_US.
As result, the provided Solr log appender is able to log runtimes from pipelines, pipelets or db statements you may need for (performance) analysis.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.