Solr log messages
DSE Search logs Solr errors, warnings, debug, trace, and info messages in the Cassandra system log.
DSE Search logs Solr errors, warnings, debug, trace, and info messages in the
Cassandra system log:
/var/log/cassandra/system.log
Changing the Solr logging level
Assuming you configured and are using the Apache
log4j utility, you can control the granularity of Solr log messages, and
other log messages, in the Cassandra system.log file by configuring the
log4j-server.properties file. The log4j-server.properties file is located in:
- Packaged installs: : /etc/dse/cassandra
- Binary Installs: /resources/cassandra/conf/
To set log levels, configure the log4j.rootLogger value, specifying one of these
values:
- All - turn on all logging
- OFF - no logging
- FATAL - severe errors causing premature termination
- ERROR - other runtime errors or unexpected conditions
- WARN - use of deprecated APIs, poor use of API, near errors, and other undesirable or unexpected runtime situations
- DEBUG - detailed information on the flow through the system
- TRACE - more detailed than DEBUG
- INFO - highlight the progress of the application at a coarse-grained level
For example, open the log4j-server.properties file and change
the log level by configuring the log4j.rootLogger
value:
# output messages into a rolling log file as well as stdout log4j.rootLogger=INFO,stdout
Accessing the validation Log
DSE Search stores validation errors that arise from non-indexable data sent from
non-Solr nodes in this log:
/var/log/cassandra/solrvalidation.log
For example, if a Cassandra node that is not running Solr puts a string in a date field, an exception is logged for that column when the data is replicated to the Solr node.