Logging for the Repair Service

Repair Service log names and locations

All Repair Service activity is logged by default to a log file in the repair_service directory applicable to the install type and each cluster name:

  • Package installs


  • Tarball installs


Rotating the Repair Service log

The log file is automatically rotated at ~9.5MB (<maxFileSize> logback setting), keeping up to ten rotated logs by default (<maxIndex> logback setting).

Configuring the Repair Service log

The Repair Service log options and levels are configurable using logback.xml.

The following example shows a standard configuration for a package install. Replace cluster_name with the name of your cluster. The log level is set at the INFO level by default. The example shows temporarily setting the level to DEBUG level for troubleshooting purposes.

<appender name="cluster_name_log" class="ch.qos.logback.core.rolling.RollingFileAppender">
          <pattern>%date{ISO8601, UTC} [%X{cluster_id:-opscenterd}] %5level: %msg (%thread)%n%exception{20}</pattern>
      <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
       <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
<filter class="ch.qos.logback.classic.filter.ThresholdFilter">

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000, info@datastax.com