Cloudera Search Configuration and Log Files

Cloudera Search (powered by Apache Solr) configuration is managed using Cloudera Manager. You can view log files on the individual Solr server or using Cloudera Manager.

Viewing and Modifying Cloudera Search Configuration

To view and edit configuration parameters for the Solr service in Cloudera Manager:

  1. Go to Solr service > Configuration.
  2. Use the SCOPE and CATEGORY filters to restrict the displayed configuration parameters. You can also enter text in the Search field to dynamically filter configuration parameters.
  3. After making changes, enter a Reason for change, and click Save Changes.
  4. Restart the Solr service (Solr service > Actions > Restart) and any dependent services.

Viewing and Modifying Log Levels for Cloudera Search and Related Services

You can view and modify log levels for Search and related services (such as Apache Flume, Apache HBase, and so on) by:

  1. Go to the service configuration page. For example: Solr service > Configuration
  2. Select the CATEGORY > Logs filter.
  3. Modify the logging threshold for the service roles. Available options (in descending verbosity) are:
    • TRACE
    • DEBUG
    • INFO
    • WARN
    • ERROR
    • FATAL
  4. Enter a Reason for change, and then click Save Changes to commit the changes.
  5. Restart the service. For example: Solr service > Actions > Restart

    You can also restart dependent services using the Restart Stale Services wizard.

Cloudera Search Log Files

Cloudera Search has several log files, stored on each Solr Server host. See the following for log file locations and a brief description of each. The referenced configuration parameters can be viewed or modified as described in Viewing and Modifying Cloudera Search Configuration:

  • /var/log/solr/ - Parent directory for most Search logs.
    • audit/ - Audit log directory, specified by the Audit Log Directory configuration parameter.
    • stacks/ - Directory containing period stack dumps, if Stacks Collection Enabled is checked. The directory name can be changed by setting the Stacks Collection Directory parameter.
    • - Solr server log file. The SOLR-1 and portion varies depending on your environment. The log default log level is INFO, and is controlled by the Solr Server Logging Threshold parameter for Solr Server roles, and the Gateway Logging Threshold parameter for Gateway roles.
    • solr_gc_log.* - Java garbage collection (GC) logs for the Solr Server process.
  • /var/run/cloudera-scm-agent/process/<process_dir_id>-solr-SOLR_SERVER/ - Configuration directory for the currently running Solr Server role.

    The <process_dir_id> portion changes each time the Solr Server is restarted. To identify the current or most recent directory, list the /var/run/cloudera-scm-agent/process/*solr* directories sorted by time in reverse as follows:

    sudo ls -ltrd /var/run/cloudera-scm-agent/process/*solr*

    The entry at the bottom is the current or most recent process directory.

    • logs/ - Log directory containing the stderr and stdout logs for the Solr Server process.