DataStax Help Center

FAQ - Setting DEBUG in the system.log for DSE Solr

Overview

This article provides instructions on how to turn on debug logging in DSE Solr to see incoming queries and returned results in the /var/log/cassandra/system.log

Background

Although it is possible to set debug on all events in the logs using the procedures mentioned below for cassandra 2.0 and 2.1 based DSE releases, the user may wish to just set debug logging for DSE Solr.

Procedure

Follow these steps to set the debug logging for Solr in DSE. Note that changing the log4j-server.properties and logback.xml files may require a restart of the DSE process.

For Cassandra 2.0 based DSE releases up to but not including 4.6.8 and 4.7.1

Edit the log4j-server.properties file to include the following line:

log4j.logger.org.apache.solr.core.SolrCore=DEBUG

Note: there can be a performance penalty when using this with vnodes. This is covered in the following internal jira:

DSP-3759 - Investigate impact and improvements of vnodes in Solr

For Cassandra 2.0 based DSE releases 4.6.8 and 4.7.1 and later

Edit the log4j-server.properties file to include the following line:

log4j.logger.com.datastax.bdp.search.solr.dht.ShardRouter=DEBUG

For Cassandra 2.1 based DSE releases

Edit the logback.xml file to include the following

<logger name="com.datastax.bdp.search.solr.dht.ShardRouter" level="DEBUG"/>

Also you can change this temporarily by using nodetool

nodetool setlogginglevel com.datastax.bdp.search.solr.dht.ShardRouter DEBUG

See Also

The following documentation links cover some further reading on this topic

Cassandra 2.1 - nodetool setlogginglevel

DSE4.8 debug logging

DSE4.6 debug logging

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk